Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-11694 Über-jira: S3a phase II: robustness, scale and performance
  3. HADOOP-14081

S3A: Consider avoiding array copy in S3ABlockOutputStream (ByteArrayBlock)

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • None
    • 2.8.0, 3.0.0-alpha4
    • fs/s3
    • None

    Description

      In S3ADataBlocks::ByteArrayBlock, data is copied whenever startUpload is called. It might be possible to directly access the byte[] array from ByteArrayOutputStream.

      Might have to extend ByteArrayOutputStream and create a method like getInputStream() which can return ByteArrayInputStream. This would avoid expensive array copy during large upload.

      Attachments

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. HADOOP-14028 S3A BlockOutputStreams doesn't delete temporary files in multipart uploads or handle part upload failures

        • Critical - Crashes, loss of data, severe memory leak.
        • Resolved

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

          People

            rajesh.balamohan Rajesh Balamohan Assign to me
            rajesh.balamohan Rajesh Balamohan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment