[
https://issues.apache.org/jira/browse/HADOOP-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-17470.
-------------------------------------
Fix Version/s: 3.3.2
Assignee: Steve Loughran
Resolution: Fixed
The S3A auditing code added tracking of every single FS API call. That should
be enough for now
> Collect more S3A IOStatistics
> -----------------------------
>
> Key: HADOOP-17470
> URL: https://issues.apache.org/jira/browse/HADOOP-17470
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Fix For: 3.3.2
>
>
> collect more stats of
> * how long FS API calls are taking
> * what is going wrong
> API
> * Duration of rename(), delete() other common API Calls.
> * openFile: how long the open operation is taking, split of open and openfile
> * time to initialize FS instance (maybe better in FileSystem.cache?)
> * create: Time to complete the create checks
> * finishedWrite: time to execute finishedWrite operations (which may include
> bulk deletes)
> Failure tracking: what failures are we seeing as counters
> Interrupts, connections, auth failures:
> This would be done in S3ARetryPolicy with an IOStatisticsStore passed in.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
