Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.14, 5.0.4, 5.1.0-rc0
Affects Version/s: 4.9.0, 4.0.23, 4.4.4, 4.2.13
Component/s: Sharding
Labels:
- sharding-wfbf-day

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v5.0, v4.4
Sprint:
Sharding EMEA 2021-06-14, Sharding EMEA 2021-06-28
Case:
Linked BF Score:
50

Currently, the migration source manager is waiting up to 6 hours for a receiver to finish cleaning overlapping range deletion tasks before starting a move chunk.

This can result in migrations being blocked on both sides for an unreasonable amount of time: a much smaller timeout must be used for this specific case, aborting the migration in case the range doesn't get cleared.

causes

SERVER-58240 Wait for range deletion timeout is too short for FSM tests

Closed

SERVER-58905 Fix test that assumes receiveChunkWaitForRangeDeleterTimeoutMS parameter existence in 5.0

Closed

SERVER-59636 Default timeout for receiveChunkWaitForRangeDeleterTimeoutMS is too low

Closed

Assignee:: Marcos José Grillo Ramirez

Reporter:: Pierlauro Sciarelli

Participants:: Githook User, Kaloian Manassiev, Marcos José Grillo Ramirez, Pierlauro Sciarelli, Vivian Ge

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: Mar 22 2021 07:57:43 PM UTC

Updated:: Oct 29 2023 09:55:54 PM UTC

Resolved:: Jun 29 2021 03:04:40 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates