- box.info.gc()
– a checkpoint’s vclock value. gc().checkpoints[n].signature – a sum of a checkpoint’s vclock’s components. gc().checkpoint_is_in_progress – true if a checkpoint is in progress, otherwise false gc().vclock
- Class luatest.server
Server:wait_for_vclock (vclock) Wait until the server’s own vclock reaches at least the given value. Including the local component. Parameters: vclock: (tab) Server’s own vclock to reach.
- box.read_view.list()
: 1172.202995842 signature: 49 is_system: false status: open vclock: &1 {1: 49} name: read_view2 id: 2 ...
- box.info.replication_anon()
: {1: 1} f58e4cb0-e0a8-42a1-b439-591dd36c8e5e: id: 0 uuid: f58e4cb0-e0a8-42a1-b439-591dd36c8e5e lsn: 0 downstream: status: follow idle: 0.0041349999992235 vclock: {1
- box.info.replication
(Notice that the table may have multiple pairs although vclock is a singular name).
- Tarantool 2.2.3
Local space operations are now counted in 0th vclock component. Every instance may have its own 0-th vclock component not matching others’.
- Removing instances
-e437-4296-85b0-d27a0621613e lsn: 0 3: id: 3 uuid: bb362584-c265-4e53-aeb6-450ae818bf59 lsn: 0 -- upstream is absent downstream: status: follow idle: 0.26624799999991 vclock
- Tarantool 1.10.6
Local space operations are now counted in 0th vclock component. Every instance may have its own 0-th vclock component not matching others’.
- Submodule box.info
This value can also be retrieved with tarantool.uptime(). uuid corresponds to replication[n].uuid (see here). vclock is a table with the vclock values of all instances in a replica set which have made
- Keys used in requests and responses
Vclock keys The vclock (vector clock) is a log sequence number map that defines the version of the dataset stored on the node.
- Tarantool 2.3.2
Local space operations are now counted in 0th vclock component. Every instance may have its own 0-th vclock component not matching others’.
- Monitoring a replica set
cd3c7da2-a638-4c5d-ae63-e7767c3a6896 lsn: 31 upstream: status: follow idle: 43.187747001648 peer: replicator@192.168.0.102:3301 lag: 0 downstream: vclock
- Tarantool 1.10.13
For example, 0...0.xlog, covering everything up to vclock {1: 15} and 0...09.snap, corresponding to vclock {1: 9} (gh-6794).
- Tarantool 2.8.4
For example, 0...0.xlog, covering everything up to vclock {1: 15} and 0...09.snap, corresponding to vclock {1: 9} (gh-6794).
- Understanding the binary protocol
of 1 component) 01 MP_UINT = 1 = id (part 1 of vclock) 06 MP_UINT = 6 = lsn (part 2 of vclock) 5a Body Map Item #2
- box.info()
: 1: id: 1 uuid: 1738767b-afa3-4987-b485-c333cf83415b lsn: 16 signature: 16 status: running vinyl: [] uptime: 21 lsn: 16 sql: [] gc: [] pid: 20293 memory: [] vclock
- Tarantool 2.4.1
Local space operations are now counted in 0th vclock component. Every instance may have its own 0-th vclock component not matching others’.
- File formats
: " 7b 7d "{}" = vclock value, initially blank ...
- Replication cluster upgrade
Play the operations from the newer xlog starting from this vclock on the instance.
- Tarantool 1.10.14
For example, 0...0.xlog that covers everything up to vclock {1: 15} and 0...09.snap corresponding to vclock {1: 9} (gh-6794).
- Replication requests and responses
Each master’s request includes a vclock pair corresponding to that master – its instance ID and its LSN, independent from other masters.
- Resolving replication conflicts
missing in the report), because the downstream has encountered the same error: # replication statuses (report from master #3) tarantool> box.info --- - version: 1.7.4-52-g980d30092 id: 3 ro: false vclock
- Module cartridge.failover
Returns: (boolean) true / false is_vclockkeeper () Check if current instance has persisted his vclock. Returns: (boolean) true / false is_paused () Check if failover paused on current instance.
- Recovering from a degraded state
fd 13, aka 192.168.0.101:58244 2: id: 2 uuid: fb252ac7-5c34-4459-84d0-54d248b8c87e lsn: 0 3: id: 3 uuid: fd7681d8-255f-4237-b8bb-c4fb9d99024d lsn: 0 downstream: vclock
- Read views
a read view, you can see the information about it by calling read_view_object:info(). tarantool> read_view1:info() --- - timestamp: 66.606817935 signature: 24 is_system: false status: open vclock
- Function box.snapshot
It goes through the log, removes duplicating operations from the memory and creates a new *.vylog file, giving it the name according to the vclock of the new checkpoint, with “create” operations only.
- Orphan status
Criteria for electing a leader include vclock value (largest is best), and whether it is read-only or read-write (read-write is best unless there is no other choice).
- Tarantool 1.7
{vclock,status,error} to box.info.replication[instance_id].upstream.{vclock,status,error}. All registered replicas from box.space.
- Tarantool 2.10.5
Fixed an assertion failure on master when a replica resubscribes with a smaller vclock than previously seen (gh-5158).
- Replication architecture
Here vclock contains log sequence numbers (827 and 584) for instances with instance IDs 1 and 2.
- Tarantool 2.8.2
Now Tarantool yields when it scans .xlog files for the latest applied vclock and finds the right place to start recovering from.
- Tarantool 2.7.3
Now Tarantool yields when it scans .xlog files for the latest applied vclock and finds the right place to start recovering from.
- Tarantool 2.10.0
For example, 0...0.xlog, covering everything up to vclock {1: 15} and 0...09.snap, corresponding to vclock {1: 9} (gh-6794).
- Tarantool 1.10
(Replication) Add vclock for safer hot standby switch(gh-3002). (Replication) Master row is skipped forever in case of wal write failure(gh-2283).
- Configuration reference
tarantool> 2019-12-13 20:34:37.424 [71329] main/117/applier/ I> subscribed 2019-12-13 20:34:37.424 [71329] main/117/applier/ I> remote vclock {1: 5} local vclock {0: 10, 1: 5} 2019-12-13 20:34
- Metrics reference
tnt_info_vclock LSN number in vclock. This metric always has the label {id="id"}, where id is the instance’s number in the replica set. tnt_replication_lsn LSN of the tarantool instance.
- Developer’s guide
Even when the old leader is demoted, it remains the vclockkeeper until the new leader successfully awaits and persists its vclock on the external storage.
