You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Bharat Viswanadham (JIRA)" <ji...@apache.org> on 2018/05/24 23:54:00 UTC
[jira] [Created] (HDDS-121) Issue with change of configuration
ozone.metastore.impl in SCM
Bharat Viswanadham created HDDS-121:
---------------------------------------
Summary: 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
BTake 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org