tarantool / tarantool/doc

config: mark instances as non-appointable by the supervised failover

Open
#4,993 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.3 3.4 config
Dominant language
CSS
Stars
15
Forks
49
Avg merge
1d 13h
Merged PRs (30d)
3

Description

This issue has been created manually due to error in parsing title of https://github.com/tarantool/tarantool-ee/commit/5cbe9e37f067ebc3e20d36eb89391cd913252e95


Dev. issues: (https://github.com/tarantool/tarantool-ee/issues/991, https://github.com/tarantool/tarantool/issues/10842)

Product: Tarantool
Since: 3.3.0
Root document:

Details

failover.replicasets.<replicaset-name>.learners section allows to
specify instances that are ignored by the supervised failover
coordinator when selecting a master.

Note: if a learner instance is in RW mode, the coordinator stops the
failover process and waits until the instance transitions to RO mode.

Example. Specify "instance-002" and "instance-003" as learners and make
them not selected as masters:

failover:
  replicasets:
    replicaset-001:
      learners:
        - instance-002
        - instance-003

A coordinator configured like this ignores these two instances when
chooses a master and forbids executing "switch" command on them.

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 configuration reference and supervised failover documentation pages linked under Root document. Check how the failover.replicasets..learners setting and RW-to-RO behavior are currently described. Done means the documentation explains that learners are excluded from master selection and cannot run the switch command, with the instance-002 and instance-003 YAML example.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.