[
https://issues.apache.org/jira/browse/HDFS-15067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013555#comment-17013555
]
Surendra Singh Lilhore commented on HDFS-15067:
-----------------------------------------------
Thanks [~ayushtkn] .
{quote} I am of the opinion, rather than having two logics, have one. default
value can be like a fallback, you don't configure or you configure it wrong, I
go back to say x, rather than having two logics
{quote}
Will check this, will try to use some fix number.
{quote}This condition checks in layman terms that if the known active turned to
standby, in this case Ideally we should reset the heartbeats for all the bps,
so that the new active can be identified, otherwise the bps tracking the
standby will be at max dn interval, so it will be delayed in identifying the
new active.
{quote}
Agree with you, need to handle this, I will update in next patch with remaining
UT's and documentation.
> Optimize heartbeat for large cluster
> ------------------------------------
>
> Key: HDFS-15067
> URL: https://issues.apache.org/jira/browse/HDFS-15067
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: datanode
> Affects Versions: 3.1.1
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Priority: Major
> Attachments: HDFS-15067.01.patch, HDFS-15067.02.patch,
> image-2020-01-09-18-00-49-556.png
>
>
> In a large cluster Namenode spend some time in processing heartbeats. For
> example, in 10K node cluster namenode process 10K RPC's for heartbeat in each
> 3sec. This will impact the client response time. This heart beat can be
> optimized. DN can start skipping one heart beat if no
> work(Write/replication/Delete) is allocated from long time. DN can start
> sending heart beat in 6 sec. Once the DN stating getting work from NN , it
> can start sending heart beat normally.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
