You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:40:08 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 ]
Ethan Rose updated HDDS-2912:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org