mirror of https://github.com/hashicorp/consul
Browse Source
This can happen when one other node in the cluster such as a client is unable to communicate with the leader server and sees it as failed. When that happens its failing status eventually gets propagated to the other servers in the cluster and eventually this can result in RPCs returning “No cluster leader” error. That error is misleading and unhelpful for determing the root cause of the issue as its not raft stability but rather and client -> server networking issue. Therefore this commit will add a new error that will be returned in that case to differentiate between the two cases.pull/9491/head
Matt Keeler
4 years ago
committed by
GitHub
4 changed files with 76 additions and 12 deletions
Loading…
Reference in new issue