[
https://issues.apache.org/jira/browse/HDFS-13473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515693#comment-16515693
]
He Xiaoqiao commented on HDFS-13473:
------------------------------------
upload v005 patch to fix bug about auto-update block token keys which trigger
by HeartbeatManager#Monitor, and failed ut
{{hadoop.hdfs.server.namenode.ha.TestFailoverWithBlockTokensEnabled
}} is related to this bug.
I checked another failed ut {{hadoop.hdfs.TestEncryptedTransfer}} and tested
locally, it seems to work fine and might not relate to this patch.
could anyone help to double check at convenience?
> 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, HDFS-13473-trunk.002.patch,
> HDFS-13473-trunk.003.patch, HDFS-13473-trunk.004.patch,
> HDFS-13473-trunk.005.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
