[
https://issues.apache.org/jira/browse/HADOOP-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032075#comment-16032075
]
Aaron Fabbri commented on HADOOP-14467:
---------------------------------------
{quote}I think we should add a wiki entry pointing to a (new) hadoop cwiki
entry.
{quote}
I'm happy to do that. Couple of noob questions: Should we have a top-level S3A
cwiki page that the site docs link to? When should things live in the site
docs versus wiki?
{quote}
maybe also the input stream could differentiate from "never opened the file"
from "opened, it was there, now it isnt". which can happen if someone deletes
it during the read process
{quote}
Makes sense. I'll look at the code and think about this. Usually I'd handle
this by passing around a request context object that keeps bits of state
associated with an operation.
> 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]
