re="openais" \
expected-quorum-votes="4" \
no-quorum-policy="ignore" \
stonith-enabled="false" \
symmetric-cluster="true" \
resource-stickiness="1"
On Thu, Mar 10, 2011 at 12:15 PM, Andrew Beekho
Hi,
I have the following scenario:
- resource 1 runs on Node A
- resource 2 should be started on Node B if resource 1 is running on Node A
- if resource 1 is not running on Node A, resource 2 should be stopped
and resource 3 started
What attribute is set on Node A, that exactly tells me that the
Hello,
They are 2 groups with identical resources, each group is assigned to
its own node. Everything is fine for the first startup, but if one
node stops or starts, the troubles starts.
I guess my problem are the more or less identical resources, it looks
like if a node joins the resources are
Hello Lars,
thanks a lot for your hint. Double negation is the smartest way ;)
regards,
Thomas
On Mon, Feb 28, 2011 at 9:36 PM, Lars Ellenberg
wrote:
> On Mon, Feb 28, 2011 at 07:59:30PM +0100, Thomas Baumann wrote:
>> Hello,
>>
>> I tried to stick a group fixed to
Hello,
I tried to stick a group fixed to one node, but if the service
corosync is stopped the group is jumping to the next node.
Here is my configuration:
How I can configure that behavior that my group is running only in
that specific host ?
regards,
Thomas
