[
https://issues.apache.org/jira/browse/HADOOP-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032925#comment-16032925
]
Steve Loughran commented on HADOOP-14467:
-----------------------------------------
bq. Should we have a top-level S3A cwiki page that the site docs link to?
Can do, though there the nice thing is we can update the wiki as it goes along
bq. When should things live in the site docs versus wiki?
Wiki has proven useful for a consistent URL across versions, whereas a URL in
the code to a docs ref would be a maintenance mess. And we get to update it on
a whim. The big limitation is the need to be cross-version in what you explain;
for things like network errors this is trivial, "ConnectionRefused" never
changes. Here we may need to say "if using s3guard....".
I've proposed doing a wiki link on BadAuth, incidentally; we should probably do
one for 301 moved, as that usually means "wrong endpoint"
> 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]
