tarantool / tarantool/doc

feedback: Automated leader election | Tarantool

Open
#2,395 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Product: Tarantool
Root document: https://www.tarantool.io/en/doc/latest/book/replication/repl_leader_elect/
SME: @ sergepetrenko
Peer reviewer:

Details

<…>ese old leader’s transactions since it is not a leader anymore.
|Another point to keep in mind is that when a new leader is elected,
it won’t automatically finalize synchronous transactions
left from the previous leader. This must be done manually using
the box.ctl.promote function. In the future, it is going to be
done automatically.|

<…>

https://www.tarantool.io/en/doc/latest/book/replication/repl_leader_elect/

@ sergepetrenko said that it is not so.

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

Read the automated leader election documentation at the linked root document, focusing on the quoted statement about finalizing synchronous transactions and box.ctl.promote. Check the SME's feedback and determine the intended correction before editing; done means the documentation accurately reflects the reported behavior.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.