[
https://issues.apache.org/jira/browse/HDFS-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-9572:
--------------------------------
Attachment: HDFS-9572.001.patch
I'm attaching a patch. We already skipped logging the {{EOFException}} after
at least one operation was sent on the connection. This patch just proposes
that we lift the restriction that at least one operation must be sent. My
experience is that the current logging of the {{EOFException}} is useless and
distracting to operators.
Since this patch is covering a side effect (logging), I didn't include an
automated test. I did manual testing by running {{telnet localhost 50010}} and
then disconnecting immediately. Before this patch, I saw the {{EOFException}}
logged. After this patch, the exception was not logged, but I still saw the
debug message if I had debug logging enabled.
Cc [~arpitagarwal], [~jnp].
> Prevent DataNode log spam if a client connects on the data transfer port but
> sends no data.
> -------------------------------------------------------------------------------------------
>
> Key: HDFS-9572
> URL: https://issues.apache.org/jira/browse/HDFS-9572
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-9572.001.patch
>
>
> Monitoring tools may choose to check liveness of the DataNode's data transfer
> port by connecting to it. The monitoring tool will close the connection
> immediately after establishment without sending any data. When this happens,
> the DataNode encounters an unexpected EOF and logs a full stack trace. This
> creates unneeded noise in the logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
