-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
v5.2, v5.0
-
Sharding 2022-01-10, Sharding 2022-01-24, Sharding 2022-02-07, Sharding 2022-05-02
-
36
-
4
This is because the usages was assuming that if an error occurred while running the function, it will be aborted so retrying can start with a clean slate. However, there is an edge case when commit was successful but the wait for write concern was interrupted. This can cause the function to assert even after successfully committing the changes.
- related to
-
SERVER-67457 Resharding operation aborted in the midst of contacting participants may stall on config server primary indefinitely
- Closed
-
SERVER-62072 _configsvrReshardCollection may return without having waited for unsetting "reshardingFields" to replicate to majority
- Closed