Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 966 times and has 2 replies Next Thread
bieberj
Senior Cruncher
United States
Joined: Dec 2, 2004
Post Count: 406
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Suggestion: - short deadline shouldn't be issued prematurely...

I looked at the new Rice project result status as my computer is waiting to start this new task. Looks like I am among the first to get the new project with a short deadline. While I can see the reason why this occurred:

<snip>

R00001_ 0cc428de44f0b164b8196d4cd4885407_ 19_ 0-- In Progress 05/12/2008 18:56:21 05/22/2008 18:56:21 0.00 0.0 / 0.0

<snip>

R00001_ 0cc428de44f0b164b8196d4cd4885407_ 19_ 19-- In Progress 05/12/2008 18:42:08 05/14/2008 18:42:08 0.00 0.0 / 0.0

<snip>

R00001_ 0cc428de44f0b164b8196d4cd4885407_ 19_ 6-- Error 05/12/2008 17:59:28 05/12/2008 18:02:46 0.00 0.0 / 0.0

<snip>

R00001_ 0cc428de44f0b164b8196d4cd4885407_ 19_ 2-- Waiting to be sent — — 0.00 0.0 / 0.0

There are six waiting to be sent.

I also saw something similar for HPF2 a while back.

My suggestion is that if there is an error that occurs before all jobs for the initial quorum is sent, then when a job is sent to replace the one that reported the error, it should have normal deadline instead of short deadline.
[May 12, 2008 7:59:10 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: Suggestion: - short deadline shouldn't be issued prematurely...

Hi bieberj,

this was diagnosed before and because of database performance concerns not yet addressed.

The 10 day original deadline ensures that the repair job will at least get around 2 days (20% of original deadline plus / minus).

Usually these jobs go to 'reliable' hosts.... those normally returning work within 24 hours or there abouts, meaning those clients might be reshuffling work automatically, but never jeopardizing any of the other deadlines for buffered tasks in the queue (there is always the occasional aberration, but what to expect on hundreds of thousands of devices).
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at May 12, 2008 8:12:15 PM]
[May 12, 2008 8:08:58 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Suggestion: - short deadline shouldn't be issued prematurely...

Hello bieberj,
knreed has explained that this happens because there is no easy way for the 'resend' function to find out what the initial deadline was. He said that he might redesign the database to add this information.

So it might happen, but probably not while he is as busy as he is right now.

Lawrence
[May 12, 2008 8:12:14 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread