On 24/05/2013, at 4:35 PM, Andrey Groshev <gre...@yandex.ru> wrote:
>
>
> 24.05.2013, 01:39, "Andrew Beekhof" <and...@beekhof.net>:
>> On 24/05/2013, at 3:49 AM, Andrey Groshev <gre...@yandex.ru> wrote:
>>
>>> 23.05.2013, 02:51, "Andrew Beekhof" <and...@beekhof.net>:
>>>> On 22/05/2013, at 10:25 PM, Groshev Andrey <gre...@yandex.ru> wrote:
>>>>> Hello,
>>>>>
>>>>> I try build cluster with 2 nodes + one quorum node (without pacemaker).
>>>> This is the root of your problem.
>>>>
>>>> Your config has:
>>>>> service {
>>>>> name: pacemaker
>>>>> ver: 1
>>>>> }
>>> Well, I tested and "service version 0" and CMAN
>>
>> Do not do this. If you want to use CMAN, remove the service {} block
>> completely.
>
> Of course , I tested their separately.
> But not fully tested "service version 0".
> I repeated the test today - his behavior too as same "version 1".
I'm sorry, I can't parse this at all.
Please delete corosync.conf and follow
http://clusterlabs.org/quickstart-redhat.html
> Maybe the problem described in the official documentation?
>
>>> - it work.
>>> But I did not find in the documentation description of this option,
>>> although it was nearly six months each weekday reread "cluster from
>>> scratch" and other documens. :)
>>> Where can I find this documentation?
>>>
>>> I was still the next question - about hangs elections.
>>> But I read your blog entirely ...
>>> That is, If plugins are buggy and no one to repair them will not, then
>>> have three choices:
>>> 1. use service version of "0"
>>
>> This is still the plugin
>>
>>> 2. use CMAN
>>> 3. Use corosync 2.x.
>>> I understood you correctly?
>>>> So even though you thought you only started corosync, you also started
>>>> part of pacemaker.
>>>> Specifically the part of pacemaker that gets loaded into corosync to
>>>> provides membership and _quorum_ APIs to the other daemons.
>>>>
>>>> The output from corosync-quorumtool is completely irrelevant to pacemaker
>>>> in this kind of setup.
>>>>
>>>> Since you're on a RHEL derivative, I highly suggest using Pacemaker with
>>>> CMAN (and updating to 6.4 while you're there :-).
>>>> In this case, the pacemaker daemons DO see the same quorum as
>>>> corosync-quorumtool and your expectations would be correct.
>>>> snip .....
>>> Unfortunately (or fortunately) I try not to focus on one specific
>>> distribution.
>>> I have to work with CentOS, and with many other Linux distributions.
>>> I am interested in your opinion, what will happen to the clusters in
>>> openSUSE?
>>>
>>> Regards Andrey Groshev.
>>>
>>> _______________________________________________
>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>>
>>> Project Home: http://www.clusterlabs.org
>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>>> Bugs: http://bugs.clusterlabs.org
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
