Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 2.8.0-rc2
Component/s: Sharding
Labels:
None

Assigned Teams:

Sharding
Operating System:
ALL
Sprint:
Sharding 10 (02/19/16)
Confidence Status:
None
Work Order:
3

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

There are cases where the donor shard can abort the migration without contacting the recipient shard. If it starts another migration before the recipient shard realizes it, then it can call _cloneMigrate against the donor shard and interfere with the new migration. A similar issue exist for _transferMods as well.

duplicates

SERVER-20290 Recipient shard for migration can continue on retrieving data even after donor shard aborts

Closed

is related to

SERVER-16432 Chunk migration data structures not properly synchronized with storage engines that offer document-level locking

Closed

Assignee:: [DO NOT USE] Backlog - Sharding Team
Reporter:: Randolph Tan
Participants:: [DO NOT USE] Backlog - Sharding Team, Randolph Tan
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Dec 12 2014 09:59:03 PM UTC
Updated:: Dec 06 2022 04:58:07 AM UTC
Resolved:: Feb 01 2016 08:23:46 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates