Listener Closes Connection After Receiving Malformed Data

Bug #589476 reported by Jeremy Jack
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released

Bug Description

I was having an issue similar to the one referenced in Question 109514 and was running around in circles until I came across and noticed that it does indeed drop the connection entirely when it receives data that it's not looking for.

Due to the vast number of data points we are querying across a vast number of servers, sometimes the data we're trying to send Graphite gets a little bungled. Yes, we absolutely can, should, and will be adding better error-checking to this but it would be amazing to have Graphite just skip the bad data, rather than close the connection entirely.

Revision history for this message
chrismd (chrismd) wrote :

Yea, initially I thought it'd be best to drop the connection but a few users have asked to change this. I have fixed this in trunk.

Changed in graphite:
status: New → Fix Committed
chrismd (chrismd)
Changed in graphite:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.