Adding secondary via rs.add on MongoDB





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















I have a master and slave on Linux (centOS 7). The rs.initiate(cfg) was done, but its shows the below output when trying to add secondary via rs.add:





genienational:PRIMARY> rs.add("localhost.localdomain:27017")
{
"ok" : 0,
"errmsg" : "The hosts test.appraisergenie.com:27017 a
nd localhost.localdomain:27017 all map to this node new co
nfiguration version 2 for replica set genienational",
"code": 103
}
genienational:PRIMARY> use local
switched to db local



MongoDB



How do I resolve?



Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.










share|improve this question
















bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • are these all mongo running on same machine? If yes, what are the different ports they are running on?

    – Astro
    Apr 21 '16 at 5:07











  • I guess adding same port of same machine you are using..

    – Gagan Sidhu
    Apr 21 '16 at 10:01




















0















I have a master and slave on Linux (centOS 7). The rs.initiate(cfg) was done, but its shows the below output when trying to add secondary via rs.add:





genienational:PRIMARY> rs.add("localhost.localdomain:27017")
{
"ok" : 0,
"errmsg" : "The hosts test.appraisergenie.com:27017 a
nd localhost.localdomain:27017 all map to this node new co
nfiguration version 2 for replica set genienational",
"code": 103
}
genienational:PRIMARY> use local
switched to db local



MongoDB



How do I resolve?



Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.










share|improve this question
















bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • are these all mongo running on same machine? If yes, what are the different ports they are running on?

    – Astro
    Apr 21 '16 at 5:07











  • I guess adding same port of same machine you are using..

    – Gagan Sidhu
    Apr 21 '16 at 10:01
















0












0








0








I have a master and slave on Linux (centOS 7). The rs.initiate(cfg) was done, but its shows the below output when trying to add secondary via rs.add:





genienational:PRIMARY> rs.add("localhost.localdomain:27017")
{
"ok" : 0,
"errmsg" : "The hosts test.appraisergenie.com:27017 a
nd localhost.localdomain:27017 all map to this node new co
nfiguration version 2 for replica set genienational",
"code": 103
}
genienational:PRIMARY> use local
switched to db local



MongoDB



How do I resolve?



Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.










share|improve this question
















I have a master and slave on Linux (centOS 7). The rs.initiate(cfg) was done, but its shows the below output when trying to add secondary via rs.add:





genienational:PRIMARY> rs.add("localhost.localdomain:27017")
{
"ok" : 0,
"errmsg" : "The hosts test.appraisergenie.com:27017 a
nd localhost.localdomain:27017 all map to this node new co
nfiguration version 2 for replica set genienational",
"code": 103
}
genienational:PRIMARY> use local
switched to db local



MongoDB



How do I resolve?



Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.







mongodb






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 27 '17 at 16:55









Paul White

54.2k14288461




54.2k14288461










asked Apr 19 '16 at 22:17









Shritam BhowmickShritam Bhowmick

1012




1012





bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • are these all mongo running on same machine? If yes, what are the different ports they are running on?

    – Astro
    Apr 21 '16 at 5:07











  • I guess adding same port of same machine you are using..

    – Gagan Sidhu
    Apr 21 '16 at 10:01





















  • are these all mongo running on same machine? If yes, what are the different ports they are running on?

    – Astro
    Apr 21 '16 at 5:07











  • I guess adding same port of same machine you are using..

    – Gagan Sidhu
    Apr 21 '16 at 10:01



















are these all mongo running on same machine? If yes, what are the different ports they are running on?

– Astro
Apr 21 '16 at 5:07





are these all mongo running on same machine? If yes, what are the different ports they are running on?

– Astro
Apr 21 '16 at 5:07













I guess adding same port of same machine you are using..

– Gagan Sidhu
Apr 21 '16 at 10:01







I guess adding same port of same machine you are using..

– Gagan Sidhu
Apr 21 '16 at 10:01












1 Answer
1






active

oldest

votes


















0














The error message in your screenshot indicates you are trying to add identical members to your replica set under different names:



"The hosts x:27017 and y:27017 all map to this node in new configuration".


If you want to configure multiple replica set members on a single machine for testing purposes, all members need to use different ports and/or IP addresses.




Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.




Mixed-version replica sets are only supported for consecutive major versions (i.e. 3.2 and 3.0) and expected to be used transiently during a rolling upgrade to a new major version of MongoDB. A mixed replica set with 3.2 and 2.6 members is definitely not supported.






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2fdba.stackexchange.com%2fquestions%2f135843%2fadding-secondary-via-rs-add-on-mongodb%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














    The error message in your screenshot indicates you are trying to add identical members to your replica set under different names:



    "The hosts x:27017 and y:27017 all map to this node in new configuration".


    If you want to configure multiple replica set members on a single machine for testing purposes, all members need to use different ports and/or IP addresses.




    Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.




    Mixed-version replica sets are only supported for consecutive major versions (i.e. 3.2 and 3.0) and expected to be used transiently during a rolling upgrade to a new major version of MongoDB. A mixed replica set with 3.2 and 2.6 members is definitely not supported.






    share|improve this answer




























      0














      The error message in your screenshot indicates you are trying to add identical members to your replica set under different names:



      "The hosts x:27017 and y:27017 all map to this node in new configuration".


      If you want to configure multiple replica set members on a single machine for testing purposes, all members need to use different ports and/or IP addresses.




      Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.




      Mixed-version replica sets are only supported for consecutive major versions (i.e. 3.2 and 3.0) and expected to be used transiently during a rolling upgrade to a new major version of MongoDB. A mixed replica set with 3.2 and 2.6 members is definitely not supported.






      share|improve this answer


























        0












        0








        0







        The error message in your screenshot indicates you are trying to add identical members to your replica set under different names:



        "The hosts x:27017 and y:27017 all map to this node in new configuration".


        If you want to configure multiple replica set members on a single machine for testing purposes, all members need to use different ports and/or IP addresses.




        Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.




        Mixed-version replica sets are only supported for consecutive major versions (i.e. 3.2 and 3.0) and expected to be used transiently during a rolling upgrade to a new major version of MongoDB. A mixed replica set with 3.2 and 2.6 members is definitely not supported.






        share|improve this answer













        The error message in your screenshot indicates you are trying to add identical members to your replica set under different names:



        "The hosts x:27017 and y:27017 all map to this node in new configuration".


        If you want to configure multiple replica set members on a single machine for testing purposes, all members need to use different ports and/or IP addresses.




        Version: The master is on Enterprise. I think 3.2 and the slave is on 2.6.




        Mixed-version replica sets are only supported for consecutive major versions (i.e. 3.2 and 3.0) and expected to be used transiently during a rolling upgrade to a new major version of MongoDB. A mixed replica set with 3.2 and 2.6 members is definitely not supported.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 11 '16 at 19:27









        StennieStennie

        6,82911628




        6,82911628






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • 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%2fdba.stackexchange.com%2fquestions%2f135843%2fadding-secondary-via-rs-add-on-mongodb%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

            Liste der Baudenkmale in Friedland (Mecklenburg)

            Single-Malt-Whisky

            Czorneboh