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

flood of recovery requests #2209

Open
santicomp2014 opened this issue Jun 23, 2020 · 0 comments
Open

flood of recovery requests #2209

santicomp2014 opened this issue Jun 23, 2020 · 0 comments
Assignees
Labels
global pinning experimental implementation of global pinning priority

Comments

@santicomp2014
Copy link
Contributor

santicomp2014 commented Jun 23, 2020

This issue was originally raised in #2205.

After #2202 was merged, flooding of recovery attempts is still occurring under a different set of conditions.

The current implementation sets the publisher in the context when downloading content; so that content recovery process is triggered only when the publisher was explicitly set in the download query/request. But it seems this is not enough to fix all of the flooding.

When a made-up hash is requested and the publisher is set, the flooding also occurs.

Something similar occurs when setting a made-up publisher.

Verify that the test scenarios behave as specified, without flooding in any case:

Chunk Publisher Expected Result
Valid Chunk Valid Publisher Recovery Successful
Invalid Chunk Valid Publisher Recovery Unsuccessful
Valid Chunk Invalid Publisher Recovery Unsuccessful
Invalid Chunk Invalid Publisher Recovery Unsuccessful

(valid/invalid means existing/non-existing)

@santicomp2014 santicomp2014 added the global pinning experimental implementation of global pinning label Jun 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
global pinning experimental implementation of global pinning priority
Projects
None yet
Development

No branches or pull requests

2 participants