You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
unix sockets: design direct-query API for multiple endpoints #1081
This sends every application query through whichever single control connection is active. Although Cluster accepts multiple socket contact points, callers cannot query or select them independently; explicit host targeting disables fallback.
Expected behavior
Define a first-class API for direct Unix-socket queries. It should support both a single maintenance node and one socket per node, without making tokenless nodes normal topology-routing targets or funneling all queries through one shared control connection.
The API shape—pinned sessions, independently poolable sockets, or another model—needs design.
Activity
test/cluster: use control connection when pools are unavailable
test/cluster: use control connection when pools are unavailable
test/cluster: use control connection when pools are unavailable