Cluster manager not discovered exception

Unfortunately, no, but it is vastly improved. The no leader issue only occurs maybe once every 24 hours, now. I am beginning to wonder if its a hardware/hypervisor issue so I priced what it would cost to host in Azure to meet my employer’s needs and … well lets just say I was quickly disabused of that option.

Hey ,

During this time…

Do you have anything running that could interfere with it? I assume your monitoring metrics in this environment?

Not that I am aware of. Each container is purpose-specific (i.e. 3 x Opensearch, 1 x Graylog/mongodb)

We are monitoring via LibreNMS (which, if you aren’t familiar, is a pretty damn awesome snmp FOSS program). Which metrics should I monitor?

Oh, Thanks for the tip :+1:

I personally would look for network issue ( sending and receiving) . Also, I seen when a node because unavailable because IP Address confliction.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.