[
https://issues.apache.org/jira/browse/HDDS-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-11539:
-------------------------------
Description:
While working on HDDS-10390, it is found that OzoneClientCache @PreDestroy hook
is never called, causing the OzoneClientCache client instance to not be reset,
causing S3G to use the same client (pointing to the same OM) even if the
MiniOzoneCluster is rebuilt. Currently, a workaround is to explicitly call
OzoneClientCache#closeClient in the MiniOzoneCluster setup.
Need to fix this and remove the workaround.
was:While working on HDDS-10390, it is found that OzoneClientCache
@PreDestroy hook is never called, causing the OzoneClientCache client instance
to not be reset. Currently, a workaround is to explicitly call
OzoneClientCache#closeClient in the integration.
> OzoneClientCache @PreDestroy is never called
> --------------------------------------------
>
> Key: HDDS-11539
> URL: https://issues.apache.org/jira/browse/HDDS-11539
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Ivan Andika
> Priority: Major
>
> While working on HDDS-10390, it is found that OzoneClientCache @PreDestroy
> hook is never called, causing the OzoneClientCache client instance to not be
> reset, causing S3G to use the same client (pointing to the same OM) even if
> the MiniOzoneCluster is rebuilt. Currently, a workaround is to explicitly
> call OzoneClientCache#closeClient in the MiniOzoneCluster setup.
> Need to fix this and remove the workaround.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
