[
https://issues.apache.org/jira/browse/HDFS-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-9572:
--------------------------------
Hadoop Flags: Reviewed
The license warnings are a known issue tracked in HDFS-9571. There are no new
license warnings introduced by this patch.
The failure in {{TestDFSUpgradeFromImage}} was just introduced by HDFS-9569. I
have reverted that patch and reopened the issue.
I cannot get a repro of the remaining failures. I've been seeing a lot of
pre-commit errors lately that look like permission errors trying to access
standard shared libraries from shell utilities.
{code}
Tests run: 7, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 29.453 sec <<<
FAILURE! - in
org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshotBlocksMap
testDeletionWithZeroSizeBlock3(org.apache.hadoop.hdfs.server.namenode.snapshot.TestSnapshotBlocksMap)
Time elapsed: 0.89 sec <<< ERROR!
java.lang.RuntimeException: Error while running command to get file permissions
: ExitCodeException exitCode=127: /bin/ls: error while loading shared
libraries: libacl.so.1: failed to map segment from shared object: Permission
denied
{code}
This is going to need further investigation.
I'm going to commit this patch.
> 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)
