efe1143ce2
[#1439] object: Sort nodes by priority metrics to compute GET request
ca816de8e9
[#1439] node: Reduce usage of
netmapAPI.NodeInfo
bc8d79ddf9
[#1447] services/tree: Move relaying code to a separate function
object: Sort nodes by priority metrics to compute GET requests
Next
return slice of structs, which contains only addresses and key. There are no way to check attributes.
744c3947a7
[#1439] object: Sort nodes by priority metrics to compute GET request
a238ed879c
[#1439] node: Reduce usage of
netmapAPI.NodeInfo
29708b78d7
[#1442] cli/tree: Enchance error message if
rpc-endpoint
isn't defined
b9284604d9
[#1442] cli/tree: Allow to specify
rpc-endpoint
with config file
65a4320c75
[#1441] services/tree: Use
grpc.WaitForReady
option when creating client
object: Sort nodes by priority metrics to compute GET requests
You are right, changes were reverted yesterday, please review.
object: Sort nodes by priority metrics to compute GET requests
When we create traverser
there is no flag which indicates that we need to set local node info or not, because we set priority metrics via a list of options. I thought we don't need to set it…
object: Sort nodes by priority metrics to compute GET requests
That was done for EC container. Reduce amount of changes.
object: Sort nodes by priority metrics to compute GET requests
For each call of LocalNodeInfo()
we are…
object: Sort nodes by priority metrics to compute GET requests
Is it ok that a storage node contains an empty attribute?