Uh oh!
There was an error while loading. Please reload this page.
cluster: use dynamic whitelist policy for proxy access - #833
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
679a13f to
ab38a22CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ab38a22 to
3b6c175CompareUh oh!
There was an error while loading. Please reload this page.
3b6c175 to
a4147e2CompareUh oh!
There was an error while loading. Please reload this page.
fruch
commented
May 4, 2026
I can confirm taking this PR in scylladb/scylla-cluster-tests#14512, and it worked as expected via public address |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
fab5d7b to
be1794dCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
be1794d to
589a752Compare| @mock_session_pools | ||
| def test_session_preserves_down_event_discounting_after_endpoint_update(self, *_): | ||
| @total_ordering | ||
| class _DeterministicHashEndPoint(EndPoint): |
…ress connections Switch python-driver to PR scylladb/python-driver#833 branch which introduces DynamicWhiteListRoundRobinPolicy. When SCT connects via public addresses (IP_SSH_CONNECTIONS == "public"), use this policy instead of WhiteListRoundRobinPolicy. DynamicWhiteListRoundRobinPolicy dynamically tracks which host the control connection resolves to and only routes queries there, solving the problem where the driver discovers private IPs from system tables that are unreachable from the client when using public/proxy access.
dkropachev
commented
May 11, 2026
Change is too intrusive, given pre-existing mess in node status handling it will only contribute to it, we found easier solution - #878, this PR is closed |
Pre-review checklist
./docs/source/.Fixes:annotations to PR description.