config.reload_jitter option
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
The behavior is defined by the implementation in the commit linked from the issue (e4bc93cf69b63c7260769434cfc39ba90bccc84e), so read that first to confirm the interval, warning and reload semantics. Then find the existing documentation pages for the config:reload and config.reload options and add a reload_jitter entry covering the default of 0, the interval behavior and the YAML example. Done when the new section matches the commit's behavior and the docs build without broken links.
Written by the indexing model from the issue text.
Description
The config.reload_jitter option spreads fetches of a new configuration
from the remote configuration storage over the given number of seconds.
When an instance detects a new configuration, it fetches it at a random
moment within this interval and applies it when the interval ends. This
avoids a burst of simultaneous fetches in large clusters, while
instances still apply the configuration at about the same time.
The default value is 0, which preserves immediate reloads.
New configurations detected during the interval are handled in the next
interval, which starts after the current one ends. If the fetched
configuration is newer than the detected one, the instance does not
apply it, issues a warning, and applies the newest configuration at the
end of the next interval.
The option affects automatic reloads from the remote configuration
source in Tarantool Enterprise Edition. Explicit config:reload() calls
are not delayed and end the current interval.
Example:
config:
reload: auto
reload_jitter: 30
Requested by @Godrik0 in https://github.com/tarantool/tarantool/commit/e4bc93cf69b63c7260769434cfc39ba90bccc84e.
- 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 78/100
-
c api
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
krahets/hello-algo#1993 ·
-
DOC: Add an example for using Cheaper Inference with OpenAIModelPossibly taken @aiapienthusiast claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
huggingface/smolagents#2988 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ioos/compliance-checker#1375 ·
Maintainers usually reply within 1 day