After a ServiceNow upgrade, all MID Servers are forced to restart simultaneously.

[Tomoki Yamagami]

Hi All,

I need to prevent my MID Servers from restarting simultaneously.

After a ServiceNow upgrade, all MID Servers are automatically restarted. Each MID Server then checks for and applies upgrades, ensuring consistency. This happens even for MID Servers in Clusters or Connector Instances.

This simultaneous restart and update also applies to MID Servers that are members of Clusters or Connector Instances. However, it's crucial to avoid any simultaneous downtime within these Clusters and Connector Instances.

While setting mid.pinned.version on MID Servers prevents subsequent upgrades, I'm unsure how to prevent the initial mandatory restart triggered by the ServiceNow upgrade.

Could you suggest a solution to avoid this initial, simultaneous restart? Thank you for your assistance.

[Runjay Patel · Accepted solution]

Hi @Tomoki Yamagami ,

Unfortunately, preventing the initial mandatory restart triggered by an upgrade is not directly configurable in ServiceNow.

mandatory restart that occurs after an upgrade is typically necessary to ensure that all new configurations and updates are applied correctly.

Accept the solution if it helped