[
https://issues.apache.org/jira/browse/HADOOP-17511?focusedWorklogId=553696&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-553696
]
ASF GitHub Bot logged work on HADOOP-17511:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 17/Feb/21 16:00
Start Date: 17/Feb/21 16:00
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #2675:
URL: https://github.com/apache/hadoop/pull/2675#issuecomment-780659540
Latest PR moves the prepareRequest() callback of the active span into the
AWS SDK.
HEAD^ does it in the request factory construction -that's still supported,
but if we can keep the AWS SDK wiring -that will be better
* guarantee of being invoked on all S3 operations, even those done in the
client during startup
* means we get audit/log of calls like doesBucketExistV2 without us
reimplementing them
* means we can simplify the work I've just done regarding marking
operations as OnceRaw and walking up/down the callstack
But: this does mean we need to solve the problem of endpoints and regions
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 553696)
Time Spent: 6.5h (was: 6h 20m)
> Add an Audit plugin point for S3A auditing/context
> --------------------------------------------------
>
> Key: HADOOP-17511
> URL: https://issues.apache.org/jira/browse/HADOOP-17511
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 3.3.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 6.5h
> Remaining Estimate: 0h
>
> Add a way for auditing tools to correlate S3 object calls with Hadoop FS API
> calls.
> Initially just to log/forward to an auditing service.
> Later: let us attach them as parameters in S3 requests, such as opentrace
> headeers or (my initial idea: http referrer header -where it will get into
> the log)
> Challenges
> * ensuring the audit span is created for every public entry point. That will
> have to include those used in s3guard tools, some defacto public APIs
> * and not re-entered for active spans. s3A code must not call back into the
> FS API points
> * Propagation across worker threads
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
