Open liveforeverx opened 6 years ago
The “relevant nodes” here include nodes that only work as clients (i.e. nodes that don’t have replicated key-value pairs but do send queries/commands). I mean, to send queries/commands to correct nodes, updates in ETS records are necessary. Could you add your remote shell node as “hidden” one?
(Now I can’t investigate more as I’m on my holidays)
It should be fixed in distillery first for all node types: https://github.com/bitwalker/swarm/blob/master/config/config.exs#L7-L16 (how swarm handles it, because of this behaviour)
I'm not familiar with distillery but looking at https://github.com/bitwalker/distillery/blob/master/priv/libexec/commands/remote_console.sh it seems that remote_console nodes start as hidden ones. How do you start your remote shell?
@skirino Via remote_console
command...
Crash, if some short-lived nodes connects to a cluster.
Do we really need to send update to all non raft
relevant
nodes?