Opened 16 years ago
Last modified 14 years ago
#862 new Defect
Client doesn't ask for new work while having suspended tasks in a queue
| Reported by: | Tamagoch | Owned by: | davea |
|---|---|---|---|
| Priority: | Undetermined | Milestone: | Undetermined |
| Component: | Client - Work Fetch Policy | Version: | 6.4.7 |
| Keywords: | Cc: |
Description
When putting some tasks or projects in a pause client seems to count them as working ones since no other jobs are requested. When trying to update active project manually scheduler requests 0 seconds of work which may leave system idle.
Sometimes increasing cache may help but I cannot see what else could make it request more tasks when there's nothing to process.
Found both in 32 and 64 bit Windows versions.
Change History (2)
comment:1 Changed 16 years ago by
comment:2 Changed 14 years ago by
Hello, I can confirm this is happening with client version 6.10.58 on Debian.
While I can understand that if one project has jobs suspended than other jobs are not requested for *that* project only (even if I think it would be better to fetch additional WUs), I can see that WUs for *other* projects are not fetched as well.
It's like even if there are jobs suspended, they are counted as "valid" WUs, while there is actually nothing running on the machine (if all are suspended) and none are fetched: the machine is idle (indefinitely?).
I think it would be better to have the set of "running + waiting to run" to always match the additional work buffer or a minimum set of hours, and if there's nothing eligible for execution, fetch new WUs no matter what.
Regards, Sandro
If a project has any suspended task, there will be no work fetched from that project. This behavior is intentional.