[
https://issues.apache.org/jira/browse/HDDS-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142339#comment-17142339
]
Aravindan Vijayan commented on HDDS-3486:
-----------------------------------------
[~Sammi] The solution involves bootstrapping the Recon SCM DB with the actual
SCM DB when it starts up. This has already been done with the OM DB, and hence
that can be used as a reference. We plan to get to it in the next release
(0.7.0). If someone else on your end can take it up, that will be great as
well. Feel free to re-assign in that case. cc [~vivekratnavel]
> 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: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Recon
> Affects Versions: 0.6.0
> Reporter: Aravindan Vijayan
> Assignee: Vivek Ratnavel Subramanian
> Priority: Major
> Labels: TriagePending
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
