[
https://issues.apache.org/jira/browse/HDFS-13473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442811#comment-16442811
]
Daryn Sharp commented on HDFS-13473:
------------------------------------
A bit concerned about doing a blocking rpc with retries.
What about something like the DN's heartbeat contains the current key version
it has? The NN's handleHeartbeat compares with its current key, calls
setNeedKeyUpdate if different. Then we don't need additional rpcs, confs, and
minimizes the code changes.
> 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
> Assignee: 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 Keys.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
