Inconsistent behavior with rs.add and rs.reconfigure

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.6
    • Component/s: Replication
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Reported from the Google groups:

      https://groups.google.com/forum/?fromgroups#!topic/mongodb-user/eXZfE8EprBI

      Description from user:

      1) restore host.com with latest backup (including oplog) and execute
      rs.add("host.com") - and you'll that data will be deleted and resynced
      from scratch
      2) restore host.com with latest backup (including oplog) and add it
      into the replica set with rs.reconfig - it will be catched up as slave
      almost immediately
      3) try to reconfigure one of shards with rs.add and rs.reconfig - and
      check the mongoses logs - you'll see the difference

            Assignee:
            Unassigned
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: