[HDDS-6063] [Multi-Tenant] Use VOLUME_LOCK in read and write requests, and some minor refactoring

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: HDDS-4944
• Fix Version/s: HDDS-4944
• Labels: pull-request-available
• Assignee: Siyao Meng
• Reporter: Ethan Rose
• Created: 03/Dec/21 00:07
• Updated: 08/Mar/22 23:30
• Resolved: 07/Mar/22 19:16

Description

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

2. We must also fix read requests which are iterating keys to check both the cache and DB.

3. Some minor refactoring, as mentioned in the PR description: https://github.com/apache/ozone/pull/3051

Issue Links

• incorporates: HDDS-6274 [Multi-Tenant] Properly iterate cache and table in OzoneManager#listTenant
• links to: GitHub Pull Request #3051