You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 20, 2024. It is now read-only.
host1 is alone; claims entire ring.
host1 gives 1 IP for weave expose;
host1 bumps ring entry 0 to version 1 due to free space update.
host2 connects to host1; receives current ring from host1.
host3 connects to host2; receives current ring from host2.
host3 receives donation from host1; updates entry 0 to version 2 and adds entry in middle.
host1 receives this updated ring from host3
host2 does not receive this update until the next periodic gossip.
host1 restarts, losing its memory of the ring.
host1 connects to host2, receives ring with entry 0 at version 1
host1 updates free space on entry 0 because no IPs are allocated. Now version 2.
host1 sees weave expose address reclaimed by weave script
host1 updates free space on entry 0 because 1 IP is allocated. Now version 3.
Now, when host2 receives updates from host3 and host1, the three peers end up with very different ideas of the ring:
Repro, to be run in the context of weaveworks/weave/test
The text was updated successfully, but these errors were encountered: