1,189
Hi Martin,
I have two AOS instances, and batch group linked to both AOS, how can I make a batch to run on both AOS's, whenever AOS1 is down to run on AOS2 and vice versa, because it is only working on AOS2 despite that batch group is linked to both AOS.
*This post is locked for comments
That's true, the batches won't work if you don't have any CIL generated. I wonder how you could have failed CIL in your prod environment but still were using it for actual operations. Definetely asking for trouble.
Seems your environment maintenance process has some flaws if your one AOS didn't have functional CIL and the other did.
When you deliver code to prod, you must shut down all AOSes. Assuming you use modelstore delivery (MS recommendation) all AOSes get the CIL from model database when they start. If you use some other delivery process, you must run full CIL generation on one AOS, and all other AOS instances must be switched off. After succesful CIL generation, you start other AOSes and they fetch the CIL from the model database.
If you fail to do this, you face issues like the one you had. Or some AOSes run different CIL version than others.
All AOS servers that are configured as batch AOS will look for Waiting batch jobs that have such batch group that is configured for processing for that AOS.
So nothing is routed from the first AOS to the second AOS. Both AOSes just look for batch jobs that they could start processing.
It seems you posted in a very old discussion and your question was not directly related to that discussion. I separated your question into it's own thread.
Do you have batch processing enabled for both AOSes in Server Configuration form in System Administration module?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
