[SERVER-44554] Validate and/or fix invariant in MetadataManager::cleanUpRange Created: 11/Nov/19  Updated: 15/Jan/20  Resolved: 15/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Saltz (Inactive) Assignee: Matthew Saltz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45585 Complete TODO listed in SERVER-44554 Closed
Operating System: ALL
Sprint: Sharding 2019-12-02, Sharding 2019-12-30, Sharding 2020-01-13, Sharding 2020-01-27
Participants:

 Description   

This invariant to check that the metadata has not been cleared when calling cleanUpRange may not be valid. It seems that it would be possible to hit this invariant with this existing use of cleanUpRange, in the case where the collection gets dropped and a refresh occurs after the migration completes but before cleanUpRange is called here. It will also be possible to hit this invariant with the addition of new code in the resumable range deleter project.

We should verify whether this should truly be an invariant and:

  • If so, fix the existing bugs around usages of cleanUpRange
  • If not, change the invariant to an error or otherwise handle this case appropriately.


 Comments   
Comment by Matthew Saltz (Inactive) [ 15/Jan/20 ]

Nothing needed to be done here after the refactors

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