You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Sammi Chen (Jira)" <ji...@apache.org> on 2020/06/22 07:19:00 UTC
[jira] [Commented] (HDDS-3486) Recon cannot track missing
containers that were created and went missing while it is down.
[ https://issues.apache.org/jira/browse/HDDS-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141753#comment-17141753 ]
Sammi Chen commented on HDDS-3486:
----------------------------------
Hi [~vivekratnavel] and [~avijayan], do you plan to fix this issue recently, before 0.6.0 release?
> 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: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org