On 15/03/2013, at 11:29 AM, Leon Fauster wrote:
> Am 04.03.2013 um 18:20 schrieb Leon Fauster :
>> okay - recap:
>>
>> 1st. i have this delay where the two nodes dont see each
>> other (after rebooting) and the result are resources running on both
>> nodes while they should only run on one n
Am 04.03.2013 um 18:20 schrieb Leon Fauster :
> okay - recap:
>
> 1st. i have this delay where the two nodes dont see each
> other (after rebooting) and the result are resources running on both
> nodes while they should only run on one node - this will be corrected
> by the cluster it self but
Am 06.03.2013 um 05:14 schrieb Andrew Beekhof :
> On Tue, Mar 5, 2013 at 4:20 AM, Leon Fauster
> wrote:
>>
>> So far all good. I am doing some stress test now and noticed that rebooting
>> one node (n2), that node (n2) will be marked as standby in the cib (shown on
>> the
>> other node (n1)).
>
On Tue, Mar 5, 2013 at 4:20 AM, Leon Fauster wrote:
> Dear list,
>
> just to excuse the triviality - i started to deploy a ha environment
> in a test lab and therefore i do not have much experience.
>
>
>
> i started to setup a 2-node cluster
>
> corosync-1.4.1-15.el6.x86_64
> pacemaker-1.1.8-
Dear list,
just to excuse the triviality - i started to deploy a ha environment
in a test lab and therefore i do not have much experience.
i started to setup a 2-node cluster
corosync-1.4.1-15.el6.x86_64
pacemaker-1.1.8-7.el6.x86_64
cman-3.0.12.1-49.el6.x86_64
with rhel6.3 and then s
