Actions
Bug #723
openTimers on lock
Start date:
06/07/2010
Due date:
% Done:
0%
Estimated time:
2.00 h
Description
Timers on Lock are definitely needed
Updated by Betoule Marc over 14 years ago
- Category set to Engine
- Status changed from New to Assigned
- Assigned To set to Betoule Marc
- Estimated time set to 2.00 h
Updated by Betoule Marc over 14 years ago
- Priority changed from High to Immediate
Updated by Betoule Marc about 14 years ago
- Priority changed from Immediate to Normal
My view is that this is more than a bug. We need to rethink the scheduler worker communication to handle such situations as :
- The scheduler got killed or lost connection > the workers should wait some configurable time for him to come back before dying silently One worker got killed or lost connection -> the scheduler should be able to detect this after a while and resubmit its job
I decrease the priority for next release.
Updated by Le Jeune Maude about 14 years ago
- Priority changed from Normal to Urgent
Actions