Hello gang. I'm back from the latest bout of alternative career maintenance. Seems like I didn't miss too much, and unlike normal the server problems waited until *after* I returned. My next disappearance (only about 10 days) will be in mid-April (touring in Argentina, Chile, and Brazil).

Before the usual Tuesday server outage Jeff noticed the splitters having trouble inserting new work into the science database. After some detective work and tests we found we hit one of several possible informix logical limits: we ran out of extents in the workunit table.

Not a big deal, and we hit this limit with other tables several times before. But the fix is a bit of a hassle. Basically you have to recreate a whole new table from scratch with more extents and repopulate it with all the data from the "full" table. We have a billion workunits in that table, so to speed this process up we only moved over workunits 90 days old (or newer) before turning the projects on again. We only need 90 days of recent workunits around for the assimilators to work, but to get the NTPCkrs rolling again we need to repopulate the whole thing, which we'll do more casually.

Since we're talking about database stuff.. is there anything that can be done for "stuck" WUs that have been pending for several months, or in some cases..years? They are ones where _0 and _1 got credit granted before _2 returned their result, and therefore, _2 is stuck waiting.Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Since we're talking about database stuff.. is there anything that can be done for "stuck" WUs that have been pending for several months, or in some cases..years? They are ones where _0 and _1 got credit granted before _2 returned their result, and therefore, _2 is stuck waiting.