Not sure if available in all versions, but at least the linux FAHClient has the --dump (wu|all) that will dump the work unit and inform the servers.
I looked into this just a moment ago, when I saw that my server had spent five days working on a WU, done about 40%, timeout later today, expiry in 3 days and eta was still about 7 days. I knew it would never make it on time and the client would dump it anyways in a few days when the expiry time is passed. My options as I saw would be:
- Not touch it, have it waste electricity for a few more days, then dump the expired WU and get new work.
- Shut down the box for a couple of days, save the energy, then dump the expired WU and get new work.
- Dump the WU now and get new work right away.
The third option seemed overall the most efficient, so I decided to go with that. I got a new WU with and the ETA for this shows just a few hours, so it seems something was wrong with the old WU.
In case someone on the team wants to look into the old WU, here's a log for when I dumped it:
- Code: Select all
12:57:48:WARNING:Dumping WU00 per user request
12:57:48:WU00:FS00:Sending unit results: id:00 state:SEND error:DUMPED project:13821 run:237 clone:1 gen:83 core:0xa7 unit:0x0000006080fccb095c883992cea0aa06
12:57:49:WU00:FS00:Connecting to 155.247.166.219:8080
12:57:50:WU00:FS00:Server responded WORK_QUIT (404)
12:57:50:WARNING:WU00:FS00:Server did not like results, dumping
I recommend making dumping a WU simple, so that other people with a hopeless WU could also put that time and energy into better use. That way you learn sooner if you need to send that WU to someone else and the science can continue faster. I don't believe cherry picking would actually become a real issue.