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

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

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None

      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

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              renctan Randolph Tan
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: