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 2022/02/07 21:02:00 UTC

[jira] [Updated] (HDDS-6063) [Multi-Tenant] Use VOLUME_LOCK in read and write requests

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

ASF GitHub Bot updated HDDS-6063:
---------------------------------
    Labels: pull-request-available  (was: )

> [Multi-Tenant] Use VOLUME_LOCK in read and write requests
> ---------------------------------------------------------
>
>                 Key: HDDS-6063
>                 URL: https://issues.apache.org/jira/browse/HDDS-6063
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ethan Rose
>            Assignee: Siyao Meng
>            Priority: Major
>              Labels: pull-request-available
>
> We have decided to use the existing VOLUME_LOCK for multi tenant read and write requests, instead of adding a new lock. We should check that all write requests are using this lock properly, and add it to read requests as necessary. We must also fix read requests which are iterating keys to check both the cache and DB.



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