Combine ha-mode with queue-master-locator in a RabbitMQ cluster
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 |
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 |
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 '18 at 11:06
chaitra.kearchaitra.kear
2718
2718
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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-locatorto 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 '18 at 6:10
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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-locatorto 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 '18 at 6:10
add a comment |
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-locatorto 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 '18 at 6:10
add a comment |
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-locatorto 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-locatorto 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 '18 at 13:38
answered Nov 19 '18 at 11:45
GabrieleGabriele
14.5k42334
14.5k42334
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 '18 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 '18 at 6:10
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 '18 at 6:10
Thanks Gabriele, I went ahead with the third approach, and it seems to work as expected
– chaitra.kear
Nov 23 '18 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.
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