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

Ambiguous behavior after replica set member recovering.

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Trivial - P5 Trivial - P5
    • None
    • 2.2.1
    • Replication
    • None
    • Windows 7 x64
    • Windows
    • Hide

      1. Create repica set (Primary, Secondary, Arbiter)
      2. Insert several documents to (e.g.) test collection.
      3. Stop Secondary server, run it offline and remove all documents from test collection.
      4. Run Secondary and wait replica set sync is completed.
      5. Stop Primary and remove all it's data.
      6. Run Primary and wait replica set sync is completed.

      Result: there is one document (the one that was added last) in test collection on Primary server.
      Expected: test collection is empty.

      Show
      1. Create repica set (Primary, Secondary, Arbiter) 2. Insert several documents to (e.g.) test collection. 3. Stop Secondary server, run it offline and remove all documents from test collection. 4. Run Secondary and wait replica set sync is completed. 5. Stop Primary and remove all it's data. 6. Run Primary and wait replica set sync is completed. Result: there is one document (the one that was added last) in test collection on Primary server. Expected: test collection is empty.

    Description

      Excess data appears after replica set member recovering.

      Attachments

        Activity

          People

            Unassigned Unassigned
            fcbshnik Yan Tanygin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: