[
https://issues.apache.org/jira/browse/HDFS-15661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271048#comment-17271048
]
Lisheng Sun edited comment on HDFS-15661 at 1/25/21, 2:57 AM:
--------------------------------------------------------------
Thank [~LiJinglun] for nice fixing，according to the way we commucate offline.
Can you fix the checkstyle and confirm the failed ut is unrelated to the v04
patch?
was (Author: leosun08):
Thank [~LiJinglun] for nice fixing，according to the way we commucate offline.
Can you fix the checkstyle and confirm the failed ut is unrelated to the v04
firstly ?
> The DeadNodeDetector shouldn't be shared by different DFSClients.
> -----------------------------------------------------------------
>
> Key: HDFS-15661
> URL: https://issues.apache.org/jira/browse/HDFS-15661
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Jinglun
> Assignee: Jinglun
> Priority: Major
> Attachments: HDFS-15661.001.patch, HDFS-15661.002.patch,
> HDFS-15661.003.patch, HDFS-15661.004.patch
>
>
> Currently the DeadNodeDetector is a member of ClientContext. That means it is
> shared by many different DFSClients. When one DFSClient.close() is invoked,
> the DeadNodeDetecotor thread would be interrupted and impact other DFSClients.
> From the original design of HDFS-13571 we could see the DeadNodeDetector is
> supposed to share dead nodes of many input streams from the same client.
> We should move the DeadNodeDetector as a member of DFSClient instead of
> ClientContext.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
