hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10201) Implement undo log in parity datanode for hflush operations
Date Tue, 01 Nov 2016 21:36:59 GMT

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

Mingliang Liu updated HDFS-10201:
    Assignee: Rui Gao  (was: Mingliang Liu)

> Implement undo log in parity datanode for hflush operations
> -----------------------------------------------------------
>                 Key: HDFS-10201
>                 URL: https://issues.apache.org/jira/browse/HDFS-10201
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: erasure-coding
>            Reporter: Mingliang Liu
>            Assignee: Rui Gao
>         Attachments: HDFS-10201-demo.patch
> According to the current design doc for hflush support in erasure coding (see [HDFS-7661]),
the parity datanode (DN) needs an undo log for flush operations. After hflush/hsync, the last
cell will be overwritten when 1) the current strip is full, 2) the file is closed, 3) or the
hflush/hsync is called again for the current non-full stripe. To serve new reader client and
to tolerate failures between successful hflush/hsync and overwrite operation, the parity DN
should preserve the old cell in the undo log before overwriting it.
> As parities correspond to block group (BG) length and parity data of different BG length
may have the same block length, the undo log should also save the respective block group (BG)
length information for the flushed data.
> This jira is to track the effort of designing and implementing an undo log in parity
DN to support hflush/hsync operations.

This message was sent by Atlassian JIRA

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

View raw message