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

Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/12/21 08:39: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=17650357#comment-17650357 ] 

mingchao zhao commented on HDDS-3486:
-------------------------------------

Ozone 1.3.0 had been released and we currently have more than 600 open issues targeted for 1.3.0. I am moving the target field to 1.4.0.

If there is anything needs to be discussed about the Target Version, 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: Devesh Kumar Singh
>            Priority: Critical
>              Labels: pull-request-available
>
> 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