Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-4941

collection rename may not replicate / clone properly

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Planning Bucket A
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL

      Description

      If a collection is renamed during initial sync or other clone operation such as copyDatabase, the collection may be missed by the clone process.

      Test will be pushed.

        Issue Links

          Activity

          Hide
          auto auto (Inactive) added a comment -

          Author:

          {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'}

          Message: SERVER-4941 test
          Branch: master
          https://github.com/mongodb/mongo/commit/8c13962e6878a9dd8de81ca7cebb729e9cc3ac43

          Show
          auto auto (Inactive) added a comment - Author: {u'login': u'astaple', u'name': u'Aaron', u'email': u'aaron@10gen.com'} Message: SERVER-4941 test Branch: master https://github.com/mongodb/mongo/commit/8c13962e6878a9dd8de81ca7cebb729e9cc3ac43
          Hide
          milkie Eric Milkie added a comment -

          SERVER-23919 will alleviate the problems from this issue. The full solution will be SERVER-15359.

          Show
          milkie Eric Milkie added a comment - SERVER-23919 will alleviate the problems from this issue. The full solution will be SERVER-15359 .

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since reply:
                3 weeks, 3 days ago
                Date of 1st Reply: