You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
replication.synchro_queue_max_size puts a limit on the number of
transactions in the master synchronous queue. replication.synchro_queue_max_size is measured in number of bytes to
be written (0 means unlimited, which was the default behaviour before).
This option affects only the behavior of the master, and defaults to
16 megabytes.
Now that replication.synchro_queue_max_size is set on the master node,
tarantool will discard new transactions that try to queue after the limit
is reached. If a transaction had to be discarded, user will get an error
message "The synchronous transaction queue is full".
This limitation does not apply during the recovery process.
The current synchro queue size can be known using box.info.synchro.queue.size:
Dev. issue: tarantool/tarantool#7486
Product: Tarantool
Since: 3.3.0
Root document: https://www.tarantool.io/en/doc/latest/reference/configuration/configuration_reference/
SME: @ Astronomax
Details
replication.synchro_queue_max_size
puts a limit on the number oftransactions in the master synchronous queue.
replication.synchro_queue_max_size
is measured in number of bytes tobe written (0 means unlimited, which was the default behaviour before).
This option affects only the behavior of the master, and defaults to
16 megabytes.
Now that
replication.synchro_queue_max_size
is set on the master node,tarantool will discard new transactions that try to queue after the limit
is reached. If a transaction had to be discarded, user will get an error
message "The synchronous transaction queue is full".
This limitation does not apply during the recovery process.
The current synchro queue size can be known using
box.info.synchro.queue.size
:[box-info-synchro] https://www.tarantool.io/en/doc/latest/reference/reference_lua/box_info/synchro/
Requested by @Astronomax in tarantool/tarantool@e319c21.
The text was updated successfully, but these errors were encountered: