[2pt] feedback: Developer’s guide | Tarantool
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Cartridge
Root document: https://www.tarantool.io/en/doc/latest/book/cartridge/cartridge_dev/#stateful-failover
SME: @ sergos
Peer reviewer: @
<…>tained from the state provider with the
long polling technique.
|All decisions are made by the coordinator – the one that holds the
lock. The coordinator is implemented as a built-in Cartridge role. There may
be many instances with the coordinator role enabled, but only one of
them can acquire the lock at the same time. We call this coordinator the “active”
one.
|The lock is released automatically when the TCP connection is cl<…>
Details
https://www.tarantool.io/en/doc/latest/book/cartridge/cartridge_dev/#stateful-failover
а я так и не понял, кому надо прописывать роль failover-coordinator (и в документации, кажется, на эту тему ничего нет). Каждому репликасету, в котором возможно переключение RW-ноды?
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
Start with the Stateful failover section in the Tarantool Cartridge Developer’s Guide at the linked documentation URL. Determine which replica sets should define the failover-coordinator role and update that section to answer the question clearly; the documentation is done when the role’s intended scope and configuration are explicit.
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
- Mostly clear
- Newbie friendliness
- 35/100