10-23-2018 11:52 AM
I was originally planning to promote a grid member to a grid master candidate until I read that all these articles discuss using the set promote_master command, promotes an existing candidate to a grid master. Or if someone can correct me on this?
Solved! Go to Solution.
10-23-2018 12:01 PM - edited 10-23-2018 01:12 PM
There are two different concepts at work here:
- Any compatible Grid member can be enabled as a Grid Master Candidate (GMC). This is as simple as ticking a check box in its properties under the Grid -> Grid Manager -> Members tab.
- Only one server in your Grid will function as the Grid Master (though two appliances can operate in an active/passive role when the Grid Master is configured for High Availability).
If you wish to move the current Grid Master to a different Grid member that is enabled as a GMC, you would connect to the CLI for the Grid member that you are looking to promote to the Grid Master role and run the "set promote_master" command. That Grid member will then send announcements throughout the Grid, triggering the rest of the Grid to connect to it.
Hope this helps clear things up.
10-24-2018 06:52 AM
Enabling the Master Candidate option does not have any impact on services. Promoting a Grid member does not cause an interruption to its services, but all other Grid members may experience a short interruption as they may pull fresh database snapshots from the new Grid Master and reload their database's.
01-14-2019 09:29 AM - edited 01-14-2019 09:45 AM
Marking a Grid Member as a GMC (candidate grid master) will not cause a reboot but it will cause a product restart on this member and this member alone because it needs to receive a complete binary database from the Grid Master and apply it rather than the partial XML database it currently has. The database switch-over involves an automated restart.