[
https://issues.apache.org/jira/browse/HDDS-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-6063:
-----------------------------
Description:
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.- - No longer the case, see the comment in HDDS-6274
was: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.
> [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
> Affects Versions: HDDS-4944
> 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.- - No longer the case, see the comment in HDDS-6274
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
