On Fri, Oct 7, 2011 at 2:50 PM, Andrew Beekhof wrote:
> On Fri, Oct 7, 2011 at 2:21 PM, Andrew Beekhof wrote:
>> On Fri, Oct 7, 2011 at 11:39 AM, Andrew Beekhof wrote:
>>> On Fri, Sep 30, 2011 at 3:44 PM, Junko IKEDA
>>> wrote:
Hi,
sorry for the confusion.
Pacemaker 1.
On Fri, Oct 7, 2011 at 2:21 PM, Andrew Beekhof wrote:
> On Fri, Oct 7, 2011 at 11:39 AM, Andrew Beekhof wrote:
>> On Fri, Sep 30, 2011 at 3:44 PM, Junko IKEDA wrote:
>>> Hi,
>>>
>>> sorry for the confusion.
>>>
>>> Pacemaker 1.0.10 OK(group resource can failover)
>>> Pacemaker 1.0.11 NG(gruop re
On Fri, Oct 7, 2011 at 11:39 AM, Andrew Beekhof wrote:
> On Fri, Sep 30, 2011 at 3:44 PM, Junko IKEDA wrote:
>> Hi,
>>
>> sorry for the confusion.
>>
>> Pacemaker 1.0.10 OK(group resource can failover)
>> Pacemaker 1.0.11 NG(gruop resource just stop, can not failover)
>> Pacemaker 1.1 <- the late
Hi, I'm from Japan, in trouble.
In the case blow, server which was primary
sometimes do not run drbd/heartbeat.
Server A(primary), Server B(secondary) is running.
Shutdown A and immediately Shutdown B.
Switch on only A, it dose not run drbd/heartbeat.
It may happen when one server was broken.
I'
On Fri, Sep 30, 2011 at 3:44 PM, Junko IKEDA wrote:
> Hi,
>
> sorry for the confusion.
>
> Pacemaker 1.0.10 OK(group resource can failover)
> Pacemaker 1.0.11 NG(gruop resource just stop, can not failover)
> Pacemaker 1.1 <- the latest hg (gruop resource just stop, can not failover)
We've actuall
On Wed, Oct 5, 2011 at 3:55 PM, raki wrote:
> Hi Andrew
> Thanks for replying back to my question.
> We had tried even the option you had mentioned , but we got the same error,
> The work around solution we followed is , as soon as we cleaned up the
> ha-debug
> log files which is more than 2Gig
On Fri, Oct 7, 2011 at 5:01 AM, gustavo panizzo wrote:
> i fix my ordering problems using fully explicit order "chains"
>
> colocation col_db0005 +inf: HASI ora-bkp vgoradb vgoralog db0005-storage
> db0005-db db0005-ip
> order ord_db0005 +inf: HASI ora-bkp vgoradb vgoralog db0005-storage db0005-
On Thu, Oct 6, 2011 at 2:47 AM, Proskurin Kirill
wrote:
> On 10/05/2011 04:19 AM, Andrew Beekhof wrote:
>>
>> On Mon, Oct 3, 2011 at 5:50 PM, Proskurin Kirill
>> wrote:
>>>
>>> On 10/03/2011 05:32 AM, Andrew Beekhof wrote:
>
> corosync-1.4.1
> pacemaker-1.1.5
> pacemaker runs wit
On Thu, Oct 6, 2011 at 10:53 PM, Nick Khamis wrote:
> On no! Sorry about the misunderstanding Andrew. What I meant was, we would
> like
> to build a production pacemaker VM cluster. An now with pci
> passthrough, is it possible
> for VMs to use the stonith device installed on the host.
I've neve
On Thu, Oct 6, 2011 at 1:53 AM, Lars Marowsky-Bree wrote:
> On 2011-10-03T11:10:13, Andrew Beekhof wrote:
>
>> Based on Boston last year, I imagine the conversations will last right
>> up until Lars starts presenting his talk on Friday afternoon.
>> People came and went at random, and if someone
On Oct 6, 2011, at 5:01 PM, Florian Haas wrote:
> On 2011-10-06 22:32, Prakash Velayutham wrote:
>> My OCFS2 file system is being used for MySQL database (failover setup)
>
> What for? A MySQL database clearly does not require OCFS2 for failover
> capability. With Pacemaker, MySQL HA needs can be
On 2011-10-06 22:32, Prakash Velayutham wrote:
> My OCFS2 file system is being used for MySQL database (failover setup)
What for? A MySQL database clearly does not require OCFS2 for failover
capability. With Pacemaker, MySQL HA needs can be easily met using
either shared storage, or single-Primar
Hello all,
I have pretty much tested most of the failure scenarios (with respect to the
cluster stack/network/hardware etc.) with my 2-node Corosync/Pacemaker/OCFS2
cluster and it has been satisfactory. Now, I am turning my attention to OCFS2
itself and it pretty much failed right away. My OCFS
i fix my ordering problems using fully explicit order "chains"
colocation col_db0005 +inf: HASI ora-bkp vgoradb vgoralog db0005-storage
db0005-db db0005-ip
order ord_db0005 +inf: HASI ora-bkp vgoradb vgoralog db0005-storage db0005-db
db0005-ip
it really works, crm configure verify give OK.
b
Possible bug with mandatory ordering involving stateful (i.e.
master-slave) resources
I have a 2-node cluster (we are running the SLES 11 HA extension, so the
pacemaker version is 1.1.2) in which a master-slave resource is
dependent on a clone resource via a mandatory ordering constraint. From
On no! Sorry about the misunderstanding Andrew. What I meant was, we would like
to build a production pacemaker VM cluster. An now with pci
passthrough, is it possible
for VMs to use the stonith device installed on the host. If not, is
lib-virt and fence_virsh
safe enough for production?
Another q
16 matches
Mail list logo
