@@ -19,8 +19,27 @@ box.info.synchro
19
19
20
20
* ``queue ``:
21
21
22
+ - ``owner `` -- ID of the replica that owns the synchronous transaction queue.
23
+ Once the owner instance appears, all other instances become read-only.
24
+ If the ``owner `` field is ``0 ``, then every instance is writeable,
25
+ but it can't create any synchronous transactions.
26
+ To claim or re-claim the queue, use :ref: `box.ctl.promote() <box_ctl-promote >` on the instance that you want
27
+ to promote.
28
+ Since version :doc: `2.10.0 </release/2.10.0 >`.
29
+
30
+ - ``term `` -- current queue term.
31
+ It contains the term of the last ``PROMOTE ``.
32
+ Usually it is equal to :ref: `box.info.election.term <box_info_election >`.
33
+ However, the queue term value may be less than the corresponding one in election term.
34
+ It can happen when a new round of elections started, but no one has promoted yet.
35
+ Since version :doc: `2.10.0 </release/2.10.0 >`.
36
+
22
37
- ``len `` -- current number of entries that are waiting in the queue.
23
38
39
+ - ``busy `` -- the boolean value is set to ``true `` if there is a synchronous transaction in progress.
40
+ Until the active transaction is complete, any other incoming synchronous transactions will be delayed.
41
+ Since version :doc: `2.10.0 </release/2.10.0 >`.
42
+
24
43
* ``quorum `` -- evaluated value of the
25
44
:ref: `replication_synchro_quorum <cfg_replication-replication_synchro_quorum >` configuration option.
26
45
Since version :doc: `2.5.3 </release/2.5.3 >`, the option can be set as a dynamic formula.
0 commit comments