Support an informer for the pinning queue size #1649
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
Milestone
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.
The text was updated successfully, but these errors were encountered: