You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Hui Fei (Jira)" <ji...@apache.org> on 2026/06/09 04:28:03 UTC
[jira] [Updated] (HDDS-2912) Separate srubber from pipeline creation
[ https://issues.apache.org/jira/browse/HDDS-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hui Fei updated HDDS-2912:
--------------------------
Target Version/s: 2.3.0 (was: 2.2.0)
<<Bulk update>>
Apache Ozone 2.2.0 release is in progress. I'm updating all unresolved jiras targeting 2.2.0 to retarget 2.3.0.
> Separate srubber from pipeline creation
> ---------------------------------------
>
> Key: HDDS-2912
> URL: https://issues.apache.org/jira/browse/HDDS-2912
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Li Cheng
> Priority: Minor
>
> Xiaoyu's Review from HDDS-1564:
> [BackgroundPipelineCreator.java|http://backgroundpipelinecreator.java/]
> Line 115: should we separate the scrubber from the pipeline creation. This way the creation and destroy pipeline are executed independently.
>
> Comment from Li:
> Currently BackgroundPipelineCreator is having its own bg thread and scheduler, but its solely operations are scrubbing pipelines and creating pipelines. Do we need to have background thread for destroying pipelines? I feel like we want to maintain this thread for all pipeline background operations. Shall I refactor BackgroundPipelineCreator to BackgroundPipelineHandler? So that all bg pipeline operations can be handled by this thread.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org