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

Don't clear filtering metadata in secondaries when entering critical section

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Incomplete
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding

    Description

      Currently, we clear the secondary filtering metadata when it reaches the point when primary reaches the critical section. It then tries to wait for primary critical section, and wait for it's replication to reach that opTime.

      Another alternative is to instead have an oplog to inform the secondaries that the donor shard has bumped the shard version. It has to do this properly both during migration commit and migration recovery during step up.

      Note: will probably need something like an extra field to ensure that behavior is backwards compatible.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: