Skip to content

unix sockets: design direct-query API for multiple endpoints #1081

Description

@dkropachev

Problem

Querying a tokenless node through UnixSocketEndPoint currently requires ControlConnectionQueryFallback.SkipPoolCreation:

Cluster(
    contact_points=socket_endpoints,
    allow_control_connection_query_fallback=ControlConnectionQueryFallback.SkipPoolCreation,
)

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.

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions