11-19-2018 03:31 PM
When a GMC is promoted into a GM, what is the reboot order for members. Say the Grid has 3 members:
1. a DNS highly available member
2. The original GM, which is also a HA member
3. the GMC, which is about to be promoted, also a HA member
If the order or reboot for the above members can not be controllr, how can rejoining the new GM "old GMC" be delayed?
Solved! Go to Solution.
11-19-2018 03:39 PM
Details regarding the promotion process can be found in the NIOS Administrators Guide. For your reference:
"During a Grid Master promotion, the newly-promoted Grid Master continuously contacts all Grid members, including the original Grid Master on UDP port 2114 until it reaches them. It notifies all Grid members that it is the new Grid Master. The Grid Members restart and then attempt to establish normal Grid communications (via BloxSync) with the newly promoted Grid Master.
You can do one of the following to promote a Master Candidate:
• Immediately notify all Grid members about the promotion.
• Set a sequential notification to provide wait time for Grid members to join the new Grid Master. Staggering the
restarts of Grid members can minimize DNS outages. The sequential order for Grid members to join the new Grid
Master begins with the old Grid Master and then the Grid members in FQDN order. The default delay time is 120
seconds. You can configure the delay time from a minimum of 30 seconds up to 600 seconds."
In short- by default, they all go at the same time. You can stagger the restarts but this does not let you control the order.