periodic stabilise #44
schmittlauch
commented 2020-06-05 21:16:09 +02:00
Owner
- periodically contact immediate successors and predecessors to get their predecessor and successor lists
- check nodes (PING) before inserting into neighbour list
- if less than k neighbours, try looking up additional ones
- [x] periodically contact immediate successors and predecessors to get their predecessor and successor lists
- [x] check nodes (PING) before inserting into neighbour list
- [x] if less than k neighbours, try looking up additional ones
schmittlauch
added this to the working EpiChord overlay (without k-choices) milestone 2020-06-05 21:16:09 +02:00
schmittlauch
added the 2020-06-05 21:16:09 +02:00
basic functionality
DHT
labels
schmittlauch
added a new dependency 2020-06-07 00:25:30 +02:00
#46 Refactor predecessors and successors to hold RemoteNodeStates, not just NodeIDs
schmittlauch
started working 2020-06-09 19:41:50 +02:00
schmittlauch
referenced this issue from a commit 2020-06-09 22:12:03 +02:00
implement stabilise request sending and parsing
contributes to #44
schmittlauch
stopped working 2020-06-09 22:18:07 +02:00
2h 36min 17s
schmittlauch
started working 2020-06-10 14:27:25 +02:00
schmittlauch
stopped working 2020-06-10 19:20:13 +02:00
4h 52min 47s
schmittlauch
referenced this issue from a commit 2020-06-20 22:28:35 +02:00
stabilise periodically
contributes to #44
schmittlauch
referenced this issue from a commit 2020-06-20 22:28:36 +02:00
ping potential neighbours before adding to list
for #44
schmittlauch
referenced this issue from a commit 2020-06-23 19:34:25 +02:00
refactored stabilise: use first responding neighbour
contributes to #44
schmittlauch
referenced this issue from a commit 2020-06-24 01:20:09 +02:00
look up additional neighbours if necessary
for #44
schmittlauch
referenced this issue from a commit 2020-06-24 02:51:50 +02:00
update responding neighbours and delete unresponding ones from cache
contributes to #44
schmittlauch
referenced this issue from a commit 2020-06-24 02:51:51 +02:00
launch stabilise thread
closes #44
although stabilise functionality is still untested
schmittlauch
closed this issue 2020-06-24 02:52:53 +02:00
Labels
No labels
ActivityPub
advanced features
basic functionality
bug
DHT
evaluation
refactoring
security
test case
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 7 hours 29 minutes
Due date
schmittlauch
7 hours 29 minutes
No due date set.
Depends on
#46 Refactor predecessors and successors to hold RemoteNodeStates, not just NodeIDs
schmittlauch/Hash2Pub
Reference: schmittlauch/Hash2Pub#44
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?