tarantool / tarantool/doc

Use priorities when bootstrapping replica in supervised mode

Open
#4,565 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Product: Tarantool
Since: 3.3.0
Root document:

Details

Now, when working in replication.failover = supervised mode the
instance priorities specified in the
failover.replicasets.<replicaset-name>.priority section are used
to select the bootstrap leader when using bootstrap_strategy: auto.
The replica with the highest priority is chosen as a bootstrap leader.
If there are more than one instance with the highest priority the first
one sorted by name alphabetically is chosen.

Example:

replication:
  failover: supervised
failover:
  replicasets:
    replicaset-001:
      priority:
        instance-002: 5
        instance-003: -3
        instance-004: 5

Setting up the config like this will make Tarantool choose
instance-002 as the bootstrap leader.
Requested by @georgiy-belyanin in https://github.com/tarantool/tarantool/commit/2eee236f1e866a53daf1b02832ee022727770d22.

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 linked in the issue, then compare their current descriptions of bootstrap_strategy and replica priorities with the requested behavior. Document highest-priority leader selection and alphabetical name tie-breaking, and verify the YAML example is represented accurately in both relevant pages.

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
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.