tarantool / tarantool/doc

Rewrite the description of box.cfg.replication

Open
#2,811 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

factual error replication
Dominant language
CSS
Stars
15
Forks
49
Avg merge
1d 13h
Merged PRs (30d)
3

Description

the documentation is incorrect: https://www.tarantool.io/ru/doc/latest/reference/configuration/#cfg-replication-replication

en:

Since version 1.7.4. If replication is not an empty string, the instance is considered to be a Tarantool replica. The replica will try to connect to the master specified in replication with a URI (Universal Resource Identifier)

ru:

Для версий от 1.7.4. и выше. Если replication не содержит пустую строку, экземпляр считается репликой. Реплика попытается подключиться к мастеру, указанному в параметре replication по URI (унифицированному идентификатору ресурса)

this is wrong.

en:
however, in fact, in the cluster, both on the master and on the replica, the value 'replication' does not contain an empty string (it contains a list of all members of the replica-set)

ru:
на самом деле, в кластере, как на мастере, так и на реплике, значение 'replication' не содержит пустую строку (там содержится список всех членов replica-set)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked configuration documentation page and review the English and Russian descriptions of box.cfg.replication. Update both descriptions to reflect that a cluster's master and replica can contain the replica-set member list, then verify that the wording no longer claims a non-empty value alone identifies a replica.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.