Welcome to MilkyWay@home

Possible Cause for Continuing DB Meltdowns Detected


Advanced search

Message boards : Number crunching : Possible Cause for Continuing DB Meltdowns Detected
Message board moderation

To post messages, you must log in.

AuthorMessage
Alinator

Send message
Joined: 7 Jun 08
Posts: 464
Credit: 56,639,936
RAC: 0
50 million credit badge10 year member badge
Message 3960 - Posted: 29 Jun 2008, 18:22:29 UTC
Last modified: 29 Jun 2008, 19:19:48 UTC

In cleaning up the detritus left behind in my local task log database from the last meltdown, I noticed that one of the tasks which I had received from just before the project ground to a halt got a 221 Redundant Result abort from the project when I reenabled MW on my hosts.

Experience over on SAH with the workload burn rate and host volume they carry showed they could not handle having the advanced features like Lost Work Autoresends or Redundant Result Aborting enabled without causing the serious negative effects on DB performance in other areas periodically.

So it might be worthwhile to see if disabling 221 functionality helps, since it's pretty clear now that the periodic completed task purge daemon isn't the primary factor causing the problem. It's far more likely that having to search every host's whole DB record every time there's a scheduler request to see if any work in progress is redundant is the culprit.

Alinator
ID: 3960 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Possible Cause for Continuing DB Meltdowns Detected

©2020 Astroinformatics Group