bitly/nsq — pull request #329 by mreiferson (2014-04-11 01:11:38+00:00)
Title: nsqd: arbitrary write deadline of 1s

Unless I'm reading the source wrong it seems like nsq will close connections that aren't responsive enough. This is totally reasonable, but in our case mostly because node is so unpredictable it can cause issues. We've had a few times where CPU usage will spike, nsq will drop connections, and thrashing ensues! Could we maybe get a flag to change this value?