Closed djmally closed 7 years ago
TCP connections are being unexpectedly closed. It's possible that you have a firewall or NAT killing your connections after a few minutes of inactivity. Try setting your heartbeat interval back down to the default 30 seconds.
Can you provide any more logs or reproducible setup?
This indeed might be related to #199, see https://github.com/nsqio/go-nsq/issues/199#issuecomment-294375520
Closing this & moving discussion to #199
Hi folks,
My team develops a distributed web fuzzing tool in Go, & we use NSQ as our message queueing system, using the
go-nsq
client. We've been seeing very high rates of messages like these in our logs recently, and wondered if you might have more insight, as it's very unclear to us what's causing this to happen:We almost always see a message like
draining... waiting for 1 messages in flight
surrounding these messages.We're running 8 nsqd nodes and 1 nsqlookupd instance, and running NSQ version 0.3.8. We've set the following nsqd configurations:
It seems like this also might be related to https://github.com/nsqio/go-nsq/issues/199