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

ASF GitHub Bot updated HDDS-10855:
----------------------------------
    Labels: pull-request-available  (was: )

> Handle Null ParentKeyInfo Error in Recon Namespace Summary Task
> ---------------------------------------------------------------
>
>                 Key: HDDS-10855
>                 URL: https://issues.apache.org/jira/browse/HDDS-10855
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Recon
>    Affects Versions: 1.5.0
>            Reporter: Mohammad Arafat Khan
>            Priority: Critical
>              Labels: pull-request-available
>
> Address the IOException encountered during Namespace Summary task processing 
> in Recon
>  
> Recon log
> {code:java}
> ERROR 
> [pool-51-thread-1]-org.apache.hadoop.ozone.recon.tasks.NSSummaryTaskWithLegacy:
>  Unable to process Namespace Summary data in Recon DB. 
> java.io.IOException: ParentKeyInfo for NSSummaryTaskWithLegacy is null
>     at 
> org.apache.hadoop.ozone.recon.tasks.NSSummaryTaskWithLegacy.setKeyParentID(NSSummaryTaskWithLegacy.java:299)
>     at 
> org.apache.hadoop.ozone.recon.tasks.NSSummaryTaskWithLegacy.processWithLegacy(NSSummaryTaskWithLegacy.java:118)
>     at 
> org.apache.hadoop.ozone.recon.tasks.NSSummaryTask.process(NSSummaryTask.java:99)
>     at 
> org.apache.hadoop.ozone.recon.tasks.ReconTaskControllerImpl.lambda$consumeOMEvents$1(ReconTaskControllerImpl.java:127)
>     at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
>     at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>     at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>     at java.base/java.lang.Thread.run(Thread.java:834) {code}



--
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