[jira] [Resolved] (HDDS-122) Issue with change of configuration ozone.metastore.impl in KSM
[ https://issues.apache.org/jira/browse/HDDS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anu Engineer resolved HDDS-122. --- Resolution: Fixed Removed LevelDB :). Fixed. > Issue with change of configuration ozone.metastore.impl in KSM > --- > > Key: HDDS-122 > URL: https://issues.apache.org/jira/browse/HDDS-122 > 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 KSM DB with a new DB type. With this, we will > lose all the information. > > To avoid this kind of scenario, when we start KSM, we need to persist the DB > used for KSM 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-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Resolved] (HDDS-122) Issue with change of configuration ozone.metastore.impl in KSM
[ https://issues.apache.org/jira/browse/HDDS-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hanisha Koneru resolved HDDS-122. - Resolution: Fixed Resolving this as it is a duplicate of HDDS-121. > Issue with change of configuration ozone.metastore.impl in KSM > --- > > Key: HDDS-122 > URL: https://issues.apache.org/jira/browse/HDDS-122 > 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 KSM DB with a new DB type. With this, we will > lose all the information. > > To avoid this kind of scenario, when we start KSM, we need to persist the DB > used for KSM 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-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
