Combine ha-mode with queue-master-locator in a RabbitMQ cluster
up vote
0
down vote
favorite
In a RabbitMQ cluster, I know that the queues can be created with their masters on different nodes, using the "min-masters" strategy of the "queue_master_locator" policy. This would mean that the queues are no longer mirrored(ha-mode policy cant be applied), as only one policy can be applied at a time. Is there a way to accomplish both?
I basically want to have the queues distributed across cluster nodes, so the memory footprint on a single node is reduced.
rabbitmq message-queue high-availability rabbitmqctl
add a comment |
up vote
0
down vote
favorite
In a RabbitMQ cluster, I know that the queues can be created with their masters on different nodes, using the "min-masters" strategy of the "queue_master_locator" policy. This would mean that the queues are no longer mirrored(ha-mode policy cant be applied), as only one policy can be applied at a time. Is there a way to accomplish both?
I basically want to have the queues distributed across cluster nodes, so the memory footprint on a single node is reduced.
rabbitmq message-queue high-availability rabbitmqctl
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In a RabbitMQ cluster, I know that the queues can be created with their masters on different nodes, using the "min-masters" strategy of the "queue_master_locator" policy. This would mean that the queues are no longer mirrored(ha-mode policy cant be applied), as only one policy can be applied at a time. Is there a way to accomplish both?
I basically want to have the queues distributed across cluster nodes, so the memory footprint on a single node is reduced.
rabbitmq message-queue high-availability rabbitmqctl
In a RabbitMQ cluster, I know that the queues can be created with their masters on different nodes, using the "min-masters" strategy of the "queue_master_locator" policy. This would mean that the queues are no longer mirrored(ha-mode policy cant be applied), as only one policy can be applied at a time. Is there a way to accomplish both?
I basically want to have the queues distributed across cluster nodes, so the memory footprint on a single node is reduced.
rabbitmq message-queue high-availability rabbitmqctl
rabbitmq message-queue high-availability rabbitmqctl
asked Nov 19 at 11:06
chaitra.kear
2718
2718
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
queue_master_locator=min-masters
policy means that the master queue node is automatically assigned using the rabbitmq node with less masters.
This is not related to ha-mirror policy.
you have 3 ways to solve the problem:
create a single policy with both the features in this way:
create only the ha policy and add the arg
x-queue-master-locator
to each single queue:
create only the ha policy and use the rabbitmq config file to define the
x-queue-master-locator
, see here for more details: https://www.rabbitmq.com/configure.html#configuration-file
Also suggesto to read this blog post about that.
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 at 6:10
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
queue_master_locator=min-masters
policy means that the master queue node is automatically assigned using the rabbitmq node with less masters.
This is not related to ha-mirror policy.
you have 3 ways to solve the problem:
create a single policy with both the features in this way:
create only the ha policy and add the arg
x-queue-master-locator
to each single queue:
create only the ha policy and use the rabbitmq config file to define the
x-queue-master-locator
, see here for more details: https://www.rabbitmq.com/configure.html#configuration-file
Also suggesto to read this blog post about that.
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 at 6:10
add a comment |
up vote
2
down vote
accepted
queue_master_locator=min-masters
policy means that the master queue node is automatically assigned using the rabbitmq node with less masters.
This is not related to ha-mirror policy.
you have 3 ways to solve the problem:
create a single policy with both the features in this way:
create only the ha policy and add the arg
x-queue-master-locator
to each single queue:
create only the ha policy and use the rabbitmq config file to define the
x-queue-master-locator
, see here for more details: https://www.rabbitmq.com/configure.html#configuration-file
Also suggesto to read this blog post about that.
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 at 6:10
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
queue_master_locator=min-masters
policy means that the master queue node is automatically assigned using the rabbitmq node with less masters.
This is not related to ha-mirror policy.
you have 3 ways to solve the problem:
create a single policy with both the features in this way:
create only the ha policy and add the arg
x-queue-master-locator
to each single queue:
create only the ha policy and use the rabbitmq config file to define the
x-queue-master-locator
, see here for more details: https://www.rabbitmq.com/configure.html#configuration-file
Also suggesto to read this blog post about that.
queue_master_locator=min-masters
policy means that the master queue node is automatically assigned using the rabbitmq node with less masters.
This is not related to ha-mirror policy.
you have 3 ways to solve the problem:
create a single policy with both the features in this way:
create only the ha policy and add the arg
x-queue-master-locator
to each single queue:
create only the ha policy and use the rabbitmq config file to define the
x-queue-master-locator
, see here for more details: https://www.rabbitmq.com/configure.html#configuration-file
Also suggesto to read this blog post about that.
edited Nov 19 at 13:38
answered Nov 19 at 11:45
Gabriele
14.3k42233
14.3k42233
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 at 6:10
add a comment |
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 at 6:10
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 at 6:10
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 at 6:10
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373302%2fcombine-ha-mode-with-queue-master-locator-in-a-rabbitmq-cluster%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown