hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-8145) Fix the editlog corruption exposed by failed TestAddStripedBlocks
Date Fri, 17 Apr 2015 23:45:59 GMT

     [ https://issues.apache.org/jira/browse/HDFS-8145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jing Zhao updated HDFS-8145:
----------------------------
    Attachment: HDFS-8145.001.patch

Thanks for the review, Nicholas! Update the patch to address the comments. The new patch only
contains the following fix:
# Do not write data block # and parity block # to editlog
# Update {{ErasureCodingZoneManager#checkMoveValidity}}: if two files are both in zones, we
need to make sure their schemas are identical.

Note that with the patch the {{TestAddStripedBlocks}} will still fail. It requires the remaining
fix that I will move to HDFS-8166.

> Fix the editlog corruption exposed by failed TestAddStripedBlocks
> -----------------------------------------------------------------
>
>                 Key: HDFS-8145
>                 URL: https://issues.apache.org/jira/browse/HDFS-8145
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: HDFS-8145.000.patch, HDFS-8145.001.patch
>
>
> {{TestAddStripedBlocks}} failed with some editlog corruption. Did some debugging, I can
see at least two issues:
> # DFSStripedOutputStream tries to send out an empty packet to close the block even if
writing 0 bytes
> # Because of the above, NN tries to close the file. This exposes another bug in {{BlockInfoStriped}},
which writes its data/parity block numbers into the close editlog but do not read them while
loading.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message