pool: get status of an instance via WATCH_ONCE #380
Comments
DerekBum
added a commit
that referenced
this issue
Mar 5, 2024
Starting from Tarantool version >= 3.0.0 `WatchOnce` requset is supported. So we can get instance status using this request instead of calling `box.info`. This way user can add instances to the pool without the `execute` role. Closes #380
2 tasks
DerekBum
added a commit
that referenced
this issue
Mar 5, 2024
Starting from Tarantool version >= 3.0.0 `WatchOnce` requset is supported. So we can get instance status using this request instead of calling `box.info`. This way user can add instances to the pool without the `execute` role. Closes #380
DerekBum
added a commit
that referenced
this issue
Mar 5, 2024
Starting from Tarantool version >= 3.0.0 `WatchOnce` requset is supported. So we can get instance status using this request instead of calling `box.info`. This way user can add instances to the pool without the `execute` role. Closes #380
DerekBum
added a commit
that referenced
this issue
Mar 5, 2024
Starting from Tarantool version >= 3.0.0 `WatchOnce` requset is supported. So we can get instance status using this request instead of calling `box.info`. This way user can add instances to the pool without the `execute` role. Closes #380
DerekBum
added a commit
that referenced
this issue
Mar 5, 2024
Starting from Tarantool version >= 3.0.0 `WatchOnce` requset is supported. So we can get instance status using this request instead of calling `box.info`. This way user can add instances to the ConnectionPool without the `execute` access. Closes #380
oleg-jukovec
pushed a commit
that referenced
this issue
Mar 6, 2024
Starting from Tarantool version >= 3.0.0 `WatchOnce` requset is supported. So we can get instance status using this request instead of calling `box.info`. This way user can add instances to the ConnectionPool without the `execute` access. Closes #380
oleg-jukovec
added a commit
that referenced
this issue
Mar 6, 2024
Overview
The small release improves the ConnectionPool. The ConnectionPool
is no longer required execute access for `box.info` from a user
for Tarantool >= 3.0.0.
Breaking changes
There are no breaking changes in the release.
New features
`execute` access for `box.info` is no longer required for
ConnectionPool for a Tarantool version >= 3.0.0 (#380).
Bugfixes
`ConnectionPool.Remove()` does not notify a `ConnectionHandler`
after an instance is already removed from the pool (#385).
Merged
oleg-jukovec
added a commit
that referenced
this issue
Mar 6, 2024
Overview
The small release improves the ConnectionPool. The ConnectionPool
is no longer required execute access for `box.info` from a user
for Tarantool >= 3.0.0.
Breaking changes
There are no breaking changes in the release.
New features
`execute` access for `box.info` is no longer required for
ConnectionPool for a Tarantool version >= 3.0.0 (#380).
Bugfixes
`ConnectionPool.Remove()` does not notify a `ConnectionHandler`
after an instance is already removed from the pool (#385).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
At now we make evals on the server side to get an instance status. It requires execute access for a user.
We could use
WATCH_ONCEinstead for servers that support it. It will allow us to require fewer rights from the user.The text was updated successfully, but these errors were encountered: