You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Peter Lee (Jira)" <ji...@apache.org> on 2025/03/01 04:28:00 UTC

[jira] [Assigned] (HDDS-12447) sendDeleteCommand should never force-delete any container replica; when needed, use sendForceDeleteCommand instead

     [ https://issues.apache.org/jira/browse/HDDS-12447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Lee reassigned HDDS-12447:
--------------------------------

    Assignee: Peter Lee

> sendDeleteCommand should never force-delete any container replica; when needed, use sendForceDeleteCommand instead
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-12447
>                 URL: https://issues.apache.org/jira/browse/HDDS-12447
>             Project: Apache Ozone
>          Issue Type: Task
>            Reporter: Siyao Meng
>            Assignee: Peter Lee
>            Priority: Major
>
> Context: https://github.com/apache/ozone/pull/7976/commits/dc9ac6b9ca3766af6fd6f75be5381fcd3be9fadb#r1975852002
> bq. In a future change we could consider a refactoring where force is never given as a parameter. All methods would be of the form sendDeleteCommand or sendForceDeleteCommand. DeleteContainerCommand could have two static factory methods to build force and non-force variants with private constructors. This would make it clearer when reading the code which paths are doing the "dangerous" force delete operation.



--
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