pyCluster supports direct node links and keeps compatibility-focused behavior for legacy cluster families.
How pyCluster opens the connection.
Examples:
tcp://host:portpycluster://host:port?login=LOCALNODE-1&client=PEERNODE-1dxspider://host:port?login=LOCALNODE-1&client=PEERNODE-1kiss:///dev/ttyUSB0?baud=9600ax25://DESTCALL?source=MYCALL&via=DIGI1,DIGI2
How pyCluster behaves after the connection is established.
Supported labels:
dxspiderarclusterdxnetclxpycluster
Configured outbound peers.
These have:
- a transport address
- a family
- retry behavior
- optional peer password
Inbound peers that connect to the local node.
These do not require:
- a DSN/transport address on the local side
- local retry logic
pycluster://example.net:7300?login=LOCALNODE-1&client=PEERNODE-1
If the remote peer requires a password:
pycluster://example.net:7300?login=LOCALNODE-1&client=PEERNODE-1&password=secret
dxspider://example.net:7300?login=LOCALNODE-1&client=PEERNODE-1
If the remote peer requires a password:
dxspider://example.net:7300?login=LOCALNODE-1&client=PEERNODE-1&password=secret
Useful visibility commands:
show/linksshow/nodeshow/connect
Useful sysop commands:
sysop/connectsysop/disconnect
In the System Operator web console, the Peers and Links editor now exposes Cluster Family as an explicit selector, including pyCluster for pyCluster-to-pyCluster links.
- pyCluster avoids silently guessing peer family/version
- explicit identity learned from protocol traffic is preferred over inference
- loop suppression is surfaced in operator views and policy-drop summaries