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-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

The persist method introduced in SERVER-48717 should behave in different ways depending on the cluster role.

Config server: don’t do anything because configTime and topologyTime are guaranteed from the oplog (last optimes on oplog)

Shard primary: call create/update with majority write concern

Shard secondary: call waitForInMemoryVectorClockToBePersisted on the primary (a PersistVectorClockCommand need to be created)

causes

SERVER-51328 Do not pass entire namespace string to db parameter when calling _vectorClockPersist

Closed

depends on

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

Closed

is depended on by

SERVER-49192 Persist the VectorClock for configTime and topologyTime casual consistency

Closed

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

Created:: Jul 09 2020 02:47:13 PM UTC
Updated:: Sep 03 2024 10:52:42 AM UTC
Resolved:: Jul 27 2020 10:49:56 AM UTC