You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consul agent running in server mode in a 3 node cluster panics and then crashed. This only happens on the node that is the leader. When this happens cluster leadership is transfered to another node. After some time (could be in a couple of hours or even days) this leader also crashes, leadership transfers to another node and the cycle continues.
Reproduction Steps
It is not known how to reproduce this or what exactly triggers this. It happens randomly in an otherwise normally functioning cluster.
Overview of the Issue
Consul agent running in server mode in a 3 node cluster panics and then crashed. This only happens on the node that is the leader. When this happens cluster leadership is transfered to another node. After some time (could be in a couple of hours or even days) this leader also crashes, leadership transfers to another node and the cycle continues.
Reproduction Steps
It is not known how to reproduce this or what exactly triggers this. It happens randomly in an otherwise normally functioning cluster.
Consul info for both Client and Server
Client info
Server info
Operating system and Environment details
The environment has Consul servers running on EC2 instances and ECS tasks running on ECS Fargate. There are about 140 consul clients running
Log Fragments
Crash log is attached: crash.log.txt
The text was updated successfully, but these errors were encountered: