Uptime during Patches and Upgrades with Event Management

StephenM
Kilo Guru

‎08-11-2023 04:36 PM

For those of you running Event Management and/or Operational Intelligence.  How are you keeping all the MID servers from getting restarted when ServiceNow performs a patch or instance upgrade.

 

We have tried several of the KBs limiting the downloads to 1 and setting a pinned version on half the MID servers but it doesn't seem to stop them from getting restarted.  These restarts cause the OI clusters to alert and the Pull Connectors alert as they have no MID servers to run.  Also and SNMP traps would be lost since they are UDP.  

 

Due to the real time nature of Event Management we want to keep this up and running at all times.  There isn't a maintenance window for the collector of collectors.  

0 Helpfuls
  • 286 Views
2 REPLIES 2

Maik Skoddow
Tera Patron
Tera Patron

‎08-11-2023 10:51 PM

Hi

did you follow the instructions on page https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0860948 ?

If so and it is still updating, please create a support ticket as it seems to be a bug.

Maik

0 Helpfuls

StephenM
Kilo Guru
In response to Maik Skoddow

‎08-14-2023 07:29 AM

Adding the pinned version parameter it doesn't upgrade but it does still reboot.  We have an open case with ServiceNow but its a lot of back and forth.  Was hoping someone from the community had a workable solution.

 

Its weird to me there is no concept of a rolling restart through the MID servers in an instance.  This seems like a simple change in logic. From parallel to serial. Having these MID server clusters have limited value if they are all going to get a restart command at the same time.  

0 Helpfuls