sadanand48 opened a new pull request, #5560: URL: https://github.com/apache/ozone/pull/5560
## What changes were proposed in this pull request? This issue can happen whenever there is a delay in container report of a container that belongs to a closed pipeline. Recon knows about pipeline state through the pipelineSync task that runs every 5 min. If a pipeline gets created and closed within 5 min, pipelineSync task in Recon gets an already CLOSED pipeline. Whenever a container pertaining to this pipeline is reported to Recon by the DN, it fails to add it in it's memory as there is a check present that prevents containers belonging to CLOSED pipelines. Recon also has a container sync task that periodically fetches containers from SCM to verify whether SCM & Recon are on the same page. The change here is to introduce a check to avoid checking pipeline state when SCM says it can do so during the container sync from as SCM can be considered the source of truth. This will not completely stop such logs from appearing but once the container sync task kicks in , the logs would disappear. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-9646 ## How was this patch tested? Manually. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
