Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-18179 Boost S3A Stream Read Performance
  3. HADOOP-18183

s3a audit logs to publish range start/end of GET requests in audit header

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • 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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            sauraank Ankit Saurabh
            stevel@apache.org Steve Loughran
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment