Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Sharding
Labels:

Assigned Teams:

Catalog and Routing
Story Points:
3
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 means that running a new migration immediately after a previous one failed with timeout can fail because there's a conflicting chunk migration in progress.

is depended on by

SERVER-72329 Complete TODO listed in SERVER-30179

Blocked

is duplicated by

SERVER-30179 moveChunk doesn't obey maxTimeMS consistently

Closed

is related to

SERVER-30179 moveChunk doesn't obey maxTimeMS consistently

Closed

SERVER-47003 MaxTimeMSExceeded on _configsvrMoveChunk can lead to blocking future migrations for that chunk

Closed

SERVER-48699 MaxTimeMS may expire in range_deleter_interacts_correctly_with_refine_shard_key.js test before _configsvrMoveChunk command started

Closed

Assignee:: Unassigned
Reporter:: Spencer Brody (Inactive)
Participants:: Connie Chen, Esha Maharishi, Spencer Brody
Votes:: 0 Vote for this issue
Watchers:: 4 Start watching this issue

Created:: May 12 2020 06:36:30 PM UTC
Updated:: Sep 13 2024 11:11:34 AM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates