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
This commit is contained in:
parent
30bf0529ed
commit
5e745cd035
5 changed files with 25 additions and 26 deletions
|
@ -104,13 +104,13 @@ PingRequestPayload ::= NULL -- do not include a node/ vserver ID, so that
|
|||
PingResponsePayload ::= SEQUENCE OF NodeState
|
||||
|
||||
LoadRequestPayload ::= SEQUENCE {
|
||||
lowerBound NodeID,
|
||||
upperBound NodeID
|
||||
upperSegmentBound NodeID
|
||||
}
|
||||
|
||||
LoadResponsePayload ::= SEQUENCE {
|
||||
loadSum REAL,
|
||||
remainingLoadTarget REAL
|
||||
remainingLoadTarget REAL,
|
||||
lowerBound NodeID
|
||||
}
|
||||
|
||||
END
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue