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

Delete SucceedsIfFilteringMetadataUUIDInitiallyDifferentFromTaskUUIDButMatchesAfterRefresh

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding EMEA 2022-03-21

      SucceedsIfFilteringMetadataUUIDInitiallyDifferentFromTaskUUIDButMatchesAfterRefresh test case must be deleted because it tests an artificial scenario that can't happen in the real world.

      The scenario is the following:

      1. Two different incarnations of the same collection: create-drop-recreate, same namespace but different UUIDs
      2. Set the filtering metadata of the first incarnation (stale)
      3. Schedule a range deletion task for the second incarnation
      4. Expect point (3) to trigger a refresh and get the filtering metadata of the second incarnation (non-stale)

      The test is wrong because it can NEVER happen that a range deletion task is created on the second incarnation without a previous successful refresh: a range deleter task is created because of a moveChunk, and a moveChunk can only happen with updated metadata.

      So the short story is: it can never happen on a specific shard to have stale filtering metadata for COLL and a range deletion task associated with "non-stale" COLL.

            Assignee:
            antonio.fuschetto@mongodb.com Antonio Fuschetto
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: