-
Notifications
You must be signed in to change notification settings - Fork 43
Description
Product: Tarantool
Since: 1.7.5
Root document: https://www.tarantool.io/en/doc/latest/book/replication/repl_monitoring/
Details
<…>ой
По умолчанию: 300
Динамический: даreplication_timeout¶
|Для версий от 1.8.2. и выше. Если у мастера нет обновлений для реплик, он отправляет сообщения контрольного сигнала каждые replication_timeout секунд, а каждая реплика возвращает сообщение подтверждения.
|И мастер, и реплики запрограммированы разорвать соединение при о<…>
https://www.tarantool.io/ru/doc/2.6/reference/configuration/#cfg-replication-replication-timeout
Replication monitoring doc in https://www.tarantool.io/ru/doc/2.3/book/replication/repl_monitoring/ says:
A replica sends heartbeat messages to the master every second, and the master is programmed to reconnect automatically if it does not see heartbeat messages within replication_timeout seconds.
which does not correspond to the current fragment
=====
https://www.tarantool.io/en/doc/latest/book/replication/repl_monitoring/ is not quite right:
A master sends heartbeat messages to a replica every second
Every second is by default. It is better to say:
If the master has no updates to send to the replicas, it sends heartbeat messages every
replication_timeout
seconds.
So, https://www.tarantool.io/en/doc/latest/reference/configuration/#cfg-replication-replication-timeout is correct.