Details
-
Sub-task
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
Following up on the discussion on HADOOP-13345, 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.
Attachments
Attachments
Issue Links
- is related to
-
HADOOP-14468 S3Guard: make short-circuit getFileStatus() configurable
- Resolved