Hemant Kumar created HDDS-8939:
----------------------------------

             Summary: isBlockLocationSame check should be skipped if object is 
not OmKeyInfo object
                 Key: HDDS-8939
                 URL: https://issues.apache.org/jira/browse/HDDS-8939
             Project: Apache Ozone
          Issue Type: Sub-task
            Reporter: Hemant Kumar


As part of [HDDS-8841|https://issues.apache.org/jira/browse/HDDS-8841], we 
added a check if block location is same for key object. Somehow 
*isBlockLocationSame* function is getting called for *non-OmKeyInfo* object. We 
should skip this check is object are not 
*OmKeyInfo* objects.


{code}2023-06-27 16:47:41,358 [snapshot-diff-job-thread-id-0] ERROR 
org.apache.hadoop.ozone.om.snapshot.SnapshotDiffManager: Caught unchecked 
exception during diff report generation for volume: pn5jtpqv bucket: buck1, 
fromSnapshot: snap1 and toSnapshot: snap2
java.lang.IllegalStateException: fromObject or toObject is not of OmKeyInfo
        at 
org.apache.hadoop.ozone.om.snapshot.SnapshotDiffManager.isBlockLocationSame(SnapshotDiffManager.java:1456)
        at 
org.apache.hadoop.ozone.om.snapshot.SnapshotDiffManager.generateDiffReport(SnapshotDiffManager.java:1377)
        at 
org.apache.hadoop.ozone.om.snapshot.SnapshotDiffManager.lambda$5(SnapshotDiffManager.java:959)
        at 
org.apache.hadoop.ozone.om.snapshot.SnapshotDiffManager.generateSnapshotDiffReport(SnapshotDiffManager.java:985)
        at 
org.apache.hadoop.ozone.om.snapshot.SnapshotDiffManager.lambda$1(SnapshotDiffManager.java:723)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
{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