[
https://issues.apache.org/jira/browse/HDFS-11317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kuhu Shukla updated HDFS-11317:
-------------------------------
Attachment: HDFS-11317.001.patch
This moves the only possible operations that come from updateHeartbeatState to
the constructor since most of the code in the method is not called as the
values are empty arrays, zero or null.
This patch will delay the call to {{rollBlocksScheduled}} or effectively the
value set to now() for lastBlocksScheduledRollTime member till the next
heartbeat.
Since the call to updateHeartbeatState is in the constructor, traditional
mockito methods to verify the call have been unsuccessful. Appreciate any ideas
from the community on the patch and a possible test as well. Thanks!
> Modify DataNodeDescriptor() to not call UpdateHeartBeatState
> ------------------------------------------------------------
>
> Key: HDFS-11317
> URL: https://issues.apache.org/jira/browse/HDFS-11317
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Kuhu Shukla
> Assignee: Kuhu Shukla
> Attachments: HDFS-11317.001.patch
>
>
> HDFS 2.7+ DataNodeDescriptor constructor calls updateHeartBeat which is
> spamming the NN logs. This call does not update much since all the fields for
> the call are null or 0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
