Enhancement #597
fixing adj2nest work around
| Status: | Resolved | Start date: | 01/27/2012 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Alex Norton |
% Done: | 0% |
|
| Category: | Scheduler | |||
| Target version: | - | |||
| Rank: | 99 | Tester: |
Description
Some agents don't update the number of item processed quickly and for large uploads will go a very long time without changing this number. This results in the scheduler choosing to kill the agent because it believes that the agent has entered an infinite loop. There should be a way for an agent to turn off this feature when the scheduler deals with it or for the agent to correctly be able to update the number of items processed.
Adj2nest is currently the only agent that is having this problem and is currently using a dummy fo_scheduler_heart(1) to keep the scheduler from killing it when it is processing large distributions. This work around it not ideal and should be replace with a more long term solution.
History
Updated by Alex Norton over 1 year ago
Agents should now be able to call fo_scheduler_heart(0) to inform the scheduler that they are still alive. This means that agents don't need to lie about processing items to convince the scheduler that they are still running. adj2nest should no longer need the work around described.
Updated by Alex Norton over 1 year ago
- Status changed from New to Resolved
Updated by Mary Laser 9 months ago
- Target version deleted (
2.0.1)
Updated by Bob Gobeille 7 months ago
- Rank set to 99
Change unranked issues to rank 99 so they show up in a ranking report at the bottom. Otherwise, they show up on top.