You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/11/20 02:58:00 UTC
[jira] [Updated] (HDDS-6022) [Multi-Tenant] Implement DeleteTenant: `ozone tenant delete`
[ https://issues.apache.org/jira/browse/HDDS-6022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-6022:
---------------------------------
Labels: pull-request-available (was: )
> [Multi-Tenant] Implement DeleteTenant: `ozone tenant delete`
> ------------------------------------------------------------
>
> Key: HDDS-6022
> URL: https://issues.apache.org/jira/browse/HDDS-6022
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Siyao Meng
> Assignee: Siyao Meng
> Priority: Major
> Labels: pull-request-available
>
> - Add a new field {{refCount}} for Ozone volumes that acts like a lock which prevents the volume from being deleted if {{refCount > 0}}
> - Implement `ozone tenant delete` that will only remove all tenant information from DB (and Ranger) if there are no users assigned to this tenant and the volume is empty.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org