Re: [ClusterLabs] Coming in Pacemaker 2.0.4: fencing delay based on what resources are where

2020-03-23 Thread Diego Akechi
On 21/03/2020 18:07, Ken Gaillot wrote: > I'd like to recognize the primary authors of the 2.0.4 features > announced so far: > - shutdown locks: myself > - switch to clock_gettime() for monotonic clock: Jan Pokorný > - crm_mon --include/--exclude: Chris Lumens > - priority-fencing-delay: Gao,Yan

Re: [ClusterLabs] Coming in Pacemaker 2.0.4: fencing delay based on what resources are where

2020-03-22 Thread Gao,Yan
On 2020/3/21 18:22, Andrei Borzenkov wrote: 21.03.2020 20:07, Ken Gaillot пишет: Hi all, I am happy to announce a feature that was discussed on this list a while back. It will be in Pacemaker 2.0.4 (the first release candidate is expected in about three weeks). A longstanding concern in two-no

Re: [ClusterLabs] Coming in Pacemaker 2.0.4: fencing delay based on what resources are where

2020-03-21 Thread Andrei Borzenkov
21.03.2020 20:07, Ken Gaillot пишет: > Hi all, > > I am happy to announce a feature that was discussed on this list a > while back. It will be in Pacemaker 2.0.4 (the first release candidate > is expected in about three weeks). > > A longstanding concern in two-node clusters is that in a split br

[ClusterLabs] Coming in Pacemaker 2.0.4: fencing delay based on what resources are where

2020-03-21 Thread Ken Gaillot
Hi all, I am happy to announce a feature that was discussed on this list a while back. It will be in Pacemaker 2.0.4 (the first release candidate is expected in about three weeks). A longstanding concern in two-node clusters is that in a split brain, one side must get a fencing delay to avoid sim