Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.3.0, 5.2.1, 5.0.7
Affects Version/s: None
Component/s: Sharding
Labels:
- sharding-nyc-subteam1

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.2, v5.0
Sprint:
Sharding 2022-01-10, Sharding 2022-01-24, Sharding 2022-02-07, Sharding 2022-05-02
Linked BF Score:
36
Story Points:
4
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Brett Nawrocki
Reporter:: Randolph Tan
Participants:: Brett Nawrocki, Githook User, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Nov 12 2021 04:53:54 PM UTC
Updated:: Oct 29 2023 09:46:07 PM UTC
Resolved:: Feb 08 2022 07:36:52 PM UTC
Confidence Status Last Update:: 04/Jan/22 8:12 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates