[
https://issues.apache.org/jira/browse/HDFS-16559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18037570#comment-18037570
]
ASF GitHub Bot commented on HDFS-16559:
---------------------------------------
github-actions[bot] commented on PR #4233:
URL: https://github.com/apache/hadoop/pull/4233#issuecomment-3519306935
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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
> Labels: pull-request-available
> Time Spent: 20m
> 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.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
