| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Suggestions / Feedback
Thread: Interessting Deadline set in the case of error |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello
I have an interesting point. In case of an error the WU is redistributed with a shorter Timeframe. In the case below the timeframe is shorter than the second still running corum. I would assume that the end dates of the still running and resent WU should be the same. X0000042390683200411191101_ 2-- In Progress 02/22/2008 13:03:06 02/24/2008 08:15:06 0.00 0.0 / 0.0 X0000042390683200411191101_ 0-- Error 02/21/2008 09:02:20 02/22/2008 12:55:23 4.85 42.0 / 0.0 X0000042390683200411191101_ 1-- In Progress 02/21/2008 08:51:40 03/01/2008 08:51:40 0.00 0.0 / 0.0 Thanks in advance. Siegfried Oesterreicher |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Reported in back room in different ways and knreed advised he's contemplating over this issue and how to resolve without increasing the DB load.
----------------------------------------Added: It is agreed that the deadline of the backup work should at least match the original quorum deadline and not default automatically to about 20% of the original deadline.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Feb 22, 2008 2:41:26 PM] |
||
|
|
BobCat13
Senior Cruncher Joined: Oct 29, 2005 Post Count: 295 Status: Offline Project Badges: 
|
Reported in back room in different ways and knreed advised he's contemplating over this issue and how to resolve without increasing the DB load. Added: It is agreed that the deadline of the backup work should at least match the original quorum deadline and not default automatically to about 20% of the original deadline. This one makes a nice example of the short deadlines on reissues: lr274_ 00018_ 14-- In Progress 04/13/2008 02:56:16 05/03/2008 02:56:16 0.00 0.0 / 0.0 lr274_ 00018_ 10-- In Progress 04/13/2008 01:59:28 05/03/2008 01:59:28 0.00 0.0 / 0.0 lr274_ 00018_ 19-- In Progress 04/13/2008 01:45:04 04/17/2008 01:45:04 0.00 0.0 / 0.0 lr274_ 00018_ 8-- In Progress 04/13/2008 01:39:21 05/03/2008 01:39:21 0.00 0.0 / 0.0 lr274_ 00018_ 18-- Error 04/13/2008 01:30:37 04/13/2008 01:32:55 0.00 0.0 / 0.0 lr274_ 00018_ 4-- In Progress 04/13/2008 01:30:33 05/03/2008 01:30:33 0.00 0.0 / 0.0 lr274_ 00018_ 12-- In Progress 04/13/2008 01:21:38 05/03/2008 01:21:38 0.00 0.0 / 0.0 lr274_ 00018_ 16-- In Progress 04/13/2008 00:43:39 05/03/2008 00:43:39 0.00 0.0 / 0.0 lr274_ 00018_ 6-- In Progress 04/13/2008 00:32:21 05/03/2008 00:32:21 0.00 0.0 / 0.0 lr274_ 00018_ 17-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 15-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 1-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 3-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 13-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 11-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 2-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 9-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 7-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 5-- Waiting to be sent — — 0.00 0.0 / 0.0 lr274_ 00018_ 0-- Waiting to be sent — — 0.00 0.0 / 0.0 The bolded task is mine. It has the 20% of original even though it was just the 7th copy sent out. It's not a problem as that machine is setup with 0.75 days cache. |
||
|
|
retsof
Former Community Advisor USA Joined: Jul 31, 2005 Post Count: 6824 Status: Offline Project Badges: 
|
Since AC@H has dependencies on previous computation and there are few workunits, setting the error deadline short probably won't hurt the server much for that project.
----------------------------------------Other projects could have more variation and more impact.
SUPPORT ADVISOR
Work+GPU i7 8700 12threads School i7 4770 8threads Default+GPU Ryzen 7 3700X 16threads Ryzen 7 3800X 16 threads Ryzen 9 3900X 24threads Home i7 3540M 4threads50% |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello BobCat13,
Here is a quote from knreed: There are three separate steps involved in a error being reported, the new replica being created and it being assigned to a host. Each of those steps occurs in a separate process that are frequently on different servers. This is part of his explanation of why a reissued work unit can have a shorter deadline than the original work unit. The database is not set up to allow easy retrieval of the initial deadline. Reissued work units have short deadlines to try to complete the quorum quickly.Lawrence |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Could have been the driving reason why AC@H was extended from 5 days to 10 days standard.... Whilst avoiding the additional database access for all make up/repair work, not only AC@H, the deadline remains bearable.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|