On 19/09/2013, at 2:13 AM, Radoslaw Garbacz
radoslaw.garb...@xtremedatainc.com wrote:
Hi,
I have a question regarding the monitor operation on disabled nodes.
I noticed that this operation is called even, when an agent is disabled for a
node. Is it an indented behavior
Yes. We have
On 2013-09-18T12:20:08, Radoslaw Garbacz radoslaw.garb...@xtremedatainc.com
wrote:
Sorry for not being specific.
The agent is meant to run only on a specific node (the head), and by
constraints is disabled on all other nodes.
'pcs constraint' reports:
Location Constraints:
Resource:
On Wed, Sep 18, 2013 at 8:58 PM, Andrew Beekhof and...@beekhof.net wrote:
On 19/09/2013, at 2:13 AM, Radoslaw Garbacz
radoslaw.garb...@xtremedatainc.com wrote:
Hi,
I have a question regarding the monitor operation on disabled nodes.
I noticed that this operation is called even, when an
Hi,
I have a question regarding the monitor operation on disabled nodes.
I noticed that this operation is called even, when an agent is disabled for
a node. Is it an indented behavior or is there something wrong with my
configuration?
Another question is, if it is intended, whether there is any
On 2013-09-18T11:13:46, Radoslaw Garbacz radoslaw.garb...@xtremedatainc.com
wrote:
Hi,
I have a question regarding the monitor operation on disabled nodes.
I noticed that this operation is called even, when an agent is disabled for
a node. Is it an indented behavior or is there something
Sorry for not being specific.
The agent is meant to run only on a specific node (the head), and by
constraints is disabled on all other nodes.
'pcs constraint' reports:
Location Constraints:
Resource: dbx_nfs_head
Enabled on: ip-10-138-14-225
Disabled on: ip-10-151-14-34
Hi,
Seems like 'ocf_is_probe' is the right call in my case.
On Wed, Sep 18, 2013 at 11:17 AM, Lars Marowsky-Bree l...@suse.com wrote:
On 2013-09-18T11:13:46, Radoslaw Garbacz
radoslaw.garb...@xtremedatainc.com wrote:
Hi,
I have a question regarding the monitor operation on disabled
