Original Redis Master does not become “good” slave after failover
I have setup a 3 node HA redis cluster with Sentinel monitors on each of the nodes.
I have the following configuration:
RedisA - Master
RedisB - Replica
RedisC - Replica
with 3 Sentinels watching the Master.
Everything works fine (I'm keeping all sentinels up, so no quorum problems):
- I stop the RedisA process and it fails over to RedisB
for Master. - I stop RedisB and it will failover and make RedisC master.
Bring back RedisA and RedisB, they become Replicas as expected. - I stop RedisC, RedisB becomes Master.
- With only RedisB and RedisA up, I stop RedisB. But now RedisA DOES NOT become master and my HA cluster breaks down.
So everything seems to be fine except the problem is that RedisA (the original Master) doesn't become an eligable slave.
Any help is greatly appreciated!
replication redis
add a comment |
I have setup a 3 node HA redis cluster with Sentinel monitors on each of the nodes.
I have the following configuration:
RedisA - Master
RedisB - Replica
RedisC - Replica
with 3 Sentinels watching the Master.
Everything works fine (I'm keeping all sentinels up, so no quorum problems):
- I stop the RedisA process and it fails over to RedisB
for Master. - I stop RedisB and it will failover and make RedisC master.
Bring back RedisA and RedisB, they become Replicas as expected. - I stop RedisC, RedisB becomes Master.
- With only RedisB and RedisA up, I stop RedisB. But now RedisA DOES NOT become master and my HA cluster breaks down.
So everything seems to be fine except the problem is that RedisA (the original Master) doesn't become an eligable slave.
Any help is greatly appreciated!
replication redis
add a comment |
I have setup a 3 node HA redis cluster with Sentinel monitors on each of the nodes.
I have the following configuration:
RedisA - Master
RedisB - Replica
RedisC - Replica
with 3 Sentinels watching the Master.
Everything works fine (I'm keeping all sentinels up, so no quorum problems):
- I stop the RedisA process and it fails over to RedisB
for Master. - I stop RedisB and it will failover and make RedisC master.
Bring back RedisA and RedisB, they become Replicas as expected. - I stop RedisC, RedisB becomes Master.
- With only RedisB and RedisA up, I stop RedisB. But now RedisA DOES NOT become master and my HA cluster breaks down.
So everything seems to be fine except the problem is that RedisA (the original Master) doesn't become an eligable slave.
Any help is greatly appreciated!
replication redis
I have setup a 3 node HA redis cluster with Sentinel monitors on each of the nodes.
I have the following configuration:
RedisA - Master
RedisB - Replica
RedisC - Replica
with 3 Sentinels watching the Master.
Everything works fine (I'm keeping all sentinels up, so no quorum problems):
- I stop the RedisA process and it fails over to RedisB
for Master. - I stop RedisB and it will failover and make RedisC master.
Bring back RedisA and RedisB, they become Replicas as expected. - I stop RedisC, RedisB becomes Master.
- With only RedisB and RedisA up, I stop RedisB. But now RedisA DOES NOT become master and my HA cluster breaks down.
So everything seems to be fine except the problem is that RedisA (the original Master) doesn't become an eligable slave.
Any help is greatly appreciated!
replication redis
replication redis
asked Jan 5 at 17:56
AdriaanAdriaan
13
13
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I have found my problem. My configuration has password authentication. The initial configuration had masterauth set for both slaves, but I did not add it to the master (since it didn't need it). When it failed over, the master became a slave, but since it didn't have the masterauth password set, it could not replicate and thus sentinel wisely refused to select it as the new master after that.
Fix: Add masterauth password to my original master (RedisA).
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1390947%2foriginal-redis-master-does-not-become-good-slave-after-failover%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
I have found my problem. My configuration has password authentication. The initial configuration had masterauth set for both slaves, but I did not add it to the master (since it didn't need it). When it failed over, the master became a slave, but since it didn't have the masterauth password set, it could not replicate and thus sentinel wisely refused to select it as the new master after that.
Fix: Add masterauth password to my original master (RedisA).
add a comment |
I have found my problem. My configuration has password authentication. The initial configuration had masterauth set for both slaves, but I did not add it to the master (since it didn't need it). When it failed over, the master became a slave, but since it didn't have the masterauth password set, it could not replicate and thus sentinel wisely refused to select it as the new master after that.
Fix: Add masterauth password to my original master (RedisA).
add a comment |
I have found my problem. My configuration has password authentication. The initial configuration had masterauth set for both slaves, but I did not add it to the master (since it didn't need it). When it failed over, the master became a slave, but since it didn't have the masterauth password set, it could not replicate and thus sentinel wisely refused to select it as the new master after that.
Fix: Add masterauth password to my original master (RedisA).
I have found my problem. My configuration has password authentication. The initial configuration had masterauth set for both slaves, but I did not add it to the master (since it didn't need it). When it failed over, the master became a slave, but since it didn't have the masterauth password set, it could not replicate and thus sentinel wisely refused to select it as the new master after that.
Fix: Add masterauth password to my original master (RedisA).
answered Jan 17 at 1:21
AdriaanAdriaan
13
13
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1390947%2foriginal-redis-master-does-not-become-good-slave-after-failover%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