Describe read view creation throttling
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- lua
- Domain
- documentation
Research direction
The text to add is already drafted in the issue. Start with the Limitations section of the read views page (linked as platform/ddl_dml/read_views) and the reference page for box.read_view.open (reference/reference_lua/box_read_view/open). Add the 100 ms throttle, the fiber blocking, and the exemption for system read views to both, then check that the cross-references (read_views_limitations, box-read_view-open) resolve in a local docs build. Done when both pages describe the same behavior and the links work.
Written by the indexing model from the issue text.
Description
Since: 3.9.0, 3.8.2, 3.7.2
https://www.tarantool.io/en/doc/latest/platform/ddl_dml/read_views/#limitations
Read view creation is rate-limited: a new read view can be opened no more
often than once every 100 milliseconds. If
:ref:box.read_view.open() <box-read_view-open> is called before this
interval has elapsed since the previous read view was opened, it blocks
the calling fiber until the interval has elapsed. System read views
created, for example, to make a
:ref:checkpoint <book_cfg_checkpoint_daemon> or join a new
:ref:replica <replication-architecture> are not affected.
--
https://www.tarantool.io/en/doc/latest/reference/reference_lua/box_read_view/open/
Read view creation is rate-limited
(see :ref:the limitations <read_views_limitations>):
if this function is called too soon after another read view was opened,
it blocks the calling fiber until the interval between two consecutive
read view opens (100 milliseconds) has elapsed.
Requested by @Gumix in https://github.com/tarantool/tarantool/commit/c182334504f2ba7762d6b430d4bb2dd0e05259f4.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from tarantool/doc
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
memcs
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Similar issues
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
area:connector bug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tester-army/e2e#1015 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
chroma-core/chroma#7879 ·
Maintainers usually reply within 1 day