On 11/18/2009 at 08:13 AM, Димитър Бойн wrote:
> Hi,
> I would love to be able to identify when a certain resource cannot run
> anywhere in a cluster anymore.
> A valid scenario would be when my cluster loses quorum -I want to leave it
> "frozen" and mark the failed resources for a Geographi
On Wed, Nov 18, 2009 at 8:22 AM, Nikola Ciprich wrote:
> Hi,
> sure, here it is. I also tried setting compatibility to none, but it did't
> help.
> cheers
> n.
I had a feeling that might be the problem.
You skipped a step :-)
Check out example D.3 of
http://clusterlabs.org/doc/en-US/Pacemaker/
Hi,
sure, here it is. I also tried setting compatibility to none, but it did't help.
cheers
n.
On Mon, Nov 16, 2009 at 03:08:23PM +0100, Andrew Beekhof wrote:
> On Tue, Nov 10, 2009 at 10:28 AM, Nikola Ciprich
> wrote:
> > Hello Andrew et al,
> > few days ago, I asked about pacemaker + corosync +
On 2009-11-13T15:23:20, Yan Gao wrote:
> Minimal:
> Consider the utilization of nodes and resources. While if a resource has
> the same score for several available nodes, do _not_ balance the load.
> That implies that the resources will be concentrated to minimal number of
> nodes.
>
> Balance
Hi,
I would love to be able to identify when a certain resource cannot run anywhere
in a cluster anymore.
A valid scenario would be when my cluster loses quorum -I want to leave it
"frozen" and mark the failed resources for a Geographical failover to a
different site.
#crm_resource crm_resourc
I want to start a single instance of resource A on any node which is running
one or more instances of resource B. And, I don't want to stop resource A until
there are no more instances of resource B on that node. I'm using pacemaker
1.0.5 & openais 0.80.5.
In my case, resource A is a Route, and
Another problem has appeared:
after the reboot of one server I often have a cluster partition and
both servers elect themselves DC.
Even if the partition doesn't appear just after the reboot of one
server (i.e. serverA), if I try to restart corosync on the other
server (i.e. serverB), the
Disabling syslog the problem disappears.
Thank you very much,
Giovanni
On Nov 16, 2009, at 4:51 PM, hj lee wrote:
Hi,
Please disable syslog in openais.conf, and try it again. It seems
this issue is related to fork() call and syslog().
hj
On Fri, Nov 13, 2009 at 1:08 PM, Giovanni Di Mil
On 2009-11-16T15:22:17, Andrew Beekhof wrote:
> I see you checked in cs: 1e3d05823222 Did that fix the issue?
No, that just prevents the subject from being truncated.
I guess I'll file a bug, unless someone confirms that this doesn't occur
for them and I need to look more deeply into my setup?
