It certainly happened at SETI a few days ago when the transitioner went offline (the server hosting the transitioner process crashed). 'Results ready to send' peaked at about 1,750,000 - the usual limit keeps it between 200,000 / 250,000 - from which we deduce that the splitters (their workunit generators) carried on running while the displayed figures weren't being updated. In their case, the database was comparatively lightly loaded at the time, and some swift homework by a staff member prevented it getting out of hand, but it was a near miss.
> Is it possible for the work generator to go a bit haywire? If we're using > a policy which checks to see the number of unsent workunits, if one of the > feeder queries gets hung up, is it possible for the work generator to keep > thinking that there aren't enough unsent workunits because the feeder > hasn't updated things and then repeatedly generate more workunits which > could flood the database? > > I'm wondering if this is a possibility because I think it's what might > have happened with the most recent MilkyWay@Home crash... > > thanks, > --Travis _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
