Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stewardship's traverse function seem to be retrieving the same chunk over and over again #4977

Closed
istae opened this issue Feb 4, 2025 · 0 comments
Assignees
Labels
needs-triaging new issues that need triaging

Comments

@istae
Copy link
Member

istae commented Feb 4, 2025

stewardship's traverse functions seem to be retrieving the came chunk over and over again.

"retrieved chunk" "chunk_address"="eed87f5ccab8f5c54d44466c6ec0fa189f0bd630f175b386aadd26ff51fc02f2" "peer_address"="f40aff05aa2bb8f9f7d2c5c4d0ba34476da29a0a1589a21f7848a11d0cbcb7fe"

this repeats for 128 times, then the node tries other references, then repeats 128 attempts for a different reference.

this is also causing the request to take an obscene amount of time to finish.

@istae istae added the needs-triaging new issues that need triaging label Feb 4, 2025
@istae istae changed the title stewardship's traverse functions seem to be retrieving the came chunk over and over again stewardship's traverse function seem to be retrieving the came chunk over and over again Feb 4, 2025
@istae istae changed the title stewardship's traverse function seem to be retrieving the came chunk over and over again stewardship's traverse function seem to be retrieving the same chunk over and over again Feb 4, 2025
@istae istae closed this as completed Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triaging new issues that need triaging
Projects
None yet
Development

No branches or pull requests

2 participants