You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Bharat Viswanadham (Jira)" <ji...@apache.org> on 2020/10/08 19:00:00 UTC
[jira] [Commented] (HDDS-4327) Potential resource leakage using
BatchOperation
[ https://issues.apache.org/jira/browse/HDDS-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210393#comment-17210393 ]
Bharat Viswanadham commented on HDDS-4327:
------------------------------------------
[~weichiu]
Are there any places in code you have observed that batch is not called within try enclosed resource?
Because in OM we use this, and we have used as
{code:java}
try(BatchOperation batchOperation = omMetadataManager.getStore()
.initBatchOperation())
{code}
> Potential resource leakage using BatchOperation
> -----------------------------------------------
>
> Key: HDDS-4327
> URL: https://issues.apache.org/jira/browse/HDDS-4327
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Wei-Chiu Chuang
> Priority: Major
>
> there are a number of places in the code where BatchOperation is used but not closed. As a best practice, better to close them explicitly.
> I have a stress test code that uses BatchOperation to insert into OM rocksdb. Without closing BatchOperation explicitly, the process crashes after just a few minutes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org