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

tarantool / tarantool / 42020345846
88%

Build:
DEFAULT BRANCH: master
Ran 05 Nov 2026 11:51AM UTC
Jobs 1
Files 526
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

05 Nov 2026 11:36AM UTC coverage: 88.138% (+0.01%) from 88.127%
42020345846

push

github

locker
config: allow to run vshard routers on application threads

This commits adds a new configuration option that makes Tarantool load
and configure the vshard router on all threads of the specified thread
group instead of the main thread.

Note that the corresponding healthcheck is disabled in this case because
a healthcheck function isn't allowed to yield while we need to yield in
the main thread order to inquire the state of the vshard router running
in an application thread. This issue will be addressed in the future.

Closes #13574

@TarantoolBot document
Title: Running vshard routers on application threads

The new configuration option `sharding.router_thread_group` specifies
the name of the thread group where the vshard router module will be
loaded and configured. The group must be defined in `threads.groups`.
The default value is "tx" (run the router on the main thread).

Using an alternative thread group is the way to scale the vshard router
performance within the same process, without spawning extra Tarantool
instances.

Notes about using vshard in application threads:
 * Adding a function to the global Lua namespace `_G` in an application
   thread does not export the function in IPROTO. Instead you should use
   `box.iproto.export()`, which works both in the main and application
   threads.
 * To grant a user a permission to execute a function exported in an
   application thread over IPROTO, you should add the corresponding
   `lua_call` privilege to the config file. The execute access to
   the universe or the super role won't work.
 * Each application thread acts as an independent router although they
   all take requests from the same IPROTO port. In particular, this
   means that `vshard.router.bootstrap` should be called once or
   `if_not_bootstrapped` option should be used, just like with routers
   running on different Tarantool instances.

72880 of 121732 branches covered (59.87%)

109519 of 124258 relevant lines covered (88.14%)

1438459.08 hits per line

Coverage Regressions

Lines Coverage ∆ File
4
92.67
-0.13% src/box/vinyl.c
4
94.15
-1.6% src/box/vy_range.c
3
22.64
-0.06% src/lib/uri/uri_parser.c
2
90.71
0.0% src/box/box.cc
2
93.81
-0.41% src/box/xrow_update_field.c
2
86.61
-0.29% src/lib/core/say.c
2
95.45
-4.55% src/lib/json/json.h
1
85.98
-0.07% src/box/xlog.c
1
96.55
-1.15% src/lib/core/histogram.c
1
96.99
0.3% src/lib/msgpuck/msgpuck.h
1
98.21
-0.02% src/lib/vclock/vclock.c
1
79.44
-0.25% src/main.cc
Jobs
ID Job ID Ran Files Coverage
1 42020345846.1 05 Nov 2026 11:51AM UTC 526
88.14
GitHub Action Run
Source Files on build 42020345846
  • Tree
  • List 526
  • Changed 25
  • Source Changed 0
  • Coverage Changed 25
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • 68fe9c1d on github
  • Prev Build on master (#42005501570)
  • Next Build on master (#42183278601)
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