[SERVER-64468] Delete SucceedsIfFilteringMetadataUUIDInitiallyDifferentFromTaskUUIDButMatchesAfterRefresh Created: 14/Mar/22  Updated: 29/Oct/23  Resolved: 14/Mar/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-64464 Check the shard version for collectio... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-03-21
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 14/Mar/22 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-64468 Delete SucceedsIfFilteringMetadataUUIDInitiallyDifferentFromTaskUUIDButMatchesAfterRefresh
Branch: master
https://github.com/mongodb/mongo/commit/e1ab3976f52497cb516b95c752eb81d4a69e3bbf

Generated at Thu Feb 08 06:00:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.