Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.3.0, 5.1.2, 5.0.6, 5.2.0-rc4
Affects Version/s: None
Component/s: Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v5.2, v5.1, v5.0
Sprint:
Sharding EMEA 2022-01-10
Confidence Status:
None
Work Order:
3

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

When starting a moveChunk, it should be ensured that there is no unfinished migration pending recovery (even for other collections). Ensuring that will guarantee that there's never more than one document in config.migrationCoordinators.

This prevents the situation that led to ~~SERVER-62245~~.

causes

SERVER-65371 MigrationSourceManager running on secondary node may trip invariant

Closed

is related to

SERVER-62245 MigrationRecovery must not assume that only one migration needs to be recovered

Closed

SERVER-60521 Deadlock on stepup due to moveChunk command running uninterrupted on secondary

Closed

Assignee:: Jordi Serra Torrens
Reporter:: Jordi Serra Torrens
Participants:: Githook User, Jordi Serra Torrens
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Dec 29 2021 03:16:51 PM UTC
Updated:: Oct 29 2023 09:44:38 PM UTC
Resolved:: Dec 30 2021 11:43:20 AM UTC
Confidence Status Last Update:: 29/Dec/21 3:31 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates