hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zephyr Guo (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-13243) File might get broken because of calling close and sync in same time
Date Wed, 07 Mar 2018 12:38:00 GMT
Zephyr Guo created HDFS-13243:

             Summary: File might get broken because of calling close and sync in same time
                 Key: HDFS-13243
                 URL: https://issues.apache.org/jira/browse/HDFS-13243
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
    Affects Versions: 2.7.2, 3.2.0
            Reporter: Zephyr Guo
             Fix For: 3.2.0

HDFS File might get broken because of corrupt block(s) that could be produced by calling close
and sync in the same time.

When calling close was not successful, UCBlock status would change to COMMITTED, and if a
sync request gets popped from queue and processed, sync operation would change the last block

After that, DataNode would report all received block to NameNode, and will check Block length
of all COMMITTED Blocks. But the block length was already different between recorded in NameNode
memory and reported by DataNode, and consequently, the last block is marked as corruptted
because of inconsistent length.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org

View raw message