hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gordon Wang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-6505) Can not close file due to last block is marked as corrupt
Date Tue, 10 Jun 2014 03:05:01 GMT
Gordon Wang created HDFS-6505:

             Summary: Can not close file due to last block is marked as corrupt
                 Key: HDFS-6505
                 URL: https://issues.apache.org/jira/browse/HDFS-6505
             Project: Hadoop HDFS
          Issue Type: Bug
    Affects Versions: 2.2.0
            Reporter: Gordon Wang

After appending a file, client could not close it. Because namenode could not complete the
last block in file. The UC status of last block remained as COMMIT and never change.
The namenode log was like this.
INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: BLOCK* checkFileProgress: blk_1073741920_13948{blockUCState=COMMITTED,
replicas=[ReplicaUnderConstruction[|RBW]]} has not reached minimal replication

After going through the log of namenode, I found a log like this
INFO BlockStateChange: BLOCK NameSystem.addToCorruptReplicasMap: blk_1073741920 added as corrupt
on by sdw3/ because client machine reported it
But actually, the last block was finished successfully in the data node. Because I could find
the log in datanode
INFO org.apache.hadoop.hdfs.server.datanode.DataNode: DataTransfer: Transmitted BP-649434182-
(numBytes=50120352) to /
INFO org.apache.hadoop.hdfs.server.datanode.DataNode.clienttrace: src: /,
dest: /, bytes: 51686616, op: HDFS_WRITE, cliID: libhdfs3_client_random_741511239_count_1_pid_215802_tid_140085714196576,
offset: 0, srvID: DS-2074102060-, blockid: BP-649434182-,
duration: 189226453336
INFO org.apache.hadoop.hdfs.server.datanode.DataNode: PacketResponder: BP-649434182-,
type=LAST_IN_PIPELINE, downstreams=0:[] terminating

This message was sent by Atlassian JIRA

View raw message