[
https://issues.apache.org/jira/browse/HDDS-5338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hanisha Koneru resolved HDDS-5338.
----------------------------------
Resolution: Not A Problem
> Handle Bootstrap when original OM has non-ratis transactions
> ------------------------------------------------------------
>
> Key: HDDS-5338
> URL: https://issues.apache.org/jira/browse/HDDS-5338
> Project: Apache Ozone
> Issue Type: Sub-task
> Affects Versions: 1.2.0
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
>
> When non-Ratis OM is converted to ratis enabled OM, there could be
> transactions in the RocksDB which are not part of the Ratis logs. If the
> Ratis logs are not purged when a new OM is bootstrapped, it will just get all
> the Ratis logs from the old OM. The non-ratis transactions in the RocksDB
> will not be transferred to the new OM as Ratis will not know that there are
> transactions in the DB not present in the logs.
> So when a new OM is bootstrapping, we should check the DB for non-ratis
> transactions and if any are present, the new OM should download the DB from
> existing OM before the setConf request is sent out.
> Thanks [~bharat] for identifying this scenario
> [here|https://github.com/apache/ozone/pull/1494#issuecomment-859329558] .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
