Re: [ClusterLabs] How Pacemaker reacts to fast changes of the same parameter in configuration

2016-11-09 Thread Kostiantyn Ponomarenko
>> Actually you would need the reduced stickiness just during the stop phase - right. Oh, that is good to know. While I can reduce time when waiting for only "stop" commands to finish, I don't think that this is worth it. Because this doesn't address my problem fully. Does that mean that the

Re: [ClusterLabs] How Pacemaker reacts to fast changes of the same parameter in configuration

2016-11-09 Thread Klaus Wenninger
On 11/09/2016 05:30 PM, Kostiantyn Ponomarenko wrote: > When one problem seems to be solved, another one appears. > Now my script looks this way: > > crm --wait configure rsc_defaults resource-stickiness=50 > crm configure rsc_defaults resource-stickiness=150 > > While now I am sure that

Re: [ClusterLabs] Change resource-stickiness during working hours with crmsh

2016-11-09 Thread Kostiantyn Ponomarenko
Thank you for the answer, Kristoffer. Thank you, Kostia On Sat, Nov 5, 2016 at 10:55 PM, Kristoffer Grönlund wrote: > Kostiantyn Ponomarenko writes: > > > Hi, > > > > I was reading about changing default resource stickiness based on time >

Re: [ClusterLabs] How Pacemaker reacts to fast changes of the same parameter in configuration

2016-11-09 Thread Kostiantyn Ponomarenko
When one problem seems to be solved, another one appears. Now my script looks this way: crm --wait configure rsc_defaults resource-stickiness=50 crm configure rsc_defaults resource-stickiness=150 While now I am sure that transactions caused by the first command won't be aborted, I see

[ClusterLabs] Antw: Re: Antw: Resources wont start on new node unless it is the only active node

2016-11-09 Thread Ulrich Windl
>>> Ken Gaillot schrieb am 09.11.2016 um 16:43 in >>> Nachricht : > On 11/09/2016 02:33 AM, Ulrich Windl wrote: > Ryan Anstey schrieb am 08.11.2016 um 19:54 in > Nachricht >>> Log when running

Re: [ClusterLabs] Antw: Resources wont start on new node unless it is the only active node

2016-11-09 Thread Ken Gaillot
On 11/09/2016 02:33 AM, Ulrich Windl wrote: Ryan Anstey schrieb am 08.11.2016 um 19:54 in Nachricht >> Log when running cleaning up the resource on the OLD node: >> >> Nov 08 09:21:18 h3 crmd[11394]: warning: No match for shutdown action on >> 167838209 > > This

[ClusterLabs] no final newline from "crm configure show"

2016-11-09 Thread Ulrich Windl
Hi! I just found a minor problem when redirecting the output of "crm configure show" to a file for archiving purposes: If you use diff to compare two files, diff complains about a missing newline (especially after having edited the other file with vim). For XML output the final newline is

Re: [ClusterLabs] Antw: Resources wont start on new node unless it is the only active node

2016-11-09 Thread Klaus Wenninger
On 11/09/2016 09:33 AM, Ulrich Windl wrote: Ryan Anstey schrieb am 08.11.2016 um 19:54 in Nachricht > : >> I've been running a ceph cluster with pacemaker for a few months now. >> Everything has

[ClusterLabs] Waiting in crm shell scripts

2016-11-09 Thread Ulrich Windl
(subject changed) >>> Dejan Muhamedagic schrieb am 08.11.2016 um 21:19 in Nachricht <20161108201951.GA4946@tuttle.homenet>: [...] > crmsh has an option (-w) to wait for the PE to settle after > committing configuration changes. I didn't know that, but thinking about

Re: [ClusterLabs] Antw: Re: Antw: Re: Antw: Pacemaker 1.1.16 - Release Candidate 1

2016-11-09 Thread Vladislav Bogdanov
09.11.2016 10:59, Ulrich Windl wrote: Ken Gaillot schrieb am 08.11.2016 um 18:16 in Nachricht <92c4a0de-33ce-cdc2-a778-17fddfe63...@redhat.com>: On 11/08/2016 03:02 AM, Ulrich Windl wrote: [...] The user is responsible for choosing meaningful values. For example, if