>> Are you saying that if a server loses its disk, it will transparently
>> write to the secondary server without any need to failover at all?
>
> Yes. As long as it still has a network connection to the peer, of course.
>
>> WOW. I never knew DRBD did this. This is a _fantastic_ feature :)
>
> Wel
2010/8/27 Florian Haas :
> On 2010-08-27 10:31, jimbob palmer wrote:
>> 2010/8/27, Florian Haas :
>>> On 2010-08-26 16:43, jimbob palmer wrote:
>>>> How can I configure pacemaker to failover when the primary node goes
>>> diskless?
>>>>
>>&
2010/8/27, Florian Haas :
> On 2010-08-26 16:43, jimbob palmer wrote:
>> How can I configure pacemaker to failover when the primary node goes
> diskless?
>>
>> Many thanks.
>
> man drbd.conf
>
> Look for the local-io-error handler and the on-io-error option.
>
The ftp connection is in the ram of the machine that dies, so for this
to work you'd need to synchronise state to the other machine the whole
time. I don't know of a cluster aware ftp server that can do this.
2010/8/26 :
> Hi There,
>
>
>
> I have followed the guide in “Clusters from Scratch” wri
How can I configure pacemaker to failover when the primary node goes diskless?
Many thanks.
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting
What is the syntax to start a resource before drbd becomes primary?
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Silly me. Thanks.
2010/3/16 Florian Haas :
> crm configure property no-quorum-policy=ignore
>
> Cheers,
> Florian
>
> On 2010-03-16 17:21, jimbob palmer wrote:
>> How can I configure a two node master slave cluster to continue
>> working when one node is powered o
How can I configure a two node master slave cluster to continue
working when one node is powered off?
I would like it to keep working even if the secondary node is dead,
offline or on standby.
Thanks.
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs
2010/2/16 Dominik Klein :
> jimbob palmer wrote:
>> Hello,
>>
>> I have a cluster that is all working perfectly. Time to break it.
>>
>> This is a two node master/slave cluster with drbd. Failover between
>> the nodes works backwards and forwards. Every
Hello,
I have a cluster that is all working perfectly. Time to break it.
This is a two node master/slave cluster with drbd. Failover between
the nodes works backwards and forwards. Everything is happier than a
well fed cat.
I wanted to see what would happen if the drbd device couldn't be
mounted
2010/2/10 Andrew Beekhof :
> On Mon, Feb 8, 2010 at 3:20 PM, jimbob palmer wrote:
>> 2010/2/8 jimbob palmer :
>>>> I get this message, but I don't think the pacemaker part is working at all.
>>>>
>>>> If I run crm_mon, I get "Attemping co
2010/2/8 Andrew Beekhof :
> On Mon, Feb 8, 2010 at 4:36 PM, jimbob palmer wrote:
>>>>> I've searched the mailing lists for qdisk, quorum disk and quorum
>>>>> partition but found nothing.
>>>>>
>>>>> How can I configure a two n
>>> I've searched the mailing lists for qdisk, quorum disk and quorum
>>> partition but found nothing.
>>>
>>> How can I configure a two node cluster to use
>>
>> a quorum disk so that the node that can see the disk will keep resources?
>
> We dont have support for qdisk.
> Check out no-quorum-poli
2010/2/8 jimbob palmer :
> Hello,
>
> I've searched the mailing lists for qdisk, quorum disk and quorum
> partition but found nothing.
>
> How can I configure a two node cluster to use
a quorum disk so that the node that can see the disk will
Hello,
I've searched the mailing lists for qdisk, quorum disk and quorum
partition but found nothing.
How can I configure a two node cluster to use
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pac
2010/2/8 jimbob palmer :
>> I get this message, but I don't think the pacemaker part is working at all.
>>
>> If I run crm_mon, I get "Attemping connection to the cluster.."
>> So it looks broken - but the logs show successful node joining and
&g
> I get this message, but I don't think the pacemaker part is working at all.
>
> If I run crm_mon, I get "Attemping connection to the cluster.."
> So it looks broken - but the logs show successful node joining and
> exiting as I start and stop openais on both nodes. So something is
> w
>> pacemaker kind of starts. Using your guide (well written btw - the use
>> of environment variables is clever) Clusters From Scratch*, everything
>> looks like it's working apart from "AIS Executive Service" missing
>> from /var/log/messages - is this normal?
>
> Should be fine, corosync has a di
>>> Maybe its right, does it run?
>>
>> Yum? Unless I force architecture to 64-bit the packages conflict with
>> each other.
>
> I meant pacemaker ;-)
pacemaker kind of starts. Using your guide (well written btw - the use
of environment variables is clever) Clusters From Scratch*, everything
look
2010/2/4 Andrew Beekhof :
> On Thu, Feb 4, 2010 at 4:12 PM, jimbob palmer wrote:
>> Forcing the architecture gets an install:
>
> [snip]
>
>> # lsb_release -a
>> LSB Version:
>> :core-3.1-amd64:core-3.1-ia32:core-3.1-noarch:graphics-3.1-amd64:graphics-3.1-ia3
2009/12/15 Andrew Beekhof :
> On Mon, Dec 14, 2009 at 12:47 PM, jimbob palmer
> wrote:
>> 2009/12/10 Andrew Beekhof :
>>
>>>> 2. Are there plans to make pacemaker work with the 64-bit version of
>>>> RHEL out of the box?
>>>
>>> I t
2009/12/10 Andrew Beekhof :
>> 2. Are there plans to make pacemaker work with the 64-bit version of
>> RHEL out of the box?
>
> I thought it did. All my machines are 64-bit so that's all I'm using.
> Perhaps this is the problem though:
> pacemaker-1.0.6-1.el5.i386 (clusterlabs)
> Why are you tr
Hello,
I am planning an upgrade from heartbeat to pacemaker. The pacemaker is
on new hardware.
I installed RHEL5.4 64-bit and visited the pacemaker website.
The pacemaker website lists the epel-5 repo as the source for
pacemaker software, but the mailing list and elsewhere hints at the
Suse RHEL
23 matches
Mail list logo
