addnode strategy

Wed, 25 Nov 2020 21:44:16 +0000

Dear MC team,

I have a network with about ten miners (in round-robin style) and some full back nodes.
I have to face the following matters:
- periodically some miner are switched off for maintenance
- the miners must be addressed by host name because their address could change

I cannot use a connect command because I'm not sure which of the miner is up and running at one moment.
Besides even if the connect command is succesful, if the server is switched off then the connected node will be unplugged from the network.

My idea is to add a crontab command (executed every day or on a periodical basis) as the following:
multichain-cli <chain_name> addnode $(dig +short miner_1_hostname):<port> add
multichain-cli <chain_name> addnode $(dig +short miner_2_hostname):<port> add
... and so on

I used 'dig +short hostname' because in MC 2.0.1 using addnode hostname instead of ip address seems to cause a crash.

Could you please comment my solution?
Thanks
Fabio

Node Discovery

Thu, 21 Jun 2018 21:34:53 +0000

Guys

Do you have any more information on how nodes discover peers either via other connected peers or using addnode?

For context we are running multiChain nodes within Kubernetes and we need to ensure nodes don't get orphaned from each other on a restart which can cause the nodes to be assigned new IP addresses. Because of the way Kubernetes works, we can fix the DNS names of the nodes and we experimented with added these across each node using the addnode api call, but these don't seem to persist across restarts.

At the minute we might need to execute addnode at startup of each node, but wanted to check if this was expected behaviour of addnode and any more information on how peer discovery works and any guidelines you might have to ensure the network remains connected across node restarts and changes of node IP addresses?

Cheers

Marty

MultiChain Developer Q&A - Recent questions tagged addnode

addnode strategy

Node Discovery