On Wed, Jan 23, 2013 at 2:21 PM, Brian J. Murrell wrote:
> OK. So you have a corosync cluster of nodes with pacemaker managing
> resources on them, including (of course) STONITH.
>
> What's the best/proper way to shut down a node, say, for maintenance
> such that pacemaker doesn't go trying to "f
Hi,
On Wed, Jan 23, 2013 at 11:28 PM, Brian J. Murrell
wrote:
> On 13-01-23 03:32 AM, Dan Frincu wrote:
>> Hi,
>
> Hi,
>
>> I usually put the node in standby, which means it can no longer run
>> any resources on it. Both Pacemaker and Corosync continue to run, node
>> provides quorum.
>
> But a n
Indeed ... thats the correct behavior as it was still an active cluster
member, it just happens to not be running any resources as its in standby.
If you shutdown (gracefully) openais and its showing happily as 'offline'
on the remaining node(s) then all will be well.
On 24 January 2013 10:28, Br
On 13-01-23 03:32 AM, Dan Frincu wrote:
> Hi,
Hi,
> I usually put the node in standby, which means it can no longer run
> any resources on it. Both Pacemaker and Corosync continue to run, node
> provides quorum.
But a node in standby will still be STONITHed if it goes AWOL. I put a
node in stan
I've asked this before, you should be able to search the question.
Essentially if pacemaker is shut down gracefully the remaining nodes are
happy to leave it be.
Generally I standby the node and then stop openais ... I have been caught
out once bringing a node back online which was in standby. The
@gmail.com>>
Antworten an: The Pacemaker cluster resource manager
mailto:pacemaker@oss.clusterlabs.org>>
Datum: Wednesday, January 23, 2013 9:32 AM
An: The Pacemaker cluster resource manager
mailto:pacemaker@oss.clusterlabs.org>>
Betreff: Re: [Pacemaker] best/proper way to shut down a n
Hi,
On Wed, Jan 23, 2013 at 5:21 AM, Brian J. Murrell wrote:
> OK. So you have a corosync cluster of nodes with pacemaker managing
> resources on them, including (of course) STONITH.
>
> What's the best/proper way to shut down a node, say, for maintenance
> such that pacemaker doesn't go trying
OK. So you have a corosync cluster of nodes with pacemaker managing
resources on them, including (of course) STONITH.
What's the best/proper way to shut down a node, say, for maintenance
such that pacemaker doesn't go trying to "fix" that situation and
STONITHing it to try to bring it back up, et
