new `box.info.status` - "waiting_for_own_rows"
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool
Since: 3.3.3, 3.4.1
Root document: https://www.tarantool.io/ru/doc/latest/reference/reference_lua/box_info/status/
SME: @ Astronomax
Details
The waiting_for_own_rows status can be relevant if a node that was once
a master crashed and lost some of its xlogs for some reason (e.g. manually
deleted by the user). In this case after rebooting, box.info.status will
be equal to waiting_for_own_rows, which means that the instance knows
that some of its transactions were lost from its xlogs and it is waiting
for them to be received via replication. While instance status is
waiting_for_own_rows it remains read-only.
Requested by @Astronomax in https://github.com/tarantool/tarantool/commit/61cb5b5e3414a2ac0aac5682bfd2435457ae87bd.
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 root document for box.info.status at the Tarantool documentation URL and review the existing status descriptions. Document waiting_for_own_rows, including that the instance waits for lost transactions via replication and remains read-only; done means the new status and its behavior are clearly described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100