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

Support an informer for the pinning queue size #1649

Closed
hsanjuan opened this issue Apr 27, 2022 · 0 comments · Fixed by #1657
Closed

Support an informer for the pinning queue size #1649

hsanjuan opened this issue Apr 27, 2022 · 0 comments · Fixed by #1657
Assignees
Labels
effort/hours Estimated to take one or several hours exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up

Comments

@hsanjuan
Copy link
Collaborator

Apart from user-tags and disk free-space metric, it would be good to support allocations based on pinning queue sizes.

For example, a peer with a queue of 0-1000 items would have preference for allocations over a peer with a queue of 1000-2000 items. Peers with similarly-sized queues would be considered equal and then allocation would be decided based on free-space.

These buckets should be configurable.

The informer would need to ask the pintracker for the information (the operationtracker) tracks these.

@hsanjuan hsanjuan added P1 High: Likely tackled by core team if no one steps up exp/expert Having worked on the specific codebase is important effort/hours Estimated to take one or several hours labels Apr 27, 2022
@hsanjuan hsanjuan self-assigned this Apr 27, 2022
@hsanjuan hsanjuan linked a pull request May 5, 2022 that will close this issue
@hsanjuan hsanjuan added this to the Release v1.0.1 milestone May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant