Commit message (Expand) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | SERVER-60109 Ensure vector clock is recovered on step-up | Pierlauro Sciarelli | 2022-01-04 | 1 | -1/+1 |
* | SERVER-47568 Disable clusterTime gossiping for nodes in unreadable states | Jack Mulrow | 2021-05-04 | 1 | -0/+4 |
* | SERVER-49353 Refactor VectorClock's protected API | Pierlauro Sciarelli | 2020-08-27 | 1 | -28/+14 |
* | SERVER-49921 Optimised persistence and recovery of the VectorClock | Kaloian Manassiev | 2020-08-17 | 1 | -0/+20 |
* | SERVER-49921 Pull the `_vectorClockPersist` command out of the 'vector_clock_... | Kaloian Manassiev | 2020-08-11 | 1 | -9/+10 |
* | SERVER-49192 Persist the VectorClock for configTime and topologyTime causal c... | Pierlauro Sciarelli | 2020-08-08 | 1 | -1/+1 |
* | SERVER-49321 Make VectorClock::Component protected | Pierlauro Sciarelli | 2020-07-22 | 1 | -4/+5 |
* | SERVER-47914 Move clusterTime from LogicalClock to VectorClock | Kevin Pulo | 2020-06-05 | 1 | -8/+31 |
* | SERVER-46200 implement basic VectorClock service | Kevin Pulo | 2020-05-12 | 1 | -0/+100 |