// DBOINCP-300: added node comment count condition in order to get Preview working ?>
Kim Kaos
Joined: 12 Jul 11
Posts: 9
Credit: 1743535
RAC: 0
23 Mar 2012 15:46:58 UTC
Topic 196250
(moderation:
)
I´ve a quazilllion unsent Gravitational Wave S6 GC search v1.01 (SSE2) jobs – jobs I´ve finis long time ago – but now they just laying there and nobody deals with them.
I spot-checked three of your oldest pending GC jobs, and all three had a first quorum partner who failed to return a valid result within deadline, and showed that the work had then been sent on to a new quorum partner, who had not yet returned but was not yet past deadline. So those three to my eye appear all right and proper--not "unsent" with nobody dealing with them. Some examples of what concerns you would help you get a response.
Where does it say its unsent? In fact it says its "awaiting validation", so clearly its been sent and come back.
As explained above by archae86 its the 2nd person who has "timed out" (passed their deadline). It will be sent out to another user.
I guess, that what the OP is trying to show, is that the timed out WU was on 15 march and is stil not resent to another host... Usually task were sent again the next day after the deadline...
May be is something related with the fact that this search is close to the end and due to the locality issue may be a lot of people opted out from this app... (A wild guess, indeed)
This is certainly related to the S6Bucket -> S6LV1 transition. In order to start the S6LV1 workunit generator we had to generate all remaining ~125,000 S6Bucket workunits, i.e. 250,000 (initially unsent) tasks. These are sent out as requested by the clients, of course not all in a day. Currently there are <15,000 S6Bucket tasks remaining to be sent, which should happen in the next 24h. The task you mentioned should be among these.
This is certainly related to the S6Bucket -> S6LV1 transition. In order to start the S6LV1 workunit generator we had to generate all remaining ~125,000 S6Bucket workunits, i.e. 250,000 (initially unsent) tasks. These are sent out as requested by the clients, of course not all in a day. Currently there are <15,000 S6Bucket tasks remaining to be sent, which should happen in the next 24h. The task you mentioned should be among these.
Unsent Gravitational Wave S6 GC search v1.01 (SSE2) jobs
)
how about posting links to a few examples.
I spot-checked three of your oldest pending GC jobs, and all three had a first quorum partner who failed to return a valid result within deadline, and showed that the work had then been sent on to a new quorum partner, who had not yet returned but was not yet past deadline. So those three to my eye appear all right and proper--not "unsent" with nobody dealing with them. Some examples of what concerns you would help you get a response.
They looks like this
)
They looks like this
http://img43.imageshack.us/img43/1136/unsent.jpg
Where does it say its unsent?
)
Where does it say its unsent? In fact it says its "awaiting validation", so clearly its been sent and come back.
As explained above by archae86 its the 2nd person who has "timed out" (passed their deadline). It will be sent out to another user.
BOINC blog
RE: Where does it say its
)
I guess, that what the OP is trying to show, is that the timed out WU was on 15 march and is stil not resent to another host... Usually task were sent again the next day after the deadline...
May be is something related with the fact that this search is close to the end and due to the locality issue may be a lot of people opted out from this app... (A wild guess, indeed)
RE: Where does it say its
)
Look under status - I have lots of them now
This is certainly related to
)
This is certainly related to the S6Bucket -> S6LV1 transition. In order to start the S6LV1 workunit generator we had to generate all remaining ~125,000 S6Bucket workunits, i.e. 250,000 (initially unsent) tasks. These are sent out as requested by the clients, of course not all in a day. Currently there are <15,000 S6Bucket tasks remaining to be sent, which should happen in the next 24h. The task you mentioned should be among these.
BM
BM
RE: This is certainly
)
Thx.