You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Nandakumar (Jira)" <ji...@apache.org> on 2022/12/22 08:43:00 UTC

[jira] [Resolved] (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:all-tabpanel ]

Nandakumar resolved HDDS-3486.
------------------------------
    Fix Version/s: 1.4.0
       Resolution: Fixed

> 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
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> 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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org