Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 25
|
![]() |
Author |
|
dango
Senior Cruncher Joined: Jul 27, 2009 Post Count: 307 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
working again...
|
||
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I had a few CEP2 work units stuck uploading on a couple of Win7 64-bit machines also, along with a few stuck MCM work units on other machines. The MCM got unstuck by themselves, but the CEP2 did not. However, I then upgraded BOINC from 7.3.10 to 7.3.11, and thereafter the CEP2s also uploaded normally. That may be just a coincidence of timing, or maybe due to the reboot I did, but it would be interesting to see whether some BOINC versions are more susceptible to stuck uploads than others.
|
||
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
There was a set of 20 batches for MCM1 that almost every workunit in the batch reached the maximum file size before the job terminated early and sent back the data it had computed so far. This resulted in a rapid filling of the filesystem. We were able to clear some space to get work flowing again and things are now stable.
The newer batches that are now flowing do not have the same situation so it looks like we are past this issue but we will be watching closely. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Did see a long list of mcm stuck in upload of 2MB. The system requirements page specifies:
Mapping Cancer Markers 40 MB 0.1 MB 3 MB Guess whatever my 2 mcm clients had was not of the bad kind. Will you be issuing a server abort for these suspect batches? Surely there will be volunteers who still have these hanging around in their buffers unstarted, or started but not completed. |
||
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
The workunits were not bad. What happens is that the some of the types of analysis that is run by the different algorithms output quantities of data. This sometimes results in large result files. Because this project had the potential to create some very large data sets, we worked with the researchers to add controls to detect when a data set was particular large and stop the analysis at a known good point and return the result early. The researchers will then evaluate that work that was done and it will either be good enough for what they need or they will run the remain bit of the job on their local grid or resubmit the remaining bit of work in future workunits.
|
||
|
|
![]() |