You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Devesh Kumar Singh (Jira)" <ji...@apache.org> on 2022/11/24 07:51:00 UTC
[jira] [Commented] (HDDS-4539) Container Health Task should not run until Recon has reached steady state.
[ https://issues.apache.org/jira/browse/HDDS-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638154#comment-17638154 ]
Devesh Kumar Singh commented on HDDS-4539:
------------------------------------------
[~smeng] - What is the criteria of Recon becomes Ready ? I think we cannot wait till all DN becomes registered as there SCM or Recon will never know how many DNs old or new ones added/updated/deleted and Recon should wait for triggering its own tasks. I think this Jira is not correct, Recon is designed to be eventual consistent. Kindly provide your opinion.
cc: [~kkasawa]
> Container Health Task should not run until Recon has reached steady state.
> --------------------------------------------------------------------------
>
> Key: HDDS-4539
> URL: https://issues.apache.org/jira/browse/HDDS-4539
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Recon
> Reporter: Aravindan Vijayan
> Assignee: Devesh Kumar Singh
> Priority: Critical
>
> On a cluster with millions of containers or hundreds of Datanodes, it will take some time for Recon to reach a steady state (all active DNs and Containers reported). If the container health task is run before this, it can incorrectly flag most of the containers as missing. This was seen in a cluster where Recon reaching steady state is slow due to HDDS-4403, and it also leads to the UI problem mentioned in HDDS-4402.
> We need to make sure the container health task is not run before cluster has reached steady state. This could be a fixed wait time (~10mins) or by checking Recon's SCM state.
--
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