On Wed, Jan 4, 2012 at 12:50 PM, Jonathan Lange <[email protected]> wrote: > On Wed, Jan 4, 2012 at 3:17 AM, Julian Edwards > <[email protected]> wrote: >> FYI I figured this out in the end. >> >> It turns out that writing OOPSes is deferred to a thread pool. However, the >> AMQP port was not open on the firewall, so once 10 OOPSes were queued up, it >> was hanging. >> > > I guess that means there should be a timeout on writing OOPSes.
Actually on tcp connects to all internal services. We don't 'write' oopses anymore except when AMQP is down - and the linear write code path is local IO and pretty snappy. -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
