Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Support Forum: Community-maintained FAQs [authorized posting allowed] Thread: BOINC: When Overdue Tasks Are Really Not Worth Completing! |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 1
|
Author |
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
It happens sometimes that a client/host is not being started for weeks and there still being jobs on it in "Ready to Start" or "Running" state. When then starting up again the tasks that were running will resume in a "Running - high priority" showing in the status column of the BOINC Manager (BM) "Tasks" view and a red text line will show in the Messages view (or as it's from 6.12 called "Notification" and "Event Log". This will read similar to this:
----------------------------------------WCG 10-9-2010 13:10:56 Task X0000033230662200405270818_1 is 34.08 days overdue; you may not get credit for it. Consider aborting it. When the client talks to the server and it's found that the result has already a complete quorum, the client will be told to abort the overdue "Ready to start" tasks without further user interaction required (from client 5.10.45 and up), which similar will show as "Server Aborted" on the Result Status pages. Example: ts05_ a090_ pqa005_ 0-- 1292373 Server Aborted 4-9-10 16:23:11 5-9-10 19:58:02 0.00 0.0 / 0.0 When finally the tasks are so old that the batch has already been moved off the Result Status page live task listings, the client will be notified of such and be it "Running - high priority" or in "Ready to start" state will be aborted with a message in the client log such as the below: WCG 10-9-2010 13:11:14 Message from server: Result X0000033220429200406031206_1 is no longer usable Best practice is that if you know to be away for longer or to be dual booting into a different operating system for weeks, to anticipate and set the "No new tasks" in the projects tab of the BM and then run the client buffer empty or if there's still work left when time is there to depart, to abort them all. This is a greatly appreciated practice as this will ensure that these tasks will be completed by another host on the grid within or close to the original deadline. Related topics: Deadlines for Standard & Rush Tasks and What Clients Get These Task Progress Information Return to the Start Here FAQ index
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All! |
||
|
|