Comment 3 for bug 701208

I made the changes suggested by Jason, actually I did 1000/45, and the problem has gone away. It doesn't seem unreasonable to have a fair number of holds (I've got 116) - I think the client should maybe be better about how it loads them. Choking out cstore drones seems like it could be avoided. Perhaps we could do paging? Maybe we could handle timeouts by throttling the request rate rather than exploding into flaming error messages? I wonder what the cost to system resources would be by having a significantly higher number of max_children... If I'm seeing this on a server running a smallish single library then I'd guess it's actually fairly common.