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 |
|---|---|---|
| benchmarks | ||
| dev-guide | ||
| dev-internal | ||
| learning | ||
| op-guide | ||
| platforms | ||
| rfc | ||
| upgrades | ||
| v2 | ||
| README.md | l--------- | 7 bytes |
| branch_management.md | -rw-r--r-- | 1.3 KB |
| demo.md | -rw-r--r-- | 13.1 KB |
| dl_build.md | -rw-r--r-- | 2.3 KB |
| docs.md | -rw-r--r-- | 3.4 KB |
| faq.md | -rw-r--r-- | 13.3 KB |
| libraries-and-tools.md | -rw-r--r-- | 8.3 KB |
| metrics.md | -rw-r--r-- | 8.5 KB |
| production-users.md | -rw-r--r-- | 3.1 KB |
| reporting_bugs.md | -rw-r--r-- | 2.3 KB |
| tuning.md | -rw-r--r-- | 5.3 KB |
Computing file changes ...
