[
https://issues.apache.org/jira/browse/HADOOP-18183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated HADOOP-18183:
--------------------------------
Hadoop Flags: Reviewed
Description:
we don't get the range of ranged get requests in s3 server logs, because the
AWS s3 log doesn't record that information. we can see it's a partial get from
the 206 response, but the length of data retrieved is lost.
LoggingAuditor.beforeExecution() would need to recognise a ranged GET and
determine the extra key-val pairs for range start and end (rs & re?)
we might need to modify {{HttpReferrerAuditHeader.buildHttpReferrer()}} to take
a map of <string, string> so it can dynamically create a header for each
request; currently that is not in there.
was:
we don't get the range of ranged get requests in s3 server logs, because the
AWS s3 log doesn't record that information. we can see it's a partial get from
the 206 response, but the length of data retrieved is lost.
LoggingAuditor.beforeExecution() would need to recognise a ranged GET and
determine the extra key-val pairs for range start and end (rs & re?)
we might need to modify {{HttpReferrerAuditHeader.buildHttpReferrer()}} to take
a map of <string, string> so it can dynamically create a header for each
request; currently that is not in there.
> s3a audit logs to publish range start/end of GET requests in audit header
> -------------------------------------------------------------------------
>
> Key: HADOOP-18183
> URL: https://issues.apache.org/jira/browse/HADOOP-18183
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.2
> Reporter: Steve Loughran
> Assignee: Ankit Saurabh
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.9
>
>
> we don't get the range of ranged get requests in s3 server logs, because the
> AWS s3 log doesn't record that information. we can see it's a partial get
> from the 206 response, but the length of data retrieved is lost.
> LoggingAuditor.beforeExecution() would need to recognise a ranged GET and
> determine the extra key-val pairs for range start and end (rs & re?)
> we might need to modify {{HttpReferrerAuditHeader.buildHttpReferrer()}} to
> take a map of <string, string> so it can dynamically create a header for each
> request; currently that is not in there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
