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 |
|---|---|---|
| authpb | ||
| doc.go | -rw-r--r-- | 687 bytes |
| range_perm_cache.go | -rw-r--r-- | 5.6 KB |
| range_perm_cache_test.go | -rw-r--r-- | 5.9 KB |
| simple_token.go | -rw-r--r-- | 3.5 KB |
| store.go | -rw-r--r-- | 24.3 KB |
| store_test.go | -rw-r--r-- | 8.0 KB |
Computing file changes ...
