Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- resharding-improvements
- resharding-success-rate-improvements

Assigned Teams:

Cluster Scalability
Backwards Compatibility:
Fully Compatible
Sprint:
ClusterScalability Mar31-Apr14, ClusterScalability Apr28-May09
Confidence Status:
None
Work Order:
3

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

The resharding donor forces a catalog cache refresh just before transitioning to done, which forces a no-op write. This write uses a write concern timeout of 60 seconds - currently we don't retry on WriteConcernTimeout, nor do currently consider this a transient error, and so if there's slowness or some network issue that causes this write to fail, we'll fail the entire resharding operation with an fassert.

is related to

SERVER-104317 All resharding services should retry on WCEs

Open

related to

SERVER-92936 Writes with a {w: majority, wtimeout:0} fail in case of network errors.

Backlog

SERVER-104258 Resharding Can Hang If Recipient Fails During ShardsvrReshardRecipientClone

Backlog

SERVER-104317 All resharding services should retry on WCEs

Open

Assignee:: Janna Golden
Reporter:: Randolph Tan
Participants:: Githook User, Janna Golden, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: Mar 17 2025 10:18:16 AM UTC
Updated:: May 20 2025 08:09:09 PM UTC
Resolved:: May 05 2025 05:31:55 PM UTC
Confidence Status Last Update:: 26/Mar/25 4:20 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates