[
https://issues.apache.org/jira/browse/HDDS-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17629849#comment-17629849
]
Devesh Kumar Singh commented on HDDS-3486:
------------------------------------------
[~swagle], As per my understanding on current design and code, as
[~aswinshakil] mentioned {{ozone.recon.scm.container.threshold}} (Default =
100) is being used during Recon startup and if Container number diff between
SCM and Recon is greater than above threshold, then recon SCM rocks DB is
updated and sync with scm Rocks DB, however this is only at Recon startup,
after that Recon is only dependent on container reports from data nodes.
A part from above, there is another design point that SCM rocks DB doesn't get
updated with container data if "ozone.scm.ratis.enable" is set as true which is
default true and data flushes to SCM rocks DB when ratis snapshot is taken
which depends on "dfs.ratis.snapshot.threshold" value (default 10000), so even
if we want to do a periodic sync with SCM rocks DB, it will not give any info
except SCM Rocks DB is updated or flushed.
> Recon cannot track missing containers that were created and went missing
> while it is down.
> ------------------------------------------------------------------------------------------
>
> Key: HDDS-3486
> URL: https://issues.apache.org/jira/browse/HDDS-3486
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Recon
> Affects Versions: 1.0.0
> Reporter: Aravindan Vijayan
> Assignee: Devesh Kumar Singh
> Priority: Critical
>
> Since Recon relies on Container reports from DNs to track replicas, if a new
> container was created and went missing when Recon was down, it will not be
> able to tag it as a missing container.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
