[Info-vax] Quorum strategy

Marc Van Dyck marc.gr.vandyck at invalid.skynet.be
Thu May 23 03:10:14 EDT 2019


on 22/05/2019, Hans Bachner supposed :
> Stephen Hoffman schrieb am 22.05.2019 um 19:08:
> [...]
>> Give one vote to the cluster member host that you're referring to as the
>> primary.  Remove the quorum disk. Give no votes for the secondary.
>>
>> The secondary is operating as only a little more than a warm standby,
>> here.  Yes, it can be configured to run some apps.
> [...]
>
> This is not what he wants:
>
> Marc Van Dyck schrieb am 22.05.2019 um 10:44:
>> So, in case of the cluster connection manager will have to make a choice
>> between the two members (for example if the two nodes can't talk with
>> each other anymore), I'd like to make sure that it's the primary member
>> that will always survive.
>
> I believe Marc also mentioned somewhere (can't find that right now...) that 
> the secondary node could/should be used for some analysis/troubleshooting 
> tasks before it is rebooted. This would not work if only the primary node had 
> a vote. It even could not be cleany shut down before rebooting it as the "new 
> primary".
>
> Hans.

Yes indeed. And also let the applications running on the secondary
stop gracefully with no recovery work necessary before restart. We
have enough work with those that crashed with the primary already.

-- 
Marc Van Dyck



More information about the Info-vax mailing list