During the day when we have heavy search load I see a few TransportExceptions in the elasticsearch logs.
Transport response handler not found of id 
We use libcurl to query elastisearch and this manifest's on the client side as
Curl Error at items/_count?: Failure when receiving data from the peer (56)
The search is simple filtering (no scoring) and getting counts. The CPU/Memory on all the nodes looks fine and don't see anything queueing on elasticsearch's end.
I am also seeing lots of young gc collections while this is happening which could be related. I am trying to understand under what conditions the exception occurs and what does it mean ?
Using elasticsearch 2.4 version.