You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Aaron Fabbri (JIRA)" <ji...@apache.org> on 2017/08/09 17:14:00 UTC
[jira] [Comment Edited] (HADOOP-14467) S3Guard: Improve FNFE
message when opening a stream
[ https://issues.apache.org/jira/browse/HADOOP-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120168#comment-16120168 ]
Aaron Fabbri edited comment on HADOOP-14467 at 8/9/17 5:13 PM:
---------------------------------------------------------------
I didn't find a nice clean way to add a new exception message that I liked here. At least now folks can google it. I feel like we could make more improvements as part of HADOOP-14468: we could report existence in S3 (if we checked), Metadata Store, etc.
was (Author: fabbri):
I didn't find a nice clean way to add a new exception message that I liked here. At least now folks can google it. I feel like we could make more improvements as part of HADOOP-14735: we could report existence in S3 (if we checked), Metadata Store, etc.
> S3Guard: Improve FNFE message when opening a stream
> ---------------------------------------------------
>
> Key: HADOOP-14467
> URL: https://issues.apache.org/jira/browse/HADOOP-14467
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Aaron Fabbri
> Assignee: Aaron Fabbri
> Priority: Minor
> Fix For: HADOOP-13345
>
> Attachments: HADOOP-14467-HADOOP-13345.001.patch
>
>
> Following up on the [discussion on HADOOP-13345|https://issues.apache.org/jira/browse/HADOOP-13345?focusedCommentId=16030050&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16030050], because S3Guard can serve getFileStatus() from the MetadataStore without doing a HEAD on S3, a FileNotFound error on a file due to S3 GET inconsistency does not happen on open(), but on the first read of the stream. We may add retries to the S3 client in the future, but for now we should have an exception message that indicates this may be due to inconsistency (assuming it isn't a more straightforward case like someone deleting the object out from under you).
> This is expected to be a rare case, since the S3 service is now mostly consistent for GET.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org