[
https://issues.apache.org/jira/browse/HDFS-11903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16030272#comment-16030272
]
Anu Engineer commented on HDFS-11903:
-------------------------------------
[~liuml07] It is pretty easy to make it support different locations, you can
create a new path ID(say a UUID) and append it to the current path. That way
you can create multiple MiniOzoneClusters if needed. We have not yet run into
the need to create multiple MiniOzoneClusters yet. Hence the current design.
> 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
> 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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
