-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Cluster Scalability
-
ClusterScalability Mar31-Apr14, ClusterScalability Apr28-May09
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
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
-