[
https://issues.apache.org/jira/browse/HDDS-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-121:
----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues
targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted
for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> Issue with change of configuration ozone.metastore.impl in SCM
> --------------------------------------------------------------
>
> Key: HDDS-121
> URL: https://issues.apache.org/jira/browse/HDDS-121
> Project: Apache Ozone
> 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: [email protected]
For additional commands, e-mail: [email protected]
