Skip to content

control-connection: keep zero-token hosts#855

Draft
dkropachev wants to merge 6 commits intomasterfrom
fix/zero-token-host-refresh
Draft

control-connection: keep zero-token hosts#855
dkropachev wants to merge 6 commits intomasterfrom
fix/zero-token-host-refresh

Conversation

@dkropachev
Copy link
Copy Markdown
Collaborator

Summary

  • Keep zero-token hosts in topology metadata without assigning token-map entries.
  • Ignore zero-token hosts by default in load-balancing query plans while preserving explicit whitelist opt-outs.
  • Prevent hosts being added or marked up from entering query plans until all pool futures complete.

Tests

  • uv run python -m pytest -q tests/unit/test_cluster.py::ClusterTest::test_on_add_excludes_host_from_query_plan_until_pool_futures_complete tests/unit/test_cluster.py::ClusterTest::test_on_up_excludes_host_from_query_plan_until_pool_futures_complete
  • uv run python -m pytest -q tests/unit/test_cluster.py tests/unit/test_policies.py tests/unit/test_control_connection.py

dkropachev added 6 commits May 5, 2026 13:15
Track zero-token status during topology refreshes and rebuild routing state when nodes gain tokens.

Filter zero-token hosts from default load balancing policies while preserving explicit whitelist behavior.
Clear host addition state when pool creation aborts after a partial async start.

Keep zero-token filtering compatible with child policies that only implement the public load-balancing API.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant