[
https://issues.apache.org/jira/browse/HDFS-17504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023241#comment-18023241
]
ASF GitHub Bot commented on HDFS-17504:
---------------------------------------
github-actions[bot] commented on PR #6792:
URL: https://github.com/apache/hadoop/pull/6792#issuecomment-3340861296
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.
> DN process should exit when BPServiceActor exit
> -----------------------------------------------
>
> Key: HDFS-17504
> URL: https://issues.apache.org/jira/browse/HDFS-17504
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Zilong Zhu
> Assignee: Zilong Zhu
> Priority: Major
> Labels: pull-request-available
>
> BPServiceActor is a very important thread. In a non-HA cluster, the exit of
> the BPServiceActor thread will cause the DN process to exit. However, in a HA
> cluster, this is not the case.
> I found HDFS-15651 causes BPServiceActor thread to exit and sets the
> "runningState" from "RunningState.FAILED" to "RunningState.EXITED", it can
> be confusing during troubleshooting.
> I believe that the DN process should exit when the flag of the BPServiceActor
> is set to RunningState.FAILED because at this point, the DN is unable to
> recover and establish a heartbeat connection with the ANN on its own.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
