[
https://issues.apache.org/jira/browse/HDDS-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17915848#comment-17915848
]
Daniil commented on HDDS-11701:
-------------------------------
Hi [~sshenoy],
Have you made any progress on investigating this issue? It would be really
helpful if you could share any details or steps on how to reproduce the bug.
Additionally, could you provide more context on the origin of block
113750153638531250? It’s unclear where this block comes from and how it’s
supposed to be handled.
Thank you!
> Ozone chunkinfo displaying invalid file location for one of the EC block
> ------------------------------------------------------------------------
>
> Key: HDDS-11701
> URL: https://issues.apache.org/jira/browse/HDDS-11701
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Soumitra Sulav
> Assignee: Sadanand Shenoy
> Priority: Major
> Attachments: Screenshot 2024-11-14 at 6.05.22 PM.png
>
>
> The ChunkInfo command displays an EC Data Block which is invalid.
> !Screenshot 2024-11-14 at 6.05.22 PM.png!
> Block-ID 113750153638531250 should be available only on 1 DataNode as the
> other 2 are EMPTY Data Blocks and the size of the block is less than the
> stripe size i.e. 1MB.
> But in the chunkinfo console output, we can find that it shows 2 Data Blocks
> with their File locations.
> {code:java}
> jq '.[][][] | select(."Block-ID" == 113750153638531250 and ."Container-ID" ==
> 10004) | .["Locations"]'
> {
> "files": [],
> "pipelineID": "05a6b4e1-0a0a-45ee-896b-fcdac2fa7703",
> "chunkType": "DATA"
> }
> {
> "files": [
>
> "/data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block"
> ],
> "pipelineID": "05a6b4e1-0a0a-45ee-896b-fcdac2fa7703",
> "chunkType": "PARITY"
> }
> {
> "files": [
>
> "/data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block"
> ],
> "pipelineID": "05a6b4e1-0a0a-45ee-896b-fcdac2fa7703",
> "chunkType": "DATA"
> }
> {
> "files": [
>
> "/data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block"
> ],
> "pipelineID": "05a6b4e1-0a0a-45ee-896b-fcdac2fa7703",
> "chunkType": "DATA"
> }
> {
> "files": [
>
> "/data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block"
> ],
> "pipelineID": "05a6b4e1-0a0a-45ee-896b-fcdac2fa7703",
> "chunkType": "PARITY"
> }
> {code}
> Confirmed by running the list command on data nodes:
> {code:java}
> Data Blocks :
> [7] 18:14:27 [SUCCESS] DN_n
> -rw-r--r--. 1 hdfs hdfs 562816 Nov 11 22:38
> /data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block
> [2] 18:14:26 [FAILURE] DN_n Exited with error code 2
> Stderr: ls: cannot access
> '/data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block':
> No such file or directory
> [3] 18:14:27 [FAILURE] DN_n Exited with error code 2
> Stderr: ls: cannot access
> '/data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block':
> No such file or directory
> Parity Blocks :
> [11] 18:14:28 [SUCCESS] DN_n
> -rw-r--r--. 1 hdfs hdfs 562816 Nov 11 22:38
> /data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block
> [8] 18:14:27 [SUCCESS] DN_n
> -rw-r--r--. 1 hdfs hdfs 562816 Nov 11 22:38
> /data/1/hadoop-ozone/datanode/data/hdds/CID-28988b31-035a-40ab-be34-9656f4383542/current/containerDir19/10004/chunks/113750153638531255.block
> {code}
> Key Name : "/vol27323/buck27323-ec/10MB"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ozone.apache.org
For additional commands, e-mail: issues-h...@ozone.apache.org
