[
https://issues.apache.org/jira/browse/HDDS-11036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102677#comment-18102677
]
Devesh Kumar Singh edited comment on HDDS-11036 at 8/7/26 6:16 AM:
-------------------------------------------------------------------
Thanks [~echonesis]for visiting this JIRA. So as of today, If Recon crashes due
to any unexpected errors, on restart of Recon , it checks if last sequence
number fetched and applied to recon OM DB snapshot and lastupdatedSeq number
maintained for each recon OM tasks differs, then Recon reinitialize those Recon
OM tasks from already fetched and applied delta DB events to Recon OM DB
snapshot.
I think this JIRA may not hold ground now.
was (Author: JIRAUSER295411):
Thanks [~echonesis]for visiting this JIRA. So as of today, If Recon crashes due
to any unexpected errors, on restart of Recon , it checks if last sequence
number fetched and applied to recon OM DB snapshot and lastupdatedSeq number
maintained for each recon OM tasks differs, then Recon reinitialize those Recon
OM tasks from already fetched and applied delta DB events to Recon OM DB
snapshot.
> Ozone Recon Data Recovery Tool
> ------------------------------
>
> Key: HDDS-11036
> URL: https://issues.apache.org/jira/browse/HDDS-11036
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Recon
> Reporter: Devesh Kumar Singh
> Priority: Major
>
> Recon do periodic sync with OM to keep OM namespace metadata like keys,
> volumes, buckets up-to date and use it for various other tasks and derive
> data out of it using various tasks (ContainerKeyMapperTask, NSSummaryTask,
> OMDBInsightTask etc).
> If due to unexpected errors at OM or Recon , Recon may lag or OM namespace
> metadata may not be in sync either due to
> # RocksDB lock issues.
> # Recon has fetched OM DB snapshot since last sequence number, but before
> processing those incremental events (PUT, DELETE, UPDATE), if some unexpected
> error caused any processed or derived data failed to save in recon DB, Recon
> will not fetch that incremental data again and will not process those events
> again.
> In such cases, Recon should have a recovery tool to fetch the OM DB snapshot
> from last fetched sequence number and then explicitly process and run tasks
> on fetched events for Recon.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
