> On 15 Jan 2015, at 12:43 am, Dmitry Koterov wrote:
>
> Sorry!
>
> Pacemaker 1.1.10
> Corosync 2.3.30
>
> BTW I removed quorum.two_node:1 from corosync.conf, and it helped! Now
> isolated node stops its services in 3-node cluster. Was it the right solution?
Yes. 'quorum.two_node:1' is only
Sorry!
Pacemaker 1.1.10
Corosync 2.3.30
BTW I removed quorum.two_node:1 from corosync.conf, and it helped! Now
isolated node stops its services in 3-node cluster. Was it the right
solution?
On Wednesday, January 14, 2015, Andrew Beekhof wrote:
>
> > On 14 Jan 2015, at 12:06 am, Dmitry Koterov
> On 14 Jan 2015, at 12:06 am, Dmitry Koterov wrote:
>
>
> > Then I see that, although node2 clearly knows it's isolated (it doesn't see
> > other 2 nodes and does not have quorum)
>
> we don't know that - there are several algorithms for calculating quorum and
> the information isn't includ
> > Then I see that, although node2 clearly knows it's isolated (it doesn't
> see other 2 nodes and does not have quorum)
>
> we don't know that - there are several algorithms for calculating quorum
> and the information isn't included in your output.
> are you using cman, or corosync underneath pa
Hi,
On Mon, Jan 12, 2015 at 07:42:10PM +0300, Dmitry Koterov wrote:
> Hello.
>
> I have 3-node cluster managed by corosync+pacemaker+crm. Node1 and Node2
> are DRBD master-slave, also they have a number of other services installed
> (postgresql, nginx, ...). Node3 is just a corosync node (for quo
Dmitry Koterov napisał:
>Hello.
>
>I have 3-node cluster managed by corosync+pacemaker+crm. Node1 and
>Node2
>are DRBD master-slave, also they have a number of other services
>installed
>(postgresql, nginx, ...). Node3 is just a corosync node (for quorum),
>no
>DRBD/postgresql/... are installed
> On 13 Jan 2015, at 7:56 am, Dmitry Koterov wrote:
>
> 1. install the resource related packages on node3 even though you never want
> them to run there. This will allow the resource-agents to verify the resource
> is in fact inactive.
>
> Thanks, your advise helped: I installed all the service
> On 13 Jan 2015, at 4:25 am, David Vossel wrote:
>
>
>
> - Original Message -
>> Hello.
>>
>> I have 3-node cluster managed by corosync+pacemaker+crm. Node1 and Node2 are
>> DRBD master-slave, also they have a number of other services installed
>> (postgresql, nginx, ...). Node3 is j
>
> 1. install the resource related packages on node3 even though you never
> want
> them to run there. This will allow the resource-agents to verify the
> resource
> is in fact inactive.
Thanks, your advise helped: I installed all the services at node3 as well
(including DRBD, but without it con
- Original Message -
> Hello.
>
> I have 3-node cluster managed by corosync+pacemaker+crm. Node1 and Node2 are
> DRBD master-slave, also they have a number of other services installed
> (postgresql, nginx, ...). Node3 is just a corosync node (for quorum), no
> DRBD/postgresql/... are ins
Hello.
I have 3-node cluster managed by corosync+pacemaker+crm. Node1 and Node2
are DRBD master-slave, also they have a number of other services installed
(postgresql, nginx, ...). Node3 is just a corosync node (for quorum), no
DRBD/postgresql/... are installed at it, only corosync+pacemaker.
But
11 matches
Mail list logo
