Clastic cluster unstable

I have ELB stack running in kubernetes. But noticed issue with two out of 3 nodes with following error

{"type": "server", "timestamp": "2021-11-29T17:42:37,326Z", "level": "WARN", "component": "o.e.c.c.ClusterFormationFailureHelper", "": "prod-eks-logs", "": "es-master-2.elasticsearch", "message": "master not discovered or elected yet, an election requires at least 2 nodes with ids from [nnYFjBsuSN25apManWU-aA, nRV2B7R3QxWYiaXoxCMiAw, Bs1vhzBRQbyJVuv3jtWJbQ], have discovered [{es-master-2.elasticsearch}{nRV2B7R3QxWYiaXoxCMiAw}{HkGh-ZY3SmmyF-dwJaSw2g}{}{}{cdfhilmrstw}, {es-master-0.elasticsearch}{Bs1vhzBRQbyJVuv3jtWJbQ}{RdXrp-17RrK1rQjk463wXw}{}{}{cdfhilmrstw}, {es-master-1.elasticsearch}{nnYFjBsuSN25apManWU-aA}{9P45vPl3QBeqvIYkxxEIkw}{}{}{cdfhilmrstw}] which is a quorum; discovery will continue using [,] from hosts providers and [{es-master-2.elasticsearch}{nRV2B7R3QxWYiaXoxCMiAw}{HkGh-ZY3SmmyF-dwJaSw2g}{}{}{cdfhilmrstw}] from last-known cluster state; node term 24, last-accepted version 500416 in term 24" }

Would like to know what is causing this and how can i prevent this in future.

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