periodic stabilise #44
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
basic functionality
DHT
labels
#46 Refactor predecessors and successors to hold RemoteNodeStates, not just NodeIDs
implement stabilise request sending and parsing
contributes to #44
2h 36min 17s
4h 52min 47s
stabilise periodically
contributes to #44
ping potential neighbours before adding to list
for #44
refactored stabilise: use first responding neighbour
contributes to #44
look up additional neighbours if necessary
for #44
update responding neighbours and delete unresponding ones from cache
contributes to #44
launch stabilise thread
closes #44
although stabilise functionality is still untested
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?