graphite-dev team mailing list archive

[chrismd <question159187@xxxxxxxxxxxxxxxxxxxxx>]

Question #159187 on Graphite changed:
https://answers.launchpad.net/graphite/+question/159187

    Status: Open => Answered

chrismd proposed the following answer:
It is probably the way your client applications are connecting to
Graphite and sending data. I've seen it many times in the past where
there will be a client that does something like this:

def send_metric(metric, value):
  sock = socket.socket()
  sock.sendall("%s %f %d" % (metric, value, time.time())
  sock.close()

for metric, value in collect_lots_of_data():
  send_metric(metric, value)

This causes tons of very short-lived connections that linger around in
TIME_WAIT for a while. Given the netstat data can you tell what clients
are initiating these connections?

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.