-
Notifications
You must be signed in to change notification settings - Fork 1k
Bootnodes aren't retried after a node starts #7261
Copy link
Copy link
Closed
Labels
non mainnet (private networks)not related to mainnet features - covers privacy, permissioning, IBFT2, QBFTnot related to mainnet features - covers privacy, permissioning, IBFT2, QBFTpeering
Description
Description
If a permissioned node is configured with one or more bootnodes, it attempts to connect to them when it first starts but if the bootnodes are unavailable at that point, the node never attempts to retry the connection(s). This requires the node to be restarted before it will try connecting to the bootnodes again, and is in contrast to static-nodes which are treated as maintained-peers and retried every 60 seconds automatically.
Acceptance Criteria
Configure a PoA (e.g. QBFT) node A with a bootnode, node B. Before node B is started, start node A
Once node A has started, wait ~ 30 seconds for the initial peering to fail. Start node B, wait 60 seconds and the nodes should end up as peers.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
non mainnet (private networks)not related to mainnet features - covers privacy, permissioning, IBFT2, QBFTnot related to mainnet features - covers privacy, permissioning, IBFT2, QBFTpeering