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

Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:35:09 UTC

[jira] [Updated] (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 ]

Ethan Rose updated HDDS-3486:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> 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: Prashant Pogde
>            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: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org