In our setup it is possible that a resource can automatically recover
and that no human intervention is needed.
Therefore our cluster should be able to recover automatically.
gr.
Johan
On 24-04-13 08:47, Michael Schwartzkopff wrote:
Am Mittwoch, 24. April 2013, 08:35:29 schrieb Johan Huysmans
I'm still investigating what happens in my situation.
So I have a cloned resource, with on-fail set to block.
I configured the failure-timeout to 30s.
An other resource groups depends on the cloned resource (order &
colocation configured)
--> start situation
* scope=status name=fail-count-d_t
I have tried to make this test, because I had the same problem.
Origin:
One node cluster, node int2node1 running with IP address 10.16.242.231, quorum ignore, DC int2node1
[root@int2node1 sysconfig]# crm_mon -1
Last updated: Wed Apr 24 09:49:32 2013
Last change: Wed Apr 24 0
On 2013-04-24T10:37:24, Johan Huysmans wrote:
> --> start situation
> * scope=status name=fail-count-d_tomcat value=0
> * depending resource group running on node
> * crm_mon shows everything ok
>
> --> a failure occurs
> * scope=status name=fail-count-d_tomcat value=1
> * depending resource g
On 24-04-13 13:24, Lars Marowsky-Bree wrote:
On 2013-04-24T10:37:24, Johan Huysmans wrote:
--> start situation
* scope=status name=fail-count-d_tomcat value=0
* depending resource group running on node
* crm_mon shows everything ok
--> a failure occurs
* scope=status name=fail-count-d_tomc
Hello,
I'm trying to configure a 2 node cluster in ubuntu with cman + corosync
+ pacemaker (the use of cman is because it is recommended at pacemaker
quickstart). In order to solve the split brain in the 2 node cluster I'm
using qdisk. For fencing, I'm trying to use fence_scsi and in this poi
bug and crm_report created: http://bugs.clusterlabs.org/show_bug.cgi?id=5021
gr.
Johan
On 24-04-13 13:40, Johan Huysmans wrote:
On 24-04-13 13:24, Lars Marowsky-Bree wrote:
On 2013-04-24T10:37:24, Johan Huysmans wrote:
--> start situation
* scope=status name=fail-count-d_tomcat value=0
* d
Hi Angel,
two hints from my side. As you're working with ubuntu
ask in this list which setup is or will be the best
concerning corosync + pacemaker. I'm pretty sure
(but I really don't know) that you'll get the advice
to drop cman.
When you use cman + pacemaker than stonithing works
as following.
We are building a new web farm to replace our 7 year old system. The old
system used ipvs/ldirectord/heartbeat to implement redundant load
balancers. All web server nodes were physical boxes.
The proposed new system will utilize approximately 24 virtual machines
as web servers. Load balancin
On 13-04-24 01:16 AM, Andrew Beekhof wrote:
>
> Almost certainly you are hitting:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=951340
Yup. The patch posted there fixed it.
> I am doing my best to convince people that make decisions that this is worthy
> of an update before 6.5.
I've a
On Wed, 24 Apr 2013 09:49:00 -0500 Robert Parsons
wrote:
>
> We are building a new web farm to replace our 7 year old system. The
> old system used ipvs/ldirectord/heartbeat to implement redundant load
> balancers. All web server nodes were physical boxes.
>
> The proposed new system will utili
Hi,
what I understand you want split vhost on separate virtual ip adresses and
join all nodes into one cluster?
I dont think it is a good idea in case of web farm, as you mentioned it
wont scale so good. What if traffic on certain vhost (virtual ip) grow up
and you would need to spread it across
Hello everbody,
As suggested by Andreas Mock in a previous thread... what is the best
setup for corosync and pacemaker in a VM running ubuntu 12.04?
In pacemaker's quickstart
(http://clusterlabs.org/quickstart-ubuntu.html) it is best adding cman
to the configuration, but I'm not sure about
Hi,
I have asked about the patents of Paxsos here,
http://www.gossamer-threads.com/lists/linuxha/pacemaker/84309#84309
and now, I would like to just update our investigation about this.
The booth uses Paxos algorithm, it seems to be issued as some US patents..
I believe that the booth is a great
14 matches
Mail list logo