[HDDS-122] Issue with change of configuration ozone.metastore.impl in KSM

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Bharat Viswanadham
• Reporter: Bharat Viswanadham
• Created: 24/May/18 23:53
• Updated: 19/Sep/18 17:07
• Resolved: 19/Sep/18 17:07

Description

Take a scenario:

1. When we started ozone cluster, I have set ozone.metastore.impl to RocksDB.
2. Later I have stopped ozone cluster. 
3. 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.

 

Issue Links

• is a clone of: HDDS-121 Issue with change of configuration ozone.metastore.impl in SCM
• is related to: HDDS-121 Issue with change of configuration ozone.metastore.impl in SCM