[
https://issues.apache.org/jira/browse/HDFS-16559?focusedWorklogId=761436&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-761436
]
ASF GitHub Bot logged work on HDFS-16559:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Apr/22 10:11
Start Date: 24/Apr/22 10:11
Worklog Time Spent: 10m
Work Description: yuanboliu opened a new pull request, #4233:
URL: https://github.com/apache/hadoop/pull/4233
…ime.
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
IBR opeeration is seperated from heartbeat thread since
[HDFS-16016](https://issues.apache.org/jira/browse/HDFS-16016), which is great.
But IBR thread is using the expireTime of heart beat to deside whether wait
or not. In a high load DataNode, IBR thread becomes an infinit loop without
sleeping and consuming 100% cpu because of the latency of heartbeat reporting.
Issue Time Tracking
-------------------
Worklog Id: (was: 761436)
Remaining Estimate: 0h
Time Spent: 10m
> Seperate IBR thread waiting time from heart beat waiting time.
> --------------------------------------------------------------
>
> Key: HDFS-16559
> URL: https://issues.apache.org/jira/browse/HDFS-16559
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Yuanbo Liu
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> IBR opeeration is seperated from heartbeat thread since HDFS-16016, which is
> great.
> But IBR thread is using the expireTime of heart beat to deside whether wait
> or not. In a high load DataNode, IBR thread becomes an infinit loop without
> sleeping and consuming 100% cpu because of the latency of heartbeat reporting.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
