Hi Vishal,
do you have a effective recipe to test if the rabbitmq's HA ?
I've three instances of it; I've also nova, cinder and neutron configured with rabbit_ha_queues = true.

Just restarting a rabbit instance seems not to be sufficient to test a real case scenario, is it ?

any advice ?

thanks,

    Alvise

On 28/07/2015 09:46, vishal yadav wrote:
You're welcome :)

On Tue, Jul 28, 2015 at 1:15 PM, Alvise Dorigo <[email protected] <mailto:[email protected]>> wrote:

    thank you very much Vishal.

        A.


    On 28/07/2015 09:41, vishal yadav wrote:
    >> "ha_all" vs. "HA".
    >> which one is correct ?

    That's the policy name, you can name anything...

    Excerpt from 'man rabbitmqctl'
    ...
    set_policy [-p vhostpath] {name} {pattern} {definition} [priority]
               Sets a policy.

               name
                   The name of the policy.

               pattern
                   The regular expression, which when matches on a
    given resources causes the policy to apply.

               definition
                   The definition of the policy, as a JSON term. In
    most shells you are very likely to need to quote this.

               priority
                   The priority of the policy as an integer,
    defaulting to 0. Higher numbers indicate greater precedence.
    ...

    Regards,
    Vishal


    On Tue, Jul 28, 2015 at 12:47 PM, Alvise Dorigo
    <[email protected] <mailto:[email protected]>> wrote:

        Hi,
        I read these two documents:

        
http://docs.openstack.org/high-availability-guide/content/_configure_rabbitmq.html

        https://www.rdoproject.org/RabbitMQ

        To configure the queues in HA mode, the two docs suggests two
        slightly different commands;

        The first one says:

        rabbitmqctl set_policy ha-all '^(?!amq\.).*' '{"ha-mode": "all"}'


        while the second one says:

        rabbitmqctl set_policy HA '^(?!amq\.).*' '{"ha-mode": "all"}'


        "ha_all" vs. "HA".

        which one is correct ?

        thanks,

            Alvise

        
__________________________________________________________________________
        OpenStack Development Mailing List (not for usage questions)
        Unsubscribe:
        [email protected]?subject:unsubscribe
        <http://[email protected]?subject:unsubscribe>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev





_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to