queue item moves position when high priority item arrives
Posted: October 19th, 2017, 1:52 am
Hello,
Please excuse the terrible description.
SAB 2.3.x (it's a mix of 2.3.0 and 2.3.1 - and hopefully that's not the reason I'm having trouble. )
Glitter - Night interface.
Problem: I have a normal (default) priority item that is at the top of the queue, and (because it was missing blocks), SAB has dutifully started downloading the internal PARs so it can be fixed.
Then, a high-priority item arrives, and proceeds to jump to the top of the queue.
The problem is the previous normal-priority item then gets pushed to the far end of the normal queue. I have to go find it and bring it to the top of the queue again so it sits below the new high-priority item.
This has happened a few times and I'm still trying to narrow down exactly when it occurs. I usually discover it when checking the queue for that item I was waiting to finish, then finding that it's not there as it's now at the end of the 'normal' queue.
From memory, when a queue item is downloading PARs, I saw them assigned a 'force' priority level, so a 'high' level item shouldn't displace it. And it shouldn't get sent to the end of the line.
I've also check the SAB logs as I've noticed it records when I move something manually around ("Switching job [ ]", etc...) - but there's nothing at the point where it began downloading the high priority item to indicate that the original item was moved in the queue.
Thoughts?
Please excuse the terrible description.
SAB 2.3.x (it's a mix of 2.3.0 and 2.3.1 - and hopefully that's not the reason I'm having trouble. )
Glitter - Night interface.
Problem: I have a normal (default) priority item that is at the top of the queue, and (because it was missing blocks), SAB has dutifully started downloading the internal PARs so it can be fixed.
Then, a high-priority item arrives, and proceeds to jump to the top of the queue.
The problem is the previous normal-priority item then gets pushed to the far end of the normal queue. I have to go find it and bring it to the top of the queue again so it sits below the new high-priority item.
This has happened a few times and I'm still trying to narrow down exactly when it occurs. I usually discover it when checking the queue for that item I was waiting to finish, then finding that it's not there as it's now at the end of the 'normal' queue.
From memory, when a queue item is downloading PARs, I saw them assigned a 'force' priority level, so a 'high' level item shouldn't displace it. And it shouldn't get sent to the end of the line.
I've also check the SAB logs as I've noticed it records when I move something manually around ("Switching job [ ]", etc...) - but there's nothing at the point where it began downloading the high priority item to indicate that the original item was moved in the queue.
Thoughts?