summaryrefslogtreecommitdiff
path: root/src/mongo/db/vector_clock.h
Commit message (Collapse)AuthorAgeFilesLines
* SERVER-63742 Default topology time in shard can lead to infinite refresh in ↵Antonio Fuschetto2022-03-021-2/+17
| | | | shard registry
* SERVER-59053 VectorClock is not gossiped in sessions started by a ↵Tommaso Tocci2021-12-161-1/+1
| | | | direct-to-shard command
* SERVER-54252 Cleanup legacy configOpTime gossipingTommaso Tocci2021-08-051-10/+0
|
* SERVER-57446 fix clang-tidy header issues and add header-filterDaniel Moody2021-08-021-2/+2
|
* SERVER-47568 Disable clusterTime gossiping for nodes in unreadable statesJack Mulrow2021-05-041-4/+15
|
* SERVER-54167: Advance VectorClock on configOpTime advancementJordi Serra Torrens2021-02-041-0/+8
|
* SERVER-50998 Remove getClusterTimeForReplicaSet()Kevin Pulo2020-09-171-7/+0
|
* SERVER-48433 Remove LogicalClock facadeKevin Pulo2020-09-171-0/+7
|
* SERVER-49970 Prefer the VectorClock's ConfigTime to configOpTime when ↵Pierlauro Sciarelli2020-09-011-0/+3
| | | | | | | querying config servers \ Co-authored-by: Pierlauro Sciarelli <pierlauro.sciarelli@mongodb.com> Co-authored-by: Kevin Pulo <kevin.pulo@mongodb.com>
* SERVER-49353 Refactor VectorClock's protected APIPierlauro Sciarelli2020-08-271-50/+44
|
* SERVER-49921 Optimised persistence and recovery of the VectorClockKaloian Manassiev2020-08-171-25/+7
|
* SERVER-49921 Pull the `_vectorClockPersist` command out of the ↵Kaloian Manassiev2020-08-111-5/+12
| | | | | | | 'vector_clock_mongod' library It should be in the same library where the commands are included, rather than together with the VectorClock implementation.
* SERVER-49192 Persist the VectorClock for configTime and topologyTime causal ↵Pierlauro Sciarelli2020-08-081-17/+16
| | | | consistency
* SERVER-49321 Make VectorClock::Component protectedPierlauro Sciarelli2020-07-221-3/+31
|
* SERVER-48717 Implement the persist/recover functionalities of the ↵Pierlauro Sciarelli2020-07-161-9/+5
| | | | VectorClock [last additional changes]
* SERVER-48717 Implement the persist/recover functionalities of the VectorClockPierlauro Sciarelli2020-07-161-0/+26
|
* SERVER-49315 Allow definition of custom vector clock gossip formatsPierlauro Sciarelli2020-07-071-3/+29
|
* SERVER-49308 Allow to advance any VectorClock time for testingPierlauro Sciarelli2020-07-071-1/+1
|
* SERVER-47406 Implement the persistence and tracking of topologyTimeKevin Pulo2020-07-011-1/+3
|
* SERVER-47914 Move clusterTime from LogicalClock to VectorClockKevin Pulo2020-06-051-14/+128
|
* SERVER-46200 implement basic VectorClock serviceKevin Pulo2020-05-121-0/+148