[ https://issues.apache.org/jira/browse/HDDS-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178919#comment-17178919 ]
Glen Geng edited comment on HDDS-4125 at 8/17/20, 11:32 AM: ------------------------------------------------------------ Since the thread pool that removes RATIS ONE pipeline is removed, we need either remove RATIS ONE pipeline immediately or let scrubPipeline() to handle RATIS ONE Pipeline. {code:java} scheduler.schedule(() -> destroyPipeline(pipeline), pipelineDestroyTimeoutInMillis, TimeUnit.MILLISECONDS, LOG, String.format("Destroy pipeline failed for pipeline:%s", pipeline)); {code} was (Author: glengeng): Since the thread pool that remove RATIS ONE pipeline is removed, we need either remove the pipeline immediately or let scrubPipeline() to handle RATIS ONE Pipeline. {code:java} scheduler.schedule(() -> destroyPipeline(pipeline), pipelineDestroyTimeoutInMillis, TimeUnit.MILLISECONDS, LOG, String.format("Destroy pipeline failed for pipeline:%s", pipeline)); {code} > Pipeline is not removed when a datanode goes stale > -------------------------------------------------- > > Key: HDDS-4125 > URL: https://issues.apache.org/jira/browse/HDDS-4125 > Project: Hadoop Distributed Data Store > Issue Type: Sub-task > Components: SCM HA > Reporter: Nanda kumar > Assignee: Nanda kumar > Priority: Major > Labels: pull-request-available > > When a node goes stale the pipelines in that node have to be closed and > removed from {{PipelineManager}}. Currently, the pipeline is only closed and > left in {{PipelineManager}}. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org