Don't list blocked nodes unknown to self
rogeralsing opened this issue · 1 comments
rogeralsing commented
When a new node joins a cluster. blocklist is gossiped to it.
Here is the new node logging all the gossiped blocked nodes:
info: Proto.Remote.BlockList[0]
Blocking member 7b0ef7bb9f144ff5a53bd2f8864010e0 due to Blocked by remote member
info: Proto.Remote.BlockList[0]
Blocking member 89a1d19d16fd407c86706dcea3eff3bb due to Blocked by remote member
info: Proto.Remote.BlockList[0]
Blocking member 60184e4a440944c99a09b834c0de8eea due to Blocked by remote member
info: Proto.Remote.BlockList[0]
Blocking member f0744000476c4606864c6459cb7ba2bb due to Blocked by remote member
info: Proto.Remote.BlockList[0]
Blocking member 161050d22b434da28068f7bcc5fa60e6 due to Blocked by remote member
This is technically correct. but useless for the reader of the logs.
we should not log entries where the member id is not present in the memberlist.
rogeralsing commented
done