Original Redis Master does not become “good” slave after failover












0















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):




  1. I stop the RedisA process and it fails over to RedisB
    for Master.

  2. I stop RedisB and it will failover and make RedisC master.
    Bring back RedisA and RedisB, they become Replicas as expected.

  3. I stop RedisC, RedisB becomes Master.

  4. 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!










share|improve this question



























    0















    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):




    1. I stop the RedisA process and it fails over to RedisB
      for Master.

    2. I stop RedisB and it will failover and make RedisC master.
      Bring back RedisA and RedisB, they become Replicas as expected.

    3. I stop RedisC, RedisB becomes Master.

    4. 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!










    share|improve this question

























      0












      0








      0








      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):




      1. I stop the RedisA process and it fails over to RedisB
        for Master.

      2. I stop RedisB and it will failover and make RedisC master.
        Bring back RedisA and RedisB, they become Replicas as expected.

      3. I stop RedisC, RedisB becomes Master.

      4. 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!










      share|improve this question














      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):




      1. I stop the RedisA process and it fails over to RedisB
        for Master.

      2. I stop RedisB and it will failover and make RedisC master.
        Bring back RedisA and RedisB, they become Replicas as expected.

      3. I stop RedisC, RedisB becomes Master.

      4. 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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 5 at 17:56









      AdriaanAdriaan

      13




      13






















          1 Answer
          1






          active

          oldest

          votes


















          0














          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).






          share|improve this answer























            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
            });


            }
            });














            draft saved

            draft discarded


















            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









            0














            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).






            share|improve this answer




























              0














              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).






              share|improve this answer


























                0












                0








                0







                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).






                share|improve this answer













                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).







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 17 at 1:21









                AdriaanAdriaan

                13




                13






























                    draft saved

                    draft discarded




















































                    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.




                    draft saved


                    draft discarded














                    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





















































                    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







                    Popular posts from this blog

                    Plaza Victoria

                    Puebla de Zaragoza

                    Musa