[ 
https://issues.apache.org/jira/browse/HDDS-9646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Doroszlai updated HDDS-9646:
-----------------------------------
    Affects Version/s: 1.4.0

> Unknown container from datanode in Recon
> ----------------------------------------
>
>                 Key: HDDS-9646
>                 URL: https://issues.apache.org/jira/browse/HDDS-9646
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Recon
>    Affects Versions: 1.4.0
>            Reporter: Sadanand Shenoy
>            Assignee: Sadanand Shenoy
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> It appears that the datanode contains container unknown to Recon. 
> ozone-recon.log:
> :
> {code:java}
> 2023-09-26 21:20:17,156 ERROR 
> [FixedThreadPoolWithAffinityExecutor-8-0]-org.apache.hadoop.hdds.scm.container.ContainerReportHandler:
>  Received container report for an unknown container 5518 from datanode 
> c3acac81-a55d-49f5-9928-6ad84af0a696 {code}
> This 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to