Potential lock contention: Coordinator is not able to publish routing table to new node which causes it fails to be bootstrapped about olric HOT 2 OPEN

Possibly, there is an issue with your setup: the peer discovery code doesn't work properly. It may propagate non-existing nodes or fail to remove failed nodes from the member list.

I think there is no problem with the lock usage. These parts of the code are carefully written, reviewed, and tested over time.

Regarding the error messages, Olric is a highly concurrent system. It has many goroutines that process some data concurrently. Some of these components are not synced. Because it is not necessary. A goroutine may try to do something; if it fails, it logs the problem and continues working as usual. The error logging may be noisy sometimes. I accept that.

As I said before, the problem might be in the peer discovery code. Is it possible to share it?

from olric.