[pve-devel] [RFC ha-manager v2 5/7] allow LRM lock stealing for fenced nodes

Thomas Lamprecht t.lamprecht at proxmox.com
Mon Mar 14 16:47:27 CET 2016



On 03/14/2016 04:33 PM, Dietmar Maurer wrote:
>> To summarize the possible states:
>> * the node is fenced and stays until someone comes and checks it
>> (through switch, power, ... - fencing) - here we can do everything with
>> the lock we want
>> * the node comes back immediately (reset) because someone thought this
>> was a good way to setup the fence agents (it really isn't) and is
> so we suggest to 'stop' nodes by fence agents (instead of restart)?
In my opinion yes, I would.
Restarting seems more dangerous to me than stopping a node (or cutting
it off from all networks) and then manually investigating what happened
and why.

>
>> through a wonder fully functional. Here it sees oh I'm in the fence
>> state, thus it doesn't even tries to get the lock and start anything
>> (thus lock stealing and time out is fine here). Or the lock
>> stealing/timeout (both "same" effect in this context) already happened
>> and the service are recovered.
>>
>> any thoughts? Do I have a really faulty reasoning somewhere?
> sounds reasonable to me.
ok, thanks. I'm preparing v3. :)




More information about the pve-devel mailing list