Loading...

XML

Word

Printable

JSON

Type: Improvement
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-05-18, Sharding 2020-06-01, Sharding 2020-06-15
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 cluster-wide cluster time is currently managed by the LogicalClock class. This should be moved to instead be the ClusterTime component of the VectorClock service, and the LogicalClock class removed.

causes

SERVER-50322 Fix libfuzzertests compile

Closed

SERVER-51074 VectorClock is not gossiped correctly on newly started sessions

Closed

depends on

SERVER-46200 Implement a VectorClockService

Closed

SERVER-48406 Add onBecomeArbiter to ReplicaSetAwareService

Closed

SERVER-48534 NetworkTestEnv should not schedule responses for fire-and-forget commands

Closed

is depended on by

SERVER-44097 Remove term from config server opTime tracking

Closed

SERVER-47406 Implement the persistence and tracking of a cluster `topologyTime`

Closed

is related to

SERVER-48610 ReplicaSetAwareService callbacks don't occur in ReplicationCoordinatorImpl tests

Closed

(2 is depended on by, 1 is related to)

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

Created:: May 04 2020 04:05:07 AM UTC
Updated:: Oct 29 2023 10:08:44 PM UTC
Resolved:: Jun 05 2020 12:56:18 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates