Re: [ClusterLabs] Fuzzy/misleading references to "restart" of a resource

2019-12-05 Thread Jan Pokorný
On 05/12/19 10:41 +0300, Andrei Borzenkov wrote: > On Thu, Dec 5, 2019 at 1:04 AM Jan Pokorný wrote: >> >> On 04/12/19 21:19 +0100, Jan Pokorný wrote: >>> OTOH, this enforced split of state transitions is perhaps what makes >>> the transaction (comprising perhaps countless other interdependent

Re: [ClusterLabs] Fuzzy/misleading references to "restart" of a resource

2019-12-04 Thread Andrei Borzenkov
On Thu, Dec 5, 2019 at 1:04 AM Jan Pokorný wrote: > > On 04/12/19 21:19 +0100, Jan Pokorný wrote: > > OTOH, this enforced split of state transitions is perhaps what makes > > the transaction (comprising perhaps countless other interdependent > > resources) serializable and thus feasible at all

Re: [ClusterLabs] Fuzzy/misleading references to "restart" of a resource

2019-12-04 Thread Jan Pokorný
On 04/12/19 21:19 +0100, Jan Pokorný wrote: > OTOH, this enforced split of state transitions is perhaps what makes > the transaction (comprising perhaps countless other interdependent > resources) serializable and thus feasible at all (think: you cannot > nest any further handling -- so as to

[ClusterLabs] Fuzzy/misleading references to "restart" of a resource (Was: When does pacemaker call 'restart'/'force-reload' operations on LSB resource?)

2019-12-04 Thread Jan Pokorný
On 04/12/19 14:53 +0900, Ondrej wrote: > When adding 'LSB' script to pacemaker cluster I can see that > pacemaker advertises 'restart' and 'force-reload' operations to be > present - regardless if the LSB script supports it or not. This > seems to be coming from following piece of code. > >