You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ivandika3 (via GitHub)" <gi...@apache.org> on 2026/09/30 02:50:30 UTC
[PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
ivandika3 opened a new pull request, #11365:
URL: https://github.com/apache/ozone/pull/11365
## What changes were proposed in this pull request?
We have supported automatic cache tracking and cleanup in [HDDS-13365](https://issues.apache.org/jira/browse/HDDS-13365), but keep using CleanupTableInfo for safe guards. If [HDDS-13365](https://issues.apache.org/jira/browse/HDDS-13365) works well, we can remove the CleanupTableInfo entirely.
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-16643
## How was this patch tested?
CI.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4180435926
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/S3SecretManager.java:
##########
@@ -102,6 +105,7 @@ default void updateCache(String accessId, S3SecretValue secret) {
if (cache != null) {
LOG.info("Updating cache for accessId/user: {}.", accessId);
cache.put(accessId, secret);
+ TableCacheUpdateTracker.recordCacheUpdate(S3_SECRET_TABLE);
Review Comment:
The `S3SecretManager` uses table cache, but the implementation does not use the unified `TypedTable`, probably because it supports both external S3 secret store (i.e. `VaultSecretStore`) and embedded (OM RocksDB), but Ozone table mechanisms only support RocksDB (`TypedTable` uses `RDBTable` as the underlying store).
There is also cache related cleanup logic in `OzoneManagerDoubleBuffer` just for `S3_SECRET_TABLE` which I think it kind of hacky since it has already been supported by the OM `TableCache`. Technically, it should be possible to unify it by making the `S3SecretCache` to be a `TableCache`, but this means that we might need to make OM to generalize the table cache and store implementation API (where the store can support other remote store like `VaultStore` or even things like remote KV store which means that OM only stores in-memory cache similar to QiHoo OM architecture), which is going to be quite involved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "rich7420 (via GitHub)" <gi...@apache.org>.
rich7420 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4173282182
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/snapshot/OMSnapshotPurgeResponse.java:
##########
@@ -30,21 +28,15 @@
import org.apache.hadoop.ozone.om.OmMetadataManagerImpl;
import org.apache.hadoop.ozone.om.OmSnapshotManager;
import org.apache.hadoop.ozone.om.helpers.SnapshotInfo;
-import org.apache.hadoop.ozone.om.response.CleanupTableInfo;
import org.apache.hadoop.ozone.om.response.OMClientResponse;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager.WritableOmSnapshotLocalDataProvider;
import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos.OMResponse;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
/**
* Response for OMSnapshotPurgeRequest.
*/
-@CleanupTableInfo(cleanupTables = {SNAPSHOT_INFO_TABLE})
public class OMSnapshotPurgeResponse extends OMClientResponse {
- private static final Logger LOG =
Review Comment:
nit: please leave the logger and its imports unchanged, since removing them is unrelated to removing `CleanupTableInfo`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4180436303
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/snapshot/OMSnapshotPurgeResponse.java:
##########
@@ -30,21 +28,15 @@
import org.apache.hadoop.ozone.om.OmMetadataManagerImpl;
import org.apache.hadoop.ozone.om.OmSnapshotManager;
import org.apache.hadoop.ozone.om.helpers.SnapshotInfo;
-import org.apache.hadoop.ozone.om.response.CleanupTableInfo;
import org.apache.hadoop.ozone.om.response.OMClientResponse;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager.WritableOmSnapshotLocalDataProvider;
import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos.OMResponse;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
/**
* Response for OMSnapshotPurgeRequest.
*/
-@CleanupTableInfo(cleanupTables = {SNAPSHOT_INFO_TABLE})
public class OMSnapshotPurgeResponse extends OMClientResponse {
- private static final Logger LOG =
Review Comment:
Unused LOG will fail PMD, tried to do it, see https://github.com/apache/ozone/actions/runs/37257723571/job/111598362211 , so we need to remove it in this patch.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4180436303
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/snapshot/OMSnapshotPurgeResponse.java:
##########
@@ -30,21 +28,15 @@
import org.apache.hadoop.ozone.om.OmMetadataManagerImpl;
import org.apache.hadoop.ozone.om.OmSnapshotManager;
import org.apache.hadoop.ozone.om.helpers.SnapshotInfo;
-import org.apache.hadoop.ozone.om.response.CleanupTableInfo;
import org.apache.hadoop.ozone.om.response.OMClientResponse;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager.WritableOmSnapshotLocalDataProvider;
import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos.OMResponse;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
/**
* Response for OMSnapshotPurgeRequest.
*/
-@CleanupTableInfo(cleanupTables = {SNAPSHOT_INFO_TABLE})
public class OMSnapshotPurgeResponse extends OMClientResponse {
- private static final Logger LOG =
Review Comment:
Unused LOG will fail PMD, tried to do it, see https://github.com/apache/ozone/actions/runs/37257723571/job/111598362211
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4180435926
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/S3SecretManager.java:
##########
@@ -102,6 +105,7 @@ default void updateCache(String accessId, S3SecretValue secret) {
if (cache != null) {
LOG.info("Updating cache for accessId/user: {}.", accessId);
cache.put(accessId, secret);
+ TableCacheUpdateTracker.recordCacheUpdate(S3_SECRET_TABLE);
Review Comment:
The `S3SecretManager` uses table cache, but the implementation does not use the unified `TypedTable`, probably because it supports both external S3 secret store (i.e. `VaultSecretStore`) and embedded (OM RocksDB), but Ozone table mechanisms only support RocksDB (`TypedTable` uses `RDBTable` as the underlying store).
There is also cache related cleanup logic in `OzoneManagerDoubleBuffer` just for `S3_SECRET_TABLE` which I think it kind of hacky since the whole cache evictions has already been supported by the OM `TableCache`. Technically, it should be possible to unify it by making the `S3SecretCache` to be a `TableCache`, but this means that we might need to make OM to generalize the table cache and store implementation API (where the store can support other remote store like `VaultStore` or even things like remote KV store which means that OM only stores in-memory cache similar to QiHoo OM architecture, see https://github.com/apache/ozone/files/13347053/OM.-Qihoo.pdf), which is going to be quite involved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "szetszwo (via GitHub)" <gi...@apache.org>.
szetszwo commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4167633590
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/S3SecretManager.java:
##########
@@ -102,6 +105,7 @@ default void updateCache(String accessId, S3SecretValue secret) {
if (cache != null) {
LOG.info("Updating cache for accessId/user: {}.", accessId);
cache.put(accessId, secret);
+ TableCacheUpdateTracker.recordCacheUpdate(S3_SECRET_TABLE);
Review Comment:
Question: why track it here?
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/file/OMDirectoryCreateResponseWithFSO.java:
##########
@@ -71,7 +65,6 @@ public OMDirectoryCreateResponseWithFSO(@Nonnull OMResponse omResponse,
public OMDirectoryCreateResponseWithFSO(@Nonnull OMResponse omResponse,
@Nonnull Result result) {
Review Comment:
Let's remove the result parameter. (If no further change is needed, let's just merge this PR and fix this later.)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4180435926
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/S3SecretManager.java:
##########
@@ -102,6 +105,7 @@ default void updateCache(String accessId, S3SecretValue secret) {
if (cache != null) {
LOG.info("Updating cache for accessId/user: {}.", accessId);
cache.put(accessId, secret);
+ TableCacheUpdateTracker.recordCacheUpdate(S3_SECRET_TABLE);
Review Comment:
The `S3SecretManager` uses table cache, but the implementation does not use the unified `TypedTable`, probably because it supports both external S3 secret store (i.e. `VaultSecretStore`) and embedded (OM RocksDB), but Ozone table mechanisms only support RocksDB (`TypedTable` uses `RDBTable` as the underlying store).
There is also cache related cleanup logic in `OzoneManagerDoubleBuffer` just for `S3_SECRET_TABLE` which I think it kind of hacky since it has already been supported by the OM `TableCache`. Technically, it should be possible to unify it by making the `S3SecretCache` to be a `TableCache`, but this means that we might need to make OM to generalize the table cache and store implementation API (where the store can support other remote store like `VaultStore` or even things like remote KV store which means that OM only stores in-memory cache similar to QiHoo OM architecture, see https://github.com/apache/ozone/files/13347053/OM.-Qihoo.pdf), which is going to be quite involved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4180435926
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/S3SecretManager.java:
##########
@@ -102,6 +105,7 @@ default void updateCache(String accessId, S3SecretValue secret) {
if (cache != null) {
LOG.info("Updating cache for accessId/user: {}.", accessId);
cache.put(accessId, secret);
+ TableCacheUpdateTracker.recordCacheUpdate(S3_SECRET_TABLE);
Review Comment:
The `S3SecretManager` uses table cache, but the implementation does not use the unified `TypedTable`, probably because it supports both external S3 secret store (i.e. `VaultSecretStore`) and embedded (OM RocksDB).
There is also cache related cleanup logic in `OzoneManagerDoubleBuffer` just for `S3_SECRET_TABLE` which I think it kind of hacky since it has already been supported by the OM `TableCache`. Technically, it should be possible to unify it by making the `S3SecretCache` to be a `TableCache`, but this means that we might need to make OM to generalize the table cache and store implementation API (where the store can support other remote store like `VaultStore` or even things like remote KV store), which is going to be quite involved.
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/file/OMDirectoryCreateResponseWithFSO.java:
##########
@@ -71,7 +65,6 @@ public OMDirectoryCreateResponseWithFSO(@Nonnull OMResponse omResponse,
public OMDirectoryCreateResponseWithFSO(@Nonnull OMResponse omResponse,
@Nonnull Result result) {
Review Comment:
Updated since there is also another review to address.
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/snapshot/OMSnapshotPurgeResponse.java:
##########
@@ -30,21 +28,15 @@
import org.apache.hadoop.ozone.om.OmMetadataManagerImpl;
import org.apache.hadoop.ozone.om.OmSnapshotManager;
import org.apache.hadoop.ozone.om.helpers.SnapshotInfo;
-import org.apache.hadoop.ozone.om.response.CleanupTableInfo;
import org.apache.hadoop.ozone.om.response.OMClientResponse;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager.WritableOmSnapshotLocalDataProvider;
import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos.OMResponse;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
/**
* Response for OMSnapshotPurgeRequest.
*/
-@CleanupTableInfo(cleanupTables = {SNAPSHOT_INFO_TABLE})
public class OMSnapshotPurgeResponse extends OMClientResponse {
- private static final Logger LOG =
Review Comment:
Thanks, updated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "rich7420 (via GitHub)" <gi...@apache.org>.
rich7420 commented on PR #11365:
URL: https://github.com/apache/ozone/pull/11365#issuecomment-5969433978
@ivandika3 thanks for the patch! overall lg
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "rich7420 (via GitHub)" <gi...@apache.org>.
rich7420 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4181003098
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/response/snapshot/OMSnapshotPurgeResponse.java:
##########
@@ -30,21 +28,15 @@
import org.apache.hadoop.ozone.om.OmMetadataManagerImpl;
import org.apache.hadoop.ozone.om.OmSnapshotManager;
import org.apache.hadoop.ozone.om.helpers.SnapshotInfo;
-import org.apache.hadoop.ozone.om.response.CleanupTableInfo;
import org.apache.hadoop.ozone.om.response.OMClientResponse;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager;
import org.apache.hadoop.ozone.om.snapshot.OmSnapshotLocalDataManager.WritableOmSnapshotLocalDataProvider;
import org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos.OMResponse;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
/**
* Response for OMSnapshotPurgeRequest.
*/
-@CleanupTableInfo(cleanupTables = {SNAPSHOT_INFO_TABLE})
public class OMSnapshotPurgeResponse extends OMClientResponse {
- private static final Logger LOG =
Review Comment:
oh ok
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on PR #11365:
URL: https://github.com/apache/ozone/pull/11365#issuecomment-6007481491
Thanks @szetszwo @rich7420 for the reviews.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 merged PR #11365:
URL: https://github.com/apache/ozone/pull/11365
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org
Re: [PR] HDDS-16643. Remove CleanupTableInfo mechanism [ozone]
Posted by "ivandika3 (via GitHub)" <gi...@apache.org>.
ivandika3 commented on code in PR #11365:
URL: https://github.com/apache/ozone/pull/11365#discussion_r4180435926
##########
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/S3SecretManager.java:
##########
@@ -102,6 +105,7 @@ default void updateCache(String accessId, S3SecretValue secret) {
if (cache != null) {
LOG.info("Updating cache for accessId/user: {}.", accessId);
cache.put(accessId, secret);
+ TableCacheUpdateTracker.recordCacheUpdate(S3_SECRET_TABLE);
Review Comment:
The `S3SecretManager` uses table cache, but the implementation does not use the unified `TypedTable`, probably because it supports both external S3 secret store (i.e. `VaultSecretStore`) and embedded (OM RocksDB), but Ozone table mechanisms only support RocksDB (`TypedTable` uses `RDBTable` as the underlying store).
There is also cache related cleanup logic in `OzoneManagerDoubleBuffer` just for `S3_SECRET_TABLE` which I think it kind of hacky since it has already been supported by the OM `TableCache`. Technically, it should be possible to unify it by making the `S3SecretCache` to be a `TableCache`, but this means that we might need to make OM to generalize the table cache and store implementation API (where the store can support other remote store like `VaultStore` or even things like remote KV store), which is going to be quite involved.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org