extend DHT protocol with load information sampling request #71
schmittlauch
commented
Owner
No description provided.
schmittlauch
added this to the k-choices load balancing milestone
schmittlauch
added the advanced features
DHT
labels
schmittlauch
added a new dependency
#70 evaluate & plot logged measurements
schmittlauch
removed a dependency
#70 evaluate & plot logged measurements
schmittlauch
added a new dependency
#72 interface between DHT and Service to request load information
schmittlauch
referenced this issue from a commit
extend ASN.1 schema for requesting load information
contributes to #71
schmittlauch
referenced this issue from a commit
parse ASN.1 representation of load querying
includes tests
contributes to #71
schmittlauch
referenced this issue from a commit
some considerations about load reporting message format
contributes to schmittlauch/Hash2Pub#71
schmittlauch
referenced this issue from a commit
parse ASN.1 representation of load querying
includes tests
contributes to #71
schmittlauch
referenced this issue from a commit
send load query request, parse result and represent it
- sending side of #71
- introduces SegmentLoadStats to hold the response data
- contributes to #2
schmittlauch
referenced this issue from a commit
only specify upper key bound when querying load
As a querying node does not always know the lower bound of the queried
segment – determined by the predecessor – let the currently responsible
node provide that bound instead.
affects #71
schmittlauch
referenced this issue from a commit
respond to QueryLoad requests
closes #71
closes #72
contributes to #2
schmittlauch
referenced this issue from a commit
implement k-choices join functions
large commit, contains a number of things:
- k-choices #2 cost calculation
- k-choices parameters
- adjusting ASN.1 network messages to contain all values required for
cost calculation #71
- adjusting stats to contain required values
- k-choices node and vserver join functions
- placeholder/ dummy invocation of k-choices join
schmittlauch
closed this issue
Labels
No labels
ActivityPub
advanced features
basic functionality
bug
DHT
evaluation
refactoring
security
test case
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
#72 interface between DHT and Service to request load information
schmittlauch/Hash2Pub
Reference: schmittlauch/Hash2Pub#71
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?