This repository has been archived by the owner on Apr 15, 2018. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Re:
#159
This will filter the selfnode from the list of nodes received and warn if it's encountered.
I'm not sure if this is the prettiest approach but I tested and it does work. This is a fairly easy scenario to produce. Using a fixed ip address, If we shutdown the old nodes and then try to start up again nodes can see the selfnode while other nodes are acquiring the lock and trying to start up
The filtering is done in the retrieve section which is significant - the node will be filtered before determining if there are nodes or not. The implication is that if only the self node exists, it will attempt to lock if the only node is selfNode as it would be filtered.