alertmanager/cluster
stuart nelson 6305229fcc
fix set initial failed peers (#1407)
* Correctly add Node to initially failed peer

Reconnect attempts to failed peers were panicking
because peer.Address() would attempt to access the
nil Node struct member.

Signed-off-by: stuart nelson <stuartnelson3@gmail.com>

* Correctly remove old peers

Again, since we aren't assigning a name (this is
generated) we rely on the node's Address for
removing the initially joining (and potentially
later re-joining) peers

Signed-off-by: stuart nelson <stuartnelson3@gmail.com>

* Test the peerJoin removes initial peers

Signed-off-by: stuart nelson <stuartnelson3@gmail.com>

* Don't add self to failing peers list

The initially failing peers list shouldn't include
the bindAddr for the alertmanager itself, as this
connection is never made, and consequently only
removed from the failedPeers list after the failed
peer timeout.

Signed-off-by: stuart nelson <stuartnelson3@gmail.com>

* Filter initialFailed with advertise addr

This may differ from bindAddr, and is the value we
want to not attempt to connect to.

Signed-off-by: stuart nelson <stuartnelson3@gmail.com>
2018-06-08 12:34:52 +02:00
..
clusterpb *: move to memberlist for clustering 2018-02-08 12:18:44 +01:00
advertise.go cluster: advertise explicitly for empty addresses (#1386) 2018-06-07 17:57:01 +02:00
cluster_test.go fix set initial failed peers (#1407) 2018-06-08 12:34:52 +02:00
cluster.go fix set initial failed peers (#1407) 2018-06-08 12:34:52 +02:00
delegate.go memberlist gossip (#1389) 2018-06-08 11:48:42 +02:00