On 10/19/2011 01:50 PM, Alan Robertson wrote:
> Hi,
>
> I have an application where having a 12-node cluster with about 250
> resources would be desirable.
>
> Is this reasonable? Can Pacemaker+Corosync be expected to reliably
> handle a cluster of this size?
>
> If not, what is the current rec
Hi,
I have an application where having a 12-node cluster with about 250
resources would be desirable.
Is this reasonable? Can Pacemaker+Corosync be expected to reliably
handle a cluster of this size?
If not, what is the current recommendation for maximum number of nodes
and resources?
Hi,
I've seen a very similar problem in a recent release. In fact, I'm in
the process of reproducing it so that it can be properly logged and so
on. When I get the right data for the bug report, I'll attach it to the
bug.
FWIW: I'm pretty sure that the signal was properly received by attrd
Hi,
On Wed, Oct 19, 2011 at 09:48:24AM +0300, sagar.shi...@tieto.com wrote:
> Hi,
>
> Can anyone please share the link for the download, as I am not able to found
> the pacemaker version 1.1.7 on Git.
The latest Pacemaker release is 1.1.6.
Thanks,
Dejan
> Following is the link for the pacema
On 2011-06-12 23:10, Viacheslav Biriukov wrote:
We have the situation when our mysql server hangs. So it begins to
restart. But it takes a while. So we need fast switching for the other
mysql master node.
hi!
do i correctly understand that this is only beneficial in a master-
master setup? a
we might need marek on this one because i did not implement
the master/slave logic and am not using it for multiple slaves.
marek, can you please comment on this?
thanks,
raoul
On 2011-08-29 23:08, Michael Szilagyi wrote:
Did some more testing and figured I would add that even Slave resources
On 2011-10-19 15:37, Raoul Bhatia [IPAX] wrote:
Please try the latest revision of this ra and get back to me if this
problem is still existing.
https://github.com/raoulbhatia/resource-agents/raw/master/heartbeat/mysql
in case you're using an old version of the ocf-functions,
you might need to
On 2011-10-07 10:34, raki wrote:
Hi Andrew
Hi Andrew
We had installed Heartbeat/Pacemaker on two Unix(Centos 5.0.2 Machines)
The RPM's we had used for installing Heartbeat ad Pacemaker are
heartbeat-3.0.3-2.3.el5.i386.rpm
pacemaker-1.0.9.1-1.15.el5.i386.rpm
Please find the crm(cluster resou
Hi all,
I've just succesfully compiled the ClusterLabs-resource-agents-v3.9.2-65-
g46c6990(.zip) from: https://github.com/ClusterLabs/resource-agents, configured
with:
./configure --prefix=$PREFIX --localstatedir=/var --sysconfdir=/etc --enable-
fatal-warnings=no
After "make" I've tried "make rpm
The allow-migrate was just something I was trying, and as you point out
produced that error unimplemented feature. Without the allow-migrate
option I just get "exec timeout error" which is doubly as frustrating,
where its simply failing to unload the ip addresses from the failed
node. It knows it's
Hi,
On Wed, Oct 19, 2011 at 8:12 AM, wrote:
> thank you
> Andreas
>
> Now I am facing core dump issue with
> corosync-1.4.2
> cluster-glue-1.0.7
> pacemaker-1.0.11
>
To report a crash of corosync, please follow this guide =>
http://corosync.org/doku.php?id=faq:crash
Regards,
Dan
> In many sce
On 10/19/2011 07:12 AM, manish.gu...@ionidea.com wrote:
> thank you
> Andreas
>
> Now I am facing core dump issue with
> corosync-1.4.2
> cluster-glue-1.0.7
> pacemaker-1.0.11
>
> In many scenario I getting core dump during corosync start operation for 2
> rings like.
>
> 1. Configure 2 rings ri
12 matches
Mail list logo
