feedback: Automated leader election | Tarantool
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
<…>other internal things need direct
connection between the nodes.
|Also, if election is enabled on the node, it won’t replicate from any nodes except
the newest leader. This is done to avoid the issue when a new leader is elected,
but the old leader has somehow survived and tries to send more changes
to the other nodes.|
Term numbers also work as a kind of a filter.
For example, you <…>
https://www.tarantool.io/en/doc/latest/book/replication/repl_leader_elect/#leader-election-process
Это неправда. Можно просто удалить целиком этот кусок . Дополнительные пояснения не нужны, т к у нас всегда каждый из узлов принимает репликацию от всех.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the linked leader-election-process documentation and locate the highlighted passage about replication from only the newest leader. Remove that passage as requested, then review the surrounding section to ensure the explanation remains coherent and the documentation builds successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100