-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
BlockAllocate rpc returns all peers when replication factor -1 but should return healthy ones only #543
Comments
Hi guys! Could you tell me please when are you planning to fix this bug and what I need to do to apply this updates? If I not mistaken current version of IPFS is v0.4.17 and ipfs-cluster-service is version 0.5.0. |
Hello. We will fix it for the next release. Hopefully this will come out in about two weeks. |
can't wait to test it Thank you! |
License: MIT Signed-off-by: Hector Sanjuan <code@hector.link>
License: MIT Signed-off-by: Hector Sanjuan <code@hector.link>
Fix #543: Use only healthy peers when adding everywhere (+tests)
Hello @mike-ngu , the a release candidate with this fix is available here: https://dist.ipfs.io/ipfs-cluster-service/ |
Hello @hsanjuan, Thank you for notification. Just to clarify, to get last bug fixing I need to install |
yes, correct |
Pre-check
secret
Basic information
Description
The bug is here: https://github.com/ipfs/ipfs-cluster/blob/master/rpc_api.go#L205
When the adder allocates and replication factor is
-1
, we return all cluster peers. This ends up having the adder try to put blocks to peers which are down. We should useLatestMetrics
instead from the monitor, with the "ping" metric type. And return the peerset extracted from those metrics (which are valid cluster peers).The text was updated successfully, but these errors were encountered: