Daryl C. W. O'Shea writes: > Justin Mason wrote: > > Daryl C. W. O'Shea writes: > > >> This won't work. I did nearly the same thing and reverted it. The > >> server will basically hang up trying to retry these messages. The > >> outstanding message list needs to be dealt with to do this. > >> > >> This was yet another thing I wanted to get to before being slammed with > >> "real" work this last week. :( > > > > uh, crap. The nightly mass-check on the zone is currently hosed because > > ofthis bug, and I'm not going to be able to get to it either for a few > > days, what with a massive switch of servers and an impending driving > > test... > > I'd at least revert this change for now, as it is it'll cause the > mass-check processes never to end (if it skips even a single message), > consuming more and more memory (and cpu time depending on the number of > messages skipped) every time another instance starts.
argh. > What's causing the messages to disappear during the mass-check run? probably the corpus being updated via rsync. it's a very big corpus. --j.
