feedback: Configuration reference | Tarantool
Open
Nobody has claimed this yet.
config
reference
verify
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
<…> instance is writing (so the two instances are always in sync),
|and trying to take the lock|.
If the primary instance goes down for any reason, the lock wil<…>
It does not serve iproto requests, but executes Lua code (if it is started in separated fibers before a box.cfg() call), correct?
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 linked Hot Standby section in the configuration reference and compare it with the database hot-standby configuration reference. Verify the documented behavior around iproto requests and Lua execution before clarifying the affected text; done means the two references accurately answer the question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100