[
https://issues.apache.org/jira/browse/HDFS-17475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013569#comment-18013569
]
ASF GitHub Bot commented on HDFS-17475:
---------------------------------------
kokonguyen191 commented on PR #6745:
URL: https://github.com/apache/hadoop/pull/6745#issuecomment-3181996366
> Where do you feel this would be used. I don't think any service will add a
precheck for this, it adds an additional perf overhead in normal scenarios.
>
> If we want to handle such scenarios, The best is either catch an exception
in the service and handle (ignore/retry)
In our production cluster, it's most commonly used as a precheck before a
long running job (hours up to days) involving reading a lot of big files. It's
used to catch situations where failure happens a few hours into a job due to
missing blocks.
> Add a command to check if files are readable
> --------------------------------------------
>
> Key: HDFS-17475
> URL: https://issues.apache.org/jira/browse/HDFS-17475
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs
> Reporter: Felix N
> Assignee: Felix N
> Priority: Minor
> Labels: pull-request-available
>
> Sometimes a job can fail due to one unreadable file down the line due to
> missing replicas or dead DNs or other reason. This command should allow users
> to check whether files are readable by checking for metadata on DNs without
> executing full read pipelines of the files.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
