[SERVER-52653] Transition resharding coordinator to kDone without bumping shard versions Created: 05/Nov/20  Updated: 29/Oct/23  Resolved: 09/Dec/20

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

Type: Bug Priority: Major - P3
Reporter: Haley Connelly Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-12-14
Participants:
Story Points: 1

 Description   

When the ReshardingCoordinatorService tries to persist its transition to kDone, it calls it tries to do so via resharding::persistStateTransitionAndCatalogUpdatesThenBumpShardVersions. However, at this point, we do not want to bump the shard version of the collection (see notifyForStateTransition) and will hit an invariant.

Our current testing does not catch this because it tests the transition to kDone by calling removeCoordinatorDocAndReshardingFields, which is a function only called by the test that no longer accurately mirrors the coordinator's code flow since SERVER-51291



 Comments   
Comment by Githook User [ 09/Dec/20 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-52653 Transition resharding coordinator to kDone without bumping shard versions
Branch: master
https://github.com/mongodb/mongo/commit/c9e03d62975fef4242ecad86e63662e974f4725f

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