XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.7.0
    • Fix Version/s: None
    • Component/s: fs/s3
    • Labels:
      None
    • Environment:

      Hadoop on AWS

    • Target Version/s:

      Description

      Amazon S3 uses, by default, the NORMAL_STORAGE class for s3 objects.
      This offers, according to Amazon's material, 99.99999999% reliability.
      For many applications, however, the 99.99% reliability offered by the REDUCED_REDUNDANCY storage class is amply sufficient, and comes with a significant cost saving.

      HDFS, when using the legacy s3n protocol, or the new s3a scheme, should support overriding the default storage class of created s3 objects so that users can take advantage of this cost benefit.

      This would require minor changes of the s3n and s3a drivers, using
      a configuration property fs.s3n.storage.class to override the default storage when desirable.

      This override could be implemented in Jets3tNativeFileSystemStore with:
      S3Object object = new S3Object(key);
      ...
      if(storageClass!=null) object.setStorageClass(storageClass);

      It would take a more complex form in s3a, e.g. setting:
      InitiateMultipartUploadRequest initiateMPURequest =
      new InitiateMultipartUploadRequest(bucket, key, om);
      if(storageClass !=null )

      { initiateMPURequest = initiateMPURequest.withStorageClass(storageClass); }

      and similar statements in various places.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ylandrin Yann Landrin-Schweitzer
              • Votes:
                1 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: