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

calibrate ideal wait time for chunk re-retrieval #2172

Closed
santicomp2014 opened this issue May 4, 2020 · 2 comments
Closed

calibrate ideal wait time for chunk re-retrieval #2172

santicomp2014 opened this issue May 4, 2020 · 2 comments
Assignees
@santicomp2014
Labels
global pinning experimental implementation of global pinning

Comments

@santicomp2014
Copy link
Contributor

When a chunk is not retreived in netstore it invokes the recoveryCallback and wait for 500 ms
and tries to RemoteFetch the reupload chunk.

This is related to #2171 for monitoring the chunk reuploaded.

The timeout should be calibrated accordingly, to guarantee the chunk was reuploaded without spending too much deadtime.
@santicomp2014 santicomp2014 added the global pinning experimental implementation of global pinning label May 4, 2020
@santicomp2014 santicomp2014 mentioned this issue May 4, 2020
Merged
@mortelli
Copy link
Contributor

we might also want to look into the timeout for the recovery feed query while we're at it

@mortelli mortelli mentioned this issue Jun 12, 2020
Merged
@mortelli
Copy link
Contributor

Closing, since we are returning error code 402 rather than retrying the fetch within the scope of the original get.

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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@santicomp2014 @mortelli