Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.8.0
-
None
-
Reviewed
Description
against S3 (and other object stores), opening connections can be expensive, closing connections may be expensive (a sign of a regression).
S3A FS and individual input streams should have counters of the # of open/close/failure+reconnect operations, timers of how long things take. This can be used downstream to measure efficiency of the code (how often connections are being made), connection reliability, etc.
Attachments
Attachments
Issue Links
- breaks
-
HADOOP-13158 S3AFileSystem#toString might throw NullPointerException due to null cannedACL.
- Resolved
- contains
-
HADOOP-12844 Recover when S3A fails on IOException in read()
- Resolved
-
HADOOP-13047 S3a Forward seek in stream length to be configurable
- Resolved
-
HADOOP-13058 S3A FS fails during init against a read-only FS if multipart purge is enabled
- Resolved
- is related to
-
HADOOP-12949 Add HTrace to the s3a connector
- Resolved
-
HADOOP-13203 S3A: Support fadvise "random" mode for high performance readPositioned() reads
- Resolved
-
HADOOP-13065 Add a new interface for retrieving FS and FC Statistics
- Resolved
-
HADOOP-16241 S3AInputStream PositionReadable should perform ranged read on dedicated stream
- Open
- relates to
-
HADOOP-14862 Metrics for AdlFileSystem
- Resolved