Make rlink auto reconnect "managed only"

om26er commented 3 years ago

Currently the autobahn-python's default WAMP reconnect logic is used if an rlink goes down. It would be useful if the reconnect interval was configurable.

om26er commented 3 years ago

That was a wrong assessment. It seems Crossbar tries to reconnect after every two seconds (with some variation). So it doesn't go into increasing intervals as autobahn python does.

om26er commented 3 years ago

Ok, I think it might be a good idea to disable auto-reconnect all together. If the rlink goes down for a few thousand realms, the re-connect attempts would look crazy on logs as well as CPU side.

oberstet commented 3 years ago

Ok, I think it might be a good idea to disable auto-reconnect all together. If the rlink goes down for a few thousand realms, the re-connect attempts would look crazy on logs as well as CPU side.

yes, I agree .. it seems (lets discuss) better to:

disable single rlink level auto-reconnect altogether (CB outgoing connections can be configured .. I think .. but we don't want it anyways, because ..)
subscribe to the respective meta event (rlink disappeared) in the orchestration code for router-clusters inside CB center node
react in the respective event handler according to a policy that manages the whole network of rlinks in the router-cluster

the holistic management of a logical unit "router cluster" spanning many nodes and rlinks was always the actual goal in CB center/edge etc .. the code for the initial setup of eg a full mesh of rlinks between a set of nodes to form a router cluster is already there! however, we miss those dynamically reacting code bits .. eg a rlink disappearing in a non-full mesh might be compensated by restarting that rlink, or a different rlink, or ...

crossbario / crossbar

Make rlink auto reconnect "managed only" #1892