Hi,
I've noticed the same type of behavior, however in a different context,
my setup includes 3 drbd devices and a group of resources, all have to
run on the same node and move together to other nodes. My issue was with
the first resource that required access to a drbd device, which was the
On 13 October 2010 09:48, Dan Frincu dfri...@streamwide.ro wrote:
Hi,
I've noticed the same type of behavior, however in a different context, my
setup includes 3 drbd devices and a group of resources, all have to run on
the same node and move together to other nodes. My issue was with the
Hi,
Pavlos Parissis wrote:
On 12 October 2010 20:00, Dan Frincu dfri...@streamwide.ro wrote:
Hi,
Lars Ellenberg wrote:
On Mon, Oct 11, 2010 at 03:50:01PM +0300, Dan Frincu wrote:
Hi,
Dejan Muhamedagic wrote:
Hi,
On Sun, Oct 10, 2010 at 10:27:13PM +0300, Dan Frincu wrote:
Hi,
I
On 13 October 2010 10:50, Dan Frincu dfri...@streamwide.ro wrote:
From what I see you have a dual primary setup with failover on the third
node, basically if you have one drbd resource for which you have both
ordering and collocation, I don't think you need to improve it, if it
ain't broke,
Pavlos Parissis wrote:
On 13 October 2010 10:50, Dan Frincu dfri...@streamwide.ro wrote:
From what I see you have a dual primary setup with failover on the third
node, basically if you have one drbd resource for which you have both
ordering and collocation, I don't think you need to improve
--- 10年10月13日,周三, pacemaker-requ...@oss.clusterlabs.org
pacemaker-requ...@oss.clusterlabs.org 写道:
Send Pacemaker mailing list submissions to
pacemaker@oss.clusterlabs.org
To subscribe or unsubscribe via the World Wide Web, visit
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Hi,
Yes, it sometime needs to be killed manually because the process hangs
and the restart operation never seems to end. Yet another reason to upgrade.
All,
Question: given the fact that this type of software usually gets
installed on a platform once and then usually goes into service for
On 11 October 2010 11:16, Pavlos Parissis pavlos.paris...@gmail.com wrote:
On 8 October 2010 09:29, Andrew Beekhof and...@beekhof.net wrote:
On Fri, Oct 8, 2010 at 8:34 AM, Pavlos Parissis
pavlos.paris...@gmail.com wrote:
On 8 October 2010 08:29, Andrew Beekhof and...@beekhof.net wrote:
On
Hi
I reboot my node, and it appears
node2 pingd: [3932]: info: stand_alone_ping: Node 192.168.10.100 is unreachable
(read)
and the node could not start
192.168.10.100 is ib network I will start ib after the node start, so do you
have any idea let the node start first?Thanks very much.:-)
Hi
I reboot my node, and it appears
node2 pingd: [3932]: info: stand_alone_ping: Node 192.168.10.100 is unreachable
(read)
and the node could not start
192.168.10.100 is ib network I will start ib after the node start, so do you
have any idea let the node start first?Thanks very much.:-)
10 matches
Mail list logo