[jira] [Commented] (HDFS-8093) BP does not exist or is not under Constructionnull

[ https://issues.apache.org/jira/browse/HDFS-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15435064#comment-15435064 ] Max Schmidt commented on HDFS-8093: --- I am still facing this issue on my namenode (just happened once

[jira] [Commented] (HDFS-6973) DFSClient does not closing a closed socket resulting in thousand of CLOSE_WAIT sockets

[ https://issues.apache.org/jira/browse/HDFS-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15110342#comment-15110342 ] Max Schmidt commented on HDFS-6973: --- Sorry here, but i found out that our driver programm forgot to close

[jira] [Commented] (HDFS-6973) DFSClient does not closing a closed socket resulting in thousand of CLOSE_WAIT sockets

[ https://issues.apache.org/jira/browse/HDFS-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15108213#comment-15108213 ] Max Schmidt commented on HDFS-6973: --- I can relate to that. We're using a

[jira] [Commented] (HDFS-6804) race condition between transferring block and appending block causes "Unexpected checksum mismatch exception"

[ https://issues.apache.org/jira/browse/HDFS-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061626#comment-15061626 ] Max Schmidt commented on HDFS-6804: --- Hadoop version is 2.7.1 used on Ubuntu 14.04.3 LTS. > race

[jira] [Commented] (HDFS-6804) race condition between transferring block and appending block causes "Unexpected checksum mismatch exception"

[ https://issues.apache.org/jira/browse/HDFS-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14991579#comment-14991579 ] Max Schmidt commented on HDFS-6804: --- We can confirm this in a 3-node cluster with replication-factor=2.