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

Audit usages of epoch in sharding code

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2020-02-24

      Description

      In several places in sharding we use a change of epoch to indicate that a collection had been dropped and recreated. After the refine shard key project however, this logic is no longer valid, since refining a shard key can cause an epoch change. We should audit and fix the places where epoch is used instead of collection UUID to check for collection drops and recreates.

      Specific examples include the MigrationDestinationManager and the CollectionShardingRuntime.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              matthew.saltz Matthew Saltz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: