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

Posted to issues@ozone.apache.org by "Siyao Meng (Jira)" <ji...@apache.org> on 2022/05/25 16:38:00 UTC

[jira] [Updated] (HDDS-6701) [Multi-Tenant] Add proper locking between Ranger background sync service and tenant requests; bug fixes

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

Siyao Meng updated HDDS-6701:
-----------------------------
    Summary: [Multi-Tenant] Add proper locking between Ranger background sync service and tenant requests; bug fixes  (was: [Multi-Tenant] Add proper locking between Ranger Background Sync Service and tenant requests)

> [Multi-Tenant] Add proper locking between Ranger background sync service and tenant requests; bug fixes
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-6701
>                 URL: https://issues.apache.org/jira/browse/HDDS-6701
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Siyao Meng
>            Assignee: Siyao Meng
>            Priority: Major
>              Labels: pull-request-available
>
> 1. This is a follow-up jira to HDDS-6371 to ensure proper locking.
> 2. Need two versions of createTenantAccess: InAuthorizer and InDB (updates cache)
> 3. Implement tenant delete Ranger call
> 4. Check HTTP response code from Ranger



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org