[jira] [Commented] (HDFS-11903) Ozone: Cleaning up local storage when closing MiniOzoneCluster

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDFS-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450681#comment-16450681 ] 

Hudson commented on HDFS-11903:
-------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14057 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14057/])
HDFS-11903. Ozone: Cleaning up local storage when closing (liuml07: rev 9e2873db29f763b46f06a05692679c81c81797d1)
* (edit) hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/ozone/MiniOzoneCluster.java


> Ozone: Cleaning up local storage when closing MiniOzoneCluster
> --------------------------------------------------------------
>
>                 Key: HDFS-11903
>                 URL: https://issues.apache.org/jira/browse/HDFS-11903
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Mingliang Liu
>            Assignee: Mingliang Liu
>            Priority: Major
>             Fix For: HDFS-7240
>
>         Attachments: HDFS-11903-HDFS-7240.000.patch
>
>
> Currently we don't delete the local storage when closing {{MiniOzoneCluster}}, which will cause creating volume with the same name to fail, even in a new JVM process. Let's delete the local storage files: {{/tmp/ozone/metadata.db}} and {{/tmp/ozone/user.db}} when closing.
> Please note this is not a complete solution. As the {{OzoneMetadataManager}}  currently is a singleton, we are not able to create two independent MiniOzoneCluster in a single JVM. Data maybe shared unexpectedly. Let's address that in another JIRA, if needed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org