[
https://issues.apache.org/jira/browse/HADOOP-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032926#comment-16032926
]
Steve Loughran edited comment on HADOOP-14467 at 6/1/17 12:50 PM:
------------------------------------------------------------------
+regarding state, easy to add a counter to the stream "opened count" (if we
aren't already tracking that), and treat an open failure if count==0 as
different from the rest
was (Author: [email protected]):
+regarding state, easy to add a flag to the stream "opened count" (if we aren't
already tracking that), and treat an open failure if count==0 as different from
the rest
> 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
>
> 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.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
