changeStreams will incorrectly notify for oplog entries generated by copying collections on movePrimary

XMLWordPrintableJSON

    • Query Execution
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This is because the Cloner used by movePrimary does not mark these oplog entries as 'fromMigrate', the way the moveChunk protocol does.

      This is a pre-existing bug since 3.6, and would go away if we tracked unsharded collections and moved them through moveChunk rather than movePrimary.

            Assignee:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: