diff options
| author | Michael Klishin <michael@clojurewerkz.org> | 2019-09-29 16:06:39 +0300 |
|---|---|---|
| committer | Michael Klishin <michael@clojurewerkz.org> | 2019-09-29 16:06:41 +0300 |
| commit | 7e2021c588784c2c190f3318b94344cb048d3e68 (patch) | |
| tree | 6807218c886d7fbeb4bc092e99324ef7ac3cc9c3 /Makefile | |
| parent | 3355754beed3559ff09c27eb1e8ee915d568f4e0 (diff) | |
| download | rabbitmq-server-git-7e2021c588784c2c190f3318b94344cb048d3e68.tar.gz | |
Clearer log message when peer discovery yields an empty list
With some backends, namely Kubernetes, a set of nodes can be
discovered but then filtered out as ineligible. For example,
a node whose pod is not yet ready would not be considered for
clustering.
Hopefully it would reduce the frequency of questions such as [1][2].
1. https://groups.google.com/forum/#!msg/rabbitmq-users/tm3Ip0mXXjs/WCOm3z_fAAAJ
2. https://github.com/rabbitmq/rabbitmq-peer-discovery-k8s/issues/52
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions