Using logstash 1.4.2 pushing to an elastic search 1.1.1 instance on a separate server. Pulling log items from AWS SQS. Everything works fine the first several hours or so, but then the following begins to appear in the logstash log.
:message=>"Error reading SQS queue.", :error=>#<OpenSSL::SSL::SSLError: Socket closed>
As soon as the first of these errors appears the rate in which logstash empties the queue slows. Eventually it stops completely as more errors appear. The java process hosting logstash continues to operate without issue.
CPU consumption stays around 30% on an m3.xlarge instance, so it appears to have enough horsepower.
Does this sound like a bug, or is there something I need to do to either prevent socket loss or get logstash to reopen them?