• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tarantool / tarantool / 38389632732
88%

Build:
DEFAULT BRANCH: master
Ran 13 Oct 2026 11:35AM UTC
Jobs 1
Files 528
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

13 Oct 2026 11:21AM UTC coverage: 87.931% (+0.008%) from 87.923%
38389632732

push

github

georgiy-belyanin
config: add reload jitter option

Currently, when a new configuration is published in remote
configuration storage, every cluster instance fetches it immediately.
In large clusters, hundreds of concurrent requests can overload the
remote configuration storage.

This patch adds the config.reload_jitter option to spread automatic
reloads over time and avoid this request burst. The option accepts a
non-negative number of seconds and defaults to zero. It is used by the
Enterprise remote configuration storage source.

Part of tarantool/tarantool-ee#1934

NO_CHANGELOG=EE-only option

@TarantoolBot document
Title: config.reload_jitter option

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:

```yaml
config:
  reload: auto
  reload_jitter: 30
```

72425 of 121314 branches covered (59.7%)

108794 of 123727 relevant lines covered (87.93%)

1413155.81 hits per line

Coverage Regressions

Lines Coverage ∆ File
4
90.71
-0.06% src/box/box.cc
4
92.45
-0.4% src/box/vy_scheduler.c
4
93.31
-1.27% src/lib/swim/swim_io.c
4
22.64
-0.08% src/lib/uri/uri_parser.c
4
88.33
-6.67% src/lua/minifio.c
2
96.3
-3.7% src/lib/core/backtrace.c
2
96.15
-3.85% src/lib/core/iostream.h
2
86.9
-0.29% src/lib/core/say.c
2
88.97
-0.35% src/lua/init.c
1
89.09
-0.61% src/box/engine.c
1
97.01
-1.49% src/box/engine.h
1
96.17
-0.17% src/box/relay.cc
1
96.0
-4.0% src/box/user_def.c
1
92.71
-0.04% src/box/vinyl.c
1
90.42
-0.08% src/box/vy_log.c
1
96.43
-0.71% src/box/vy_point_lookup.c
1
95.74
0.0% src/box/vy_range.c
1
85.82
0.01% src/box/xlog.c
1
89.82
-0.04% src/box/xrow.c
Jobs
ID Job ID Ran Files Coverage
1 38389632732.1 13 Oct 2026 11:35AM UTC 528
87.93
GitHub Action Run
Source Files on build 38389632732
  • Tree
  • List 528
  • Changed 35
  • Source Changed 0
  • Coverage Changed 35
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • e4bc93cf on github
  • Prev Build on master (#38244949203)
  • Next Build on master (#38550570356)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc