hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "He Xiaoqiao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-13473) DataNode update BlockKeys using mode PULL rather than PUSH from NameNode
Date Wed, 18 Apr 2018 14:31:00 GMT

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

He Xiaoqiao updated HDFS-13473:
    Attachment: HDFS-13473-trunk.001.patch

> DataNode update BlockKeys using mode PULL rather than PUSH from NameNode
> ------------------------------------------------------------------------
>                 Key: HDFS-13473
>                 URL: https://issues.apache.org/jira/browse/HDFS-13473
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>            Reporter: He Xiaoqiao
>            Priority: Major
>         Attachments: HDFS-13473-trunk.001.patch
> It is passive behavior about updating Block keys for DataNode currently, and it depends
on if NameNode return #KeyUpdateCommand for heartbeat response.
> There are several problems of this Block keys synchronization mode:
> a. NameNode can't be sensed about if Block Keys reach DataNode successfully,
> b. It is also not sensed for DataNode who meets some exception while receive or process
heartbeat response which include BlockKeyCommand,
> such as HDFS-13441 and HDFS-12749 mentioned.
> So I propose improve Push Block Keys from NameNode for DataNode to DataNode Pull Block

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