Am Dienstag, 13. April 2010 08:35:19 schrieb bi...@antworte.me:
> Last Question on this.
> Is it really correct and possible that the master AND backup run on all
> nodes at the same time with same syncid (as below) to get here no SPOF?
> That means master AND backup are like a "clone" resource and
Last Question on this.
Is it really correct and possible that the master AND backup run on all
nodes at the same time with same syncid (as below) to get here no SPOF?
That means master AND backup are like a "clone" resource and run on all
nodes.
Tom.
On Thu, 25 Feb 2010 11:53:59 +0100, Michael
On Mon, Apr 12, 2010 at 12:41 PM, Alain.Moulle wrote:
> Because I need that at the very first time I do //etc/init.d/corosync
> start/ the time to be available
> on only one node of the HA cluster_ is reduced to minimum_, and to get
> this, I need
> to have values of 5s for both (I've tested after
Hi Brian,
here are some patches to test.
I have only lightly tested them to the extent that they
compile and appear to configure a valid service.
You can enable one packet scheduling (OPS) by passing the -o option
to ipvsadm when creating a virtual service.
e.g.
# ipvsadm -A -u
Greetings All,
This is to announce version 0.3.3 of Hawk, a web-based GUI for
Pacemaker HA clusters. Noticeable changes from version 0.3.1
include:
- Port number is now 7630 (registered with IANA)
- Shows Master/Slave sets (but currently just shows children as
"started")
- Added confirmation p
Because I need that at the very first time I do //etc/init.d/corosync
start/ the time to be available
on only one node of the HA cluster_ is reduced to minimum_, and to get
this, I need
to have values of 5s for both (I've tested after modification via CRM
API and stop and start again, it starts
Hi Dejan,
thank you!
> Hi,
>
> On Fri, Apr 09, 2010 at 09:18:09AM +0200, Zausel wrote:
>> Hi,
>>
>> I updated my pacemaker on my SLES 11 system. after that my op
>> monitor for the ocf:heartbeat:mysql resource works only at the
>> first time. after some minutes the monitor dosen't check the
>> d
On Mon, Apr 12, 2010 at 10:37 AM, Alain.Moulle wrote:
> Hi,
>
> Thanks for your response Andrew.
>
> Further questions :
> I would like to change /*cluster-delay*/ and /*dc-deadtime*/ default
> values in sources,
why?
> I found cluster-delay default value in common.c in pacemaker pengine part :
Hi,
Thanks for your response Andrew.
Further questions :
I would like to change /*cluster-delay*/ and /*dc-deadtime*/ default
values in sources,
I found cluster-delay default value in common.c in pacemaker pengine part :
pacemaker/lib/pengine/common.c :
{ "cluster-delay", "transition_idle_ti
