>>> Klaus Wenninger schrieb am 09.11.2016 um 17:42 in
Nachricht <80c65564-b299-e504-4c6c-afd0ff86e...@redhat.com>:
> 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 rs
Hi again
Sorry for missing the omission of the master role within the colocation
constraint.
I added it - but unfortunately still no success.
(In the meantime I added 2 additional filesystem resources on top of the
NFSServer, but that should not change anything regarding the root problem
>> 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 real
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 tr
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
> > rules, but I didn't find a way to set using crmsh. I
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 ano
>>> 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 cleaning up the resource on the OLD node:
>>>
>>> Nov 08 09:21:18 h3 crmd[11394]: warning: No matc
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 indicates a node commun
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 there
On 11/09/2016 01:09 PM, Ulrich Windl wrote:
> (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
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 been working normally, but when I added a fourth node it
>> won't work like the others, even
(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 scripting, it would be more h
Hi!
Reading the manual page of crm shell (crmsh-2.1.2+git132.gbc9fde0-13.1 of
LSES11 SP4), I think that it does ot yet support the "reload" operation. Is
that correct?
Ulrich
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mail
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
node-health-base is +10
>>> 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 been working normally, but when I added a fourth node it
> won't work like the others, even though their OS is the same and the
Welcome to th
>>> 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
> node-health-base is +10 but yellow is -15, then any y
16 matches
Mail list logo
