[ClusterLabs] Recurring troubles with the weak grip on processes (Was: Timeout stopping corosync-qdevice service)

2019-05-02 Thread Jan Pokorný
On 30/04/19 20:39 +0300, Andrei Borzenkov wrote: > 30.04.2019 9:51, Jan Friesse пишет: >> >>> Now, corosync-qdevice gets SIGTERM as "signal to terminate", but it >>> installs SIGTERM handler that does not exit and only closes some socket. >>> May be this should trigger termination of main loop,

Re: [ClusterLabs] Timeout stopping corosync-qdevice service

2019-05-02 Thread Jan Friesse
Andrei, 30.04.2019 9:51, Jan Friesse пишет: Now, corosync-qdevice gets SIGTERM as "signal to terminate", but it installs SIGTERM handler that does not exit and only closes some socket. May be this should trigger termination of main loop, but somehow it does not. Yep, this is exactly how

Re: [ClusterLabs] Corosync unable to reach consensus for membership

2019-05-02 Thread Jan Friesse
Prasad, Hello Jan, Please block both input and output. Corosync isn't able to handle byzantine faults. Thanks. It results in clean partition if I block both outgoing and incoming udp traffic to and from a given node. Good However, could you suggest me what is the best way to handle