Skip to content
This repository has been archived by the owner on Aug 2, 2021. It is now read-only.

fix content recovery request flooding #2205

Closed
mortelli opened this issue Jun 12, 2020 · 1 comment
Closed

fix content recovery request flooding #2205

mortelli opened this issue Jun 12, 2020 · 1 comment
Assignees
@santicomp2014
Labels
global pinning experimental implementation of global pinning priority

Comments

@mortelli
Copy link
Contributor

Every chunk which fails to be retrieved is resulting in a content repair routine being triggered.

This is causing an infinite loop of callbacks after executing just one down command for a missing chunk, without even having the recovery feed set or any other chunk uploaded to the network.

Content repair should be triggered only when explicitely asked to by the end-user through a down or curl command.

This should be fixed alongside issue #2193.
@mortelli mortelli added priority global pinning experimental implementation of global pinning labels Jun 12, 2020
@mortelli mortelli changed the title fix content recovery requests flooding fix content recovery request flooding Jun 12, 2020
@santicomp2014 santicomp2014 mentioned this issue Jun 12, 2020
Merged
@mortelli
Copy link
Contributor Author

completed through #2202

@santicomp2014 santicomp2014 mentioned this issue Jun 23, 2020
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@santicomp2014 santicomp2014

Labels
global pinning experimental implementation of global pinning priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@santicomp2014 @mortelli