Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.9.2, 1.13.2
-
None
-
None
Description
When a queue has files swapped out and a new file is added to it, it doesn't check whether or not that new file's priority is high enough for it to be in the non-swapped (active) set. This isn't normally a problem, however if the active files are waiting for the new file before they can be transferred, this might result in a stoppage (such as when you have a processor similar to MergeContent with the defragmentation strategy). This is also an problem if you expect a large queue of files to be prioritized properly but are not actively being consumed or added to in large enough volume.