Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.7.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-1645-Milestone-3

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10
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

Before deleting the MigrationCoordinatorDocument (here)
Before writing the TransactionCoordinatorDocument (refer to SERVER-38918)
~~Upon some specific calls to ShardRegistry::reload~~ (repurposed):
- ~~When a shard is added (here)~~
- ~~When a shard is removed (here)~~

depends on

SERVER-48717 Implement the persist/recover functionalities of the VectorClock

Closed

SERVER-49400 Differenciate VectorClock persist behavior based on cluster role

Closed

is depended on by

SERVER-49193 Recover the VectorClock on shard primary step up

Closed

related to

SERVER-62243 Wait for vector clock document majority-commit without timeout

Closed

Assignee:: Pierlauro Sciarelli
Reporter:: Pierlauro Sciarelli
Participants:: Githook User, Pierlauro Sciarelli
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jun 30 2020 02:24:09 PM UTC
Updated:: Oct 29 2023 10:06:18 PM UTC
Resolved:: Aug 08 2020 12:33:12 PM UTC