hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Chansler (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4422) S3 file systems should not create bucket
Date Tue, 03 Mar 2009 01:53:58 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Chansler updated HADOOP-4422:
------------------------------------

    Release Note: Modified Hadoop file system to no longer create S3 buckets. Applications
can create buckets for their S3 file systems by other means, for example, using the JetS3t
API.  (was: S3 buckets are no longer created by the Hadoop filesystem. Applications that relied
on this behavior should be changed to create buckets for their S3 filesystems by some other
means (e.g. the JetS3t API).)
    Hadoop Flags: [Incompatible change, Reviewed]  (was: [Reviewed, Incompatible change])

Edit release note for publication.

> S3 file systems should not create bucket
> ----------------------------------------
>
>                 Key: HADOOP-4422
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4422
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.18.1
>            Reporter: David Phillips
>            Assignee: David Phillips
>             Fix For: 0.20.0
>
>         Attachments: hadoop-s3n-nocreate.patch, hadoop-s3n-nocreate.patch
>
>
> Both S3 file systems (s3 and s3n) try to create the bucket at every initialization. 
This is bad because
> * Every S3 operation costs money.  These unnecessary calls are an unnecessary expense.
> * These calls can fail when called concurrently.  This makes the file system unusable
in large jobs.
> * Any operation, such as a "fs -ls", creates a bucket.  This is counter-intuitive and
undesirable.
> The initialization code should assume the bucket exists:
> * Creating a bucket is a very rare operation.  Accounts are limited to 100 buckets.
> * Any check at initialization for bucket existence is a waste of money.
> Per Amazon: "Because bucket operations work against a centralized, global resource space,
it is not appropriate to make bucket create or delete calls on the high availability code
path of your application. It is better to create or delete buckets in a separate initialization
or setup routine that you run less often."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message