Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.9.0
Affects Version/s: None
Component/s: Sharding
Labels:
- PM-234-T-lifecycle

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2021-01-25
Story Points:
1
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

There's a separate data consistency check we already have implement to verify the config.collections info is consistent with listCollections on the shards so the combination of knowing the collection exists with a new UUID in combination with the title is sufficient.

depends on

SERVER-51130 Implement onReshardingFieldsChanges for donor and recipient state machines

Closed

SERVER-51131 Implement RecipientStateMachine::onReshardingFieldChanges

Closed

SERVER-52742 Ensure both donorFields and recipientFields exists on the original collection entry after a resharding operation commits

Closed

SERVER-52747 Implement rename collection functionality on resharding recipient

Closed

SERVER-52797 Change resharding shard refresh code to only refresh the original namespace after the operation has committed

Closed

Assignee:: Max Hirschhorn
Reporter:: Blake Oler
Participants:: Blake Oler, Githook User, Max Hirschhorn
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Nov 18 2020 03:18:56 PM UTC
Updated:: Oct 29 2023 10:00:17 PM UTC
Resolved:: Jan 12 2021 12:43:02 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates