mongo replication not happeningMongo replication lag slowly increasingMongo replication lag slowly...

Figuring out size of Device Drivers and where they are loaded in High Memory

Why are "square law" devices important?

If I have Haste cast on me, does it reduce the casting time for my spells that normally take more than a turn to cast?

Coworker is trying to get me to sign his petition to run for office. How to decline politely?

Can I do anything else with aspersions other than cast them?

What is an explicit bijection in combinatorics?

Was the Soviet N1 really capable of sending 9.6 GB/s of telemetry?

What's the meaning of #0?

Did the characters in Moving Pictures not know about cameras like Twoflower's?

Exploding Numbers

Why write a book when there's a movie in my head?

Short story about a man betting a group he could tell a story, and one of them would disappear and the others would not notice

Cryptic cross... with words

What is formjacking?

Identical projects by students at two different colleges: still plagiarism?

Why do single electrical receptacles exist?

Now...where was I?

Isn't a semicolon (';') needed after a function declaration in C++?

How can changes in personality/values of a person who turned into a vampire be explained?

Build ASCII Podiums

Is there any danger of my neighbor having my wife's signature?

Is the tritone (A4 / d5) still banned in Roman Catholic music?

How bad is a Computer Science course that doesn't teach Design Patterns?

What are some good alternatives to Whisper for blockchain messaging?



mongo replication not happening


Mongo replication lag slowly increasingMongo replication lag slowly increasingMongo Replication with VIPClient not reading from Mongo secondary databasehow to convert mongodb(2.4.10) startup2 to primaryMongo initial sync failing with InvalidSyncSourceReplica Set Question - one primary instance with two secondary instancesMongoDB sharded cluster chunks distributionADD new node Replication in MongoDBMongodb rs.add() new member in STARTUP state













1















I setup master/slave replication of mongodb on EC2. But I see not replication happening. When I do "show dbs" on master, it shows all dbs expected.



But when I do the same on replica, it does not show me any db.



Please help me troubleshoot.



rs.config()
{
"_id" : "ittw",
"version" : 1,
"members" : [
{
"_id" : 0,
"host" : "ip-10-304-48-93:27017"
}
]
}

rs.config()
{
"_id" : "ittw",
"version" : 2,
"members" : [
{
"_id" : 0,
"host" : "domU-17-31-19-16-88-5F:27017"
},
{
"_id" : 1,
"host" : "ec2-50-321-52-908.compute-1.amazonaws.com:27017"
}
]
}



rs.status() // replica
{
"set" : "ittw",
"date" : ISODate("2013-08-12T06:55:57Z"),
"myState" : 1,
"members" : [
{
"_id" : 0,
"name" : "$ip:27017",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 356039,
"optime" : Timestamp(1375934685, 1),
"optimeDate" : ISODate("2013-08-08T04:04:45Z"),
"self" : true
}
],
"ok" : 1
}



rs.status() //Master
{
"set" : "ittw",
"date" : ISODate("2013-08-12T06:57:19Z"),
"myState" : 1,
"members" : [
{
"_id" : 0,
"name" : "PRI_IP:27017",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 356543,
"optime" : Timestamp(1376289725, 1),
"optimeDate" : ISODate("2013-08-12T06:42:05Z"),
"self" : true
},
{
"_id" : 1,
"name" : "REP_IP:27017",
"health" : 1,
"state" : 1,
"stateStr" : "PRIMARY",
"uptime" : 355869,
"optime" : Timestamp(1375934685, 1),
"optimeDate" : ISODate("2013-08-08T04:04:45Z"),
"lastHeartbeat" : ISODate("2013-08-12T06:57:17Z"),
"lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00Z"),
"pingMs" : 1
}
],
"ok" : 1
}









share|improve this question





























    1















    I setup master/slave replication of mongodb on EC2. But I see not replication happening. When I do "show dbs" on master, it shows all dbs expected.



    But when I do the same on replica, it does not show me any db.



    Please help me troubleshoot.



    rs.config()
    {
    "_id" : "ittw",
    "version" : 1,
    "members" : [
    {
    "_id" : 0,
    "host" : "ip-10-304-48-93:27017"
    }
    ]
    }

    rs.config()
    {
    "_id" : "ittw",
    "version" : 2,
    "members" : [
    {
    "_id" : 0,
    "host" : "domU-17-31-19-16-88-5F:27017"
    },
    {
    "_id" : 1,
    "host" : "ec2-50-321-52-908.compute-1.amazonaws.com:27017"
    }
    ]
    }



    rs.status() // replica
    {
    "set" : "ittw",
    "date" : ISODate("2013-08-12T06:55:57Z"),
    "myState" : 1,
    "members" : [
    {
    "_id" : 0,
    "name" : "$ip:27017",
    "health" : 1,
    "state" : 1,
    "stateStr" : "PRIMARY",
    "uptime" : 356039,
    "optime" : Timestamp(1375934685, 1),
    "optimeDate" : ISODate("2013-08-08T04:04:45Z"),
    "self" : true
    }
    ],
    "ok" : 1
    }



    rs.status() //Master
    {
    "set" : "ittw",
    "date" : ISODate("2013-08-12T06:57:19Z"),
    "myState" : 1,
    "members" : [
    {
    "_id" : 0,
    "name" : "PRI_IP:27017",
    "health" : 1,
    "state" : 1,
    "stateStr" : "PRIMARY",
    "uptime" : 356543,
    "optime" : Timestamp(1376289725, 1),
    "optimeDate" : ISODate("2013-08-12T06:42:05Z"),
    "self" : true
    },
    {
    "_id" : 1,
    "name" : "REP_IP:27017",
    "health" : 1,
    "state" : 1,
    "stateStr" : "PRIMARY",
    "uptime" : 355869,
    "optime" : Timestamp(1375934685, 1),
    "optimeDate" : ISODate("2013-08-08T04:04:45Z"),
    "lastHeartbeat" : ISODate("2013-08-12T06:57:17Z"),
    "lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00Z"),
    "pingMs" : 1
    }
    ],
    "ok" : 1
    }









    share|improve this question



























      1












      1








      1








      I setup master/slave replication of mongodb on EC2. But I see not replication happening. When I do "show dbs" on master, it shows all dbs expected.



      But when I do the same on replica, it does not show me any db.



      Please help me troubleshoot.



      rs.config()
      {
      "_id" : "ittw",
      "version" : 1,
      "members" : [
      {
      "_id" : 0,
      "host" : "ip-10-304-48-93:27017"
      }
      ]
      }

      rs.config()
      {
      "_id" : "ittw",
      "version" : 2,
      "members" : [
      {
      "_id" : 0,
      "host" : "domU-17-31-19-16-88-5F:27017"
      },
      {
      "_id" : 1,
      "host" : "ec2-50-321-52-908.compute-1.amazonaws.com:27017"
      }
      ]
      }



      rs.status() // replica
      {
      "set" : "ittw",
      "date" : ISODate("2013-08-12T06:55:57Z"),
      "myState" : 1,
      "members" : [
      {
      "_id" : 0,
      "name" : "$ip:27017",
      "health" : 1,
      "state" : 1,
      "stateStr" : "PRIMARY",
      "uptime" : 356039,
      "optime" : Timestamp(1375934685, 1),
      "optimeDate" : ISODate("2013-08-08T04:04:45Z"),
      "self" : true
      }
      ],
      "ok" : 1
      }



      rs.status() //Master
      {
      "set" : "ittw",
      "date" : ISODate("2013-08-12T06:57:19Z"),
      "myState" : 1,
      "members" : [
      {
      "_id" : 0,
      "name" : "PRI_IP:27017",
      "health" : 1,
      "state" : 1,
      "stateStr" : "PRIMARY",
      "uptime" : 356543,
      "optime" : Timestamp(1376289725, 1),
      "optimeDate" : ISODate("2013-08-12T06:42:05Z"),
      "self" : true
      },
      {
      "_id" : 1,
      "name" : "REP_IP:27017",
      "health" : 1,
      "state" : 1,
      "stateStr" : "PRIMARY",
      "uptime" : 355869,
      "optime" : Timestamp(1375934685, 1),
      "optimeDate" : ISODate("2013-08-08T04:04:45Z"),
      "lastHeartbeat" : ISODate("2013-08-12T06:57:17Z"),
      "lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00Z"),
      "pingMs" : 1
      }
      ],
      "ok" : 1
      }









      share|improve this question
















      I setup master/slave replication of mongodb on EC2. But I see not replication happening. When I do "show dbs" on master, it shows all dbs expected.



      But when I do the same on replica, it does not show me any db.



      Please help me troubleshoot.



      rs.config()
      {
      "_id" : "ittw",
      "version" : 1,
      "members" : [
      {
      "_id" : 0,
      "host" : "ip-10-304-48-93:27017"
      }
      ]
      }

      rs.config()
      {
      "_id" : "ittw",
      "version" : 2,
      "members" : [
      {
      "_id" : 0,
      "host" : "domU-17-31-19-16-88-5F:27017"
      },
      {
      "_id" : 1,
      "host" : "ec2-50-321-52-908.compute-1.amazonaws.com:27017"
      }
      ]
      }



      rs.status() // replica
      {
      "set" : "ittw",
      "date" : ISODate("2013-08-12T06:55:57Z"),
      "myState" : 1,
      "members" : [
      {
      "_id" : 0,
      "name" : "$ip:27017",
      "health" : 1,
      "state" : 1,
      "stateStr" : "PRIMARY",
      "uptime" : 356039,
      "optime" : Timestamp(1375934685, 1),
      "optimeDate" : ISODate("2013-08-08T04:04:45Z"),
      "self" : true
      }
      ],
      "ok" : 1
      }



      rs.status() //Master
      {
      "set" : "ittw",
      "date" : ISODate("2013-08-12T06:57:19Z"),
      "myState" : 1,
      "members" : [
      {
      "_id" : 0,
      "name" : "PRI_IP:27017",
      "health" : 1,
      "state" : 1,
      "stateStr" : "PRIMARY",
      "uptime" : 356543,
      "optime" : Timestamp(1376289725, 1),
      "optimeDate" : ISODate("2013-08-12T06:42:05Z"),
      "self" : true
      },
      {
      "_id" : 1,
      "name" : "REP_IP:27017",
      "health" : 1,
      "state" : 1,
      "stateStr" : "PRIMARY",
      "uptime" : 355869,
      "optime" : Timestamp(1375934685, 1),
      "optimeDate" : ISODate("2013-08-08T04:04:45Z"),
      "lastHeartbeat" : ISODate("2013-08-12T06:57:17Z"),
      "lastHeartbeatRecv" : ISODate("1970-01-01T00:00:00Z"),
      "pingMs" : 1
      }
      ],
      "ok" : 1
      }






      mongodb






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 12 '13 at 10:08







      www.tyme-it.com

















      asked Aug 12 '13 at 6:54









      www.tyme-it.comwww.tyme-it.com

      10827




      10827






















          4 Answers
          4






          active

          oldest

          votes


















          2














          It looks like what you have done is run rs.initiate() on both the primary and the secondary server.



          In this case the outcome is that you have two different replica sets called ittw rather than a single replica set with replication. The primary knows about both nodes, but the "secondary" you setup is also configured as a primary for a replica set only containing itself. This definitely won't work.



          As per the instructions on Deploying a replica set, you should only run rs.initiate() on the primary, and then use rs.add("hostname:port") to add secondaries to the same replica set.



          To fix up your dud secondary to a clean state, you should:




          • stop the secondary using db.shutdownServer() or appropriate command like service mongodb stop (depending on how you installed MongoDB)

          • remove the files in the dbpath directory for the secondary

          • restart the secondary

          • use the mongo shell to connect to the primary, and rs.add() your secondary


          If all is well you should see consistent rs.status() information on the primary and new secondary.






          share|improve this answer































            1














            Have you run the rs.initiate command to kick it all off?



            Docs



            Also how do you have your replset configured? Is it a single master and a single slave? Do you have a second secondary or an arbiter to provide quorm and ensure clean failover?






            share|improve this answer
























            • rs.initiate() { "info" : "try querying local.system.replset to see current configuration", "ok" : 0, "errmsg" : "already initialized" }

              – www.tyme-it.com
              Aug 12 '13 at 10:07











            • 1 master + 1 slave

              – www.tyme-it.com
              Aug 12 '13 at 10:08











            • It looks like you have a split brain i.e. both nodes think they are primary. Have you tried rs.stepdown() on one of the nodes Docs

              – Mike Birkett
              Aug 12 '13 at 10:18











            • Also I see you have two versions of rs.config. Have you run rs.reconfig using the newest version? Docs

              – Mike Birkett
              Aug 12 '13 at 10:21



















            0














            I have correct this problem with the 2 parameters in the config file:



            net.http.enabled:                "true"
            net.http.RESTInterfaceEnabled: "true"





            share|improve this answer

































              0














              MongoDB Replication is Automated and available in www.MongoGen.com





              share








              New contributor




              mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.




















                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%2f47958%2fmongo-replication-not-happening%23new-answer', 'question_page');
                }
                );

                Post as a guest















                Required, but never shown

























                4 Answers
                4






                active

                oldest

                votes








                4 Answers
                4






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes









                2














                It looks like what you have done is run rs.initiate() on both the primary and the secondary server.



                In this case the outcome is that you have two different replica sets called ittw rather than a single replica set with replication. The primary knows about both nodes, but the "secondary" you setup is also configured as a primary for a replica set only containing itself. This definitely won't work.



                As per the instructions on Deploying a replica set, you should only run rs.initiate() on the primary, and then use rs.add("hostname:port") to add secondaries to the same replica set.



                To fix up your dud secondary to a clean state, you should:




                • stop the secondary using db.shutdownServer() or appropriate command like service mongodb stop (depending on how you installed MongoDB)

                • remove the files in the dbpath directory for the secondary

                • restart the secondary

                • use the mongo shell to connect to the primary, and rs.add() your secondary


                If all is well you should see consistent rs.status() information on the primary and new secondary.






                share|improve this answer




























                  2














                  It looks like what you have done is run rs.initiate() on both the primary and the secondary server.



                  In this case the outcome is that you have two different replica sets called ittw rather than a single replica set with replication. The primary knows about both nodes, but the "secondary" you setup is also configured as a primary for a replica set only containing itself. This definitely won't work.



                  As per the instructions on Deploying a replica set, you should only run rs.initiate() on the primary, and then use rs.add("hostname:port") to add secondaries to the same replica set.



                  To fix up your dud secondary to a clean state, you should:




                  • stop the secondary using db.shutdownServer() or appropriate command like service mongodb stop (depending on how you installed MongoDB)

                  • remove the files in the dbpath directory for the secondary

                  • restart the secondary

                  • use the mongo shell to connect to the primary, and rs.add() your secondary


                  If all is well you should see consistent rs.status() information on the primary and new secondary.






                  share|improve this answer


























                    2












                    2








                    2







                    It looks like what you have done is run rs.initiate() on both the primary and the secondary server.



                    In this case the outcome is that you have two different replica sets called ittw rather than a single replica set with replication. The primary knows about both nodes, but the "secondary" you setup is also configured as a primary for a replica set only containing itself. This definitely won't work.



                    As per the instructions on Deploying a replica set, you should only run rs.initiate() on the primary, and then use rs.add("hostname:port") to add secondaries to the same replica set.



                    To fix up your dud secondary to a clean state, you should:




                    • stop the secondary using db.shutdownServer() or appropriate command like service mongodb stop (depending on how you installed MongoDB)

                    • remove the files in the dbpath directory for the secondary

                    • restart the secondary

                    • use the mongo shell to connect to the primary, and rs.add() your secondary


                    If all is well you should see consistent rs.status() information on the primary and new secondary.






                    share|improve this answer













                    It looks like what you have done is run rs.initiate() on both the primary and the secondary server.



                    In this case the outcome is that you have two different replica sets called ittw rather than a single replica set with replication. The primary knows about both nodes, but the "secondary" you setup is also configured as a primary for a replica set only containing itself. This definitely won't work.



                    As per the instructions on Deploying a replica set, you should only run rs.initiate() on the primary, and then use rs.add("hostname:port") to add secondaries to the same replica set.



                    To fix up your dud secondary to a clean state, you should:




                    • stop the secondary using db.shutdownServer() or appropriate command like service mongodb stop (depending on how you installed MongoDB)

                    • remove the files in the dbpath directory for the secondary

                    • restart the secondary

                    • use the mongo shell to connect to the primary, and rs.add() your secondary


                    If all is well you should see consistent rs.status() information on the primary and new secondary.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Aug 21 '13 at 14:26









                    StennieStennie

                    6,64411627




                    6,64411627

























                        1














                        Have you run the rs.initiate command to kick it all off?



                        Docs



                        Also how do you have your replset configured? Is it a single master and a single slave? Do you have a second secondary or an arbiter to provide quorm and ensure clean failover?






                        share|improve this answer
























                        • rs.initiate() { "info" : "try querying local.system.replset to see current configuration", "ok" : 0, "errmsg" : "already initialized" }

                          – www.tyme-it.com
                          Aug 12 '13 at 10:07











                        • 1 master + 1 slave

                          – www.tyme-it.com
                          Aug 12 '13 at 10:08











                        • It looks like you have a split brain i.e. both nodes think they are primary. Have you tried rs.stepdown() on one of the nodes Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:18











                        • Also I see you have two versions of rs.config. Have you run rs.reconfig using the newest version? Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:21
















                        1














                        Have you run the rs.initiate command to kick it all off?



                        Docs



                        Also how do you have your replset configured? Is it a single master and a single slave? Do you have a second secondary or an arbiter to provide quorm and ensure clean failover?






                        share|improve this answer
























                        • rs.initiate() { "info" : "try querying local.system.replset to see current configuration", "ok" : 0, "errmsg" : "already initialized" }

                          – www.tyme-it.com
                          Aug 12 '13 at 10:07











                        • 1 master + 1 slave

                          – www.tyme-it.com
                          Aug 12 '13 at 10:08











                        • It looks like you have a split brain i.e. both nodes think they are primary. Have you tried rs.stepdown() on one of the nodes Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:18











                        • Also I see you have two versions of rs.config. Have you run rs.reconfig using the newest version? Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:21














                        1












                        1








                        1







                        Have you run the rs.initiate command to kick it all off?



                        Docs



                        Also how do you have your replset configured? Is it a single master and a single slave? Do you have a second secondary or an arbiter to provide quorm and ensure clean failover?






                        share|improve this answer













                        Have you run the rs.initiate command to kick it all off?



                        Docs



                        Also how do you have your replset configured? Is it a single master and a single slave? Do you have a second secondary or an arbiter to provide quorm and ensure clean failover?







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered Aug 12 '13 at 9:53









                        Mike BirkettMike Birkett

                        1411




                        1411













                        • rs.initiate() { "info" : "try querying local.system.replset to see current configuration", "ok" : 0, "errmsg" : "already initialized" }

                          – www.tyme-it.com
                          Aug 12 '13 at 10:07











                        • 1 master + 1 slave

                          – www.tyme-it.com
                          Aug 12 '13 at 10:08











                        • It looks like you have a split brain i.e. both nodes think they are primary. Have you tried rs.stepdown() on one of the nodes Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:18











                        • Also I see you have two versions of rs.config. Have you run rs.reconfig using the newest version? Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:21



















                        • rs.initiate() { "info" : "try querying local.system.replset to see current configuration", "ok" : 0, "errmsg" : "already initialized" }

                          – www.tyme-it.com
                          Aug 12 '13 at 10:07











                        • 1 master + 1 slave

                          – www.tyme-it.com
                          Aug 12 '13 at 10:08











                        • It looks like you have a split brain i.e. both nodes think they are primary. Have you tried rs.stepdown() on one of the nodes Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:18











                        • Also I see you have two versions of rs.config. Have you run rs.reconfig using the newest version? Docs

                          – Mike Birkett
                          Aug 12 '13 at 10:21

















                        rs.initiate() { "info" : "try querying local.system.replset to see current configuration", "ok" : 0, "errmsg" : "already initialized" }

                        – www.tyme-it.com
                        Aug 12 '13 at 10:07





                        rs.initiate() { "info" : "try querying local.system.replset to see current configuration", "ok" : 0, "errmsg" : "already initialized" }

                        – www.tyme-it.com
                        Aug 12 '13 at 10:07













                        1 master + 1 slave

                        – www.tyme-it.com
                        Aug 12 '13 at 10:08





                        1 master + 1 slave

                        – www.tyme-it.com
                        Aug 12 '13 at 10:08













                        It looks like you have a split brain i.e. both nodes think they are primary. Have you tried rs.stepdown() on one of the nodes Docs

                        – Mike Birkett
                        Aug 12 '13 at 10:18





                        It looks like you have a split brain i.e. both nodes think they are primary. Have you tried rs.stepdown() on one of the nodes Docs

                        – Mike Birkett
                        Aug 12 '13 at 10:18













                        Also I see you have two versions of rs.config. Have you run rs.reconfig using the newest version? Docs

                        – Mike Birkett
                        Aug 12 '13 at 10:21





                        Also I see you have two versions of rs.config. Have you run rs.reconfig using the newest version? Docs

                        – Mike Birkett
                        Aug 12 '13 at 10:21











                        0














                        I have correct this problem with the 2 parameters in the config file:



                        net.http.enabled:                "true"
                        net.http.RESTInterfaceEnabled: "true"





                        share|improve this answer






























                          0














                          I have correct this problem with the 2 parameters in the config file:



                          net.http.enabled:                "true"
                          net.http.RESTInterfaceEnabled: "true"





                          share|improve this answer




























                            0












                            0








                            0







                            I have correct this problem with the 2 parameters in the config file:



                            net.http.enabled:                "true"
                            net.http.RESTInterfaceEnabled: "true"





                            share|improve this answer















                            I have correct this problem with the 2 parameters in the config file:



                            net.http.enabled:                "true"
                            net.http.RESTInterfaceEnabled: "true"






                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Oct 14 '14 at 12:54









                            RLF

                            13k12440




                            13k12440










                            answered Oct 14 '14 at 12:31









                            tfrsub00tfrsub00

                            1




                            1























                                0














                                MongoDB Replication is Automated and available in www.MongoGen.com





                                share








                                New contributor




                                mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                Check out our Code of Conduct.

























                                  0














                                  MongoDB Replication is Automated and available in www.MongoGen.com





                                  share








                                  New contributor




                                  mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                  Check out our Code of Conduct.























                                    0












                                    0








                                    0







                                    MongoDB Replication is Automated and available in www.MongoGen.com





                                    share








                                    New contributor




                                    mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.










                                    MongoDB Replication is Automated and available in www.MongoGen.com






                                    share








                                    New contributor




                                    mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.








                                    share


                                    share






                                    New contributor




                                    mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.









                                    answered 2 mins ago









                                    mongogen.commongogen.com

                                    1




                                    1




                                    New contributor




                                    mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.





                                    New contributor





                                    mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.






                                    mongogen.com is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                                    Check out our Code of Conduct.






























                                        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%2f47958%2fmongo-replication-not-happening%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

                                        ORA-01691 (unable to extend lob segment) even though my tablespace has AUTOEXTEND onORA-01692: unable to...

                                        Always On Availability groups resolving state after failover - Remote harden of transaction...

                                        Circunscripción electoral de Guipúzcoa Referencias Menú de navegaciónLas claves del sistema electoral en...