[
https://issues.apache.org/jira/browse/HDFS-16062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041401#comment-18041401
]
ASF GitHub Bot commented on HDFS-16062:
---------------------------------------
github-actions[bot] commented on PR #3092:
URL: https://github.com/apache/hadoop/pull/3092#issuecomment-3590739387
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.
> When a DataNode hot reload configuration, JMX will block for a long time
> ------------------------------------------------------------------------
>
> Key: HDFS-16062
> URL: https://issues.apache.org/jira/browse/HDFS-16062
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When executing the reconfig command on the DataNode, for example:
> hdfs dfsadmin -reconfig datanode hadoopxxxx.jd.163.org:8025 start
> At this time, the JMX of the DataNode is requested. At this time, JMX will
> still block after a long time.
> When this happens, it is mainly caused by some disk exceptions (such as disk
> unavailability) on the DataNode. At this time, DataNode#JMX will block.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
