You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2020/06/02 15:56:00 UTC
[jira] [Updated] (HDDS-121) Issue with change of configuration
ozone.metastore.impl in SCM
[ https://issues.apache.org/jira/browse/HDDS-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-121:
-------------------------------
Target Version/s: 0.7.0
Is this still an issue? I think we no longer support LevelDB. although we may support other storage engines in the future.
> Issue with change of configuration ozone.metastore.impl in SCM
> --------------------------------------------------------------
>
> Key: HDDS-121
> URL: https://issues.apache.org/jira/browse/HDDS-121
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
>
> Take a scenario:
> # When we started ozone cluster, I have set ozone.metastore.impl to RocksDB.
> # Later I have stopped ozone cluster.
> # Changed the configuration of ozone.metastore.impl to LevelDB
> Now, when we restart we create SCM container DB, node DB, delete blocks DB with a new db type. With this we will lose all the information.
>
> To avoid this kind of scenario, when we start SCM, we need to persist the DB used for SCM into a VersionFile, and use this. In this way with later restarts, if we have a version file, we read the dbType from Version file and use it for metadata store.
>
--
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