Revision 9d9be2bc86f3694b0f42aff4eeef3451100e6c2b authored by Anthony Romano on 14 March 2017, 20:31:09 UTC, committed by Gyu-Ho Lee on 18 March 2017, 14:56:18 UTC
In cases of multiple endpoints, it's possible member add would get a its member list from a member that has not yet recognized the membership update. Instead, confirm that the member list response is from the member that acked the member add or from a member that has synced with the cluster following the member add. Fixes #7498
1 parent e5462f7
File | Mode | Size |
---|---|---|
adt | ||
contention | ||
cors | ||
cpuutil | ||
crc | ||
expect | ||
fileutil | ||
flags | ||
httputil | ||
idutil | ||
ioutil | ||
logutil | ||
mock | ||
monotime | ||
netutil | ||
osutil | ||
pathutil | ||
pbutil | ||
report | ||
runtime | ||
schedule | ||
stringutil | ||
testutil | ||
tlsutil | ||
transport | ||
types | ||
wait | ||
README.md | -rw-r--r-- | 194 bytes |
Computing file changes ...