Re: Minutes: Hadoop Contributor Meeting 05/06/2010

2010-05-07 Thread Tom White
Here's my (single) slide about the 0.21 release.

Tom

On Thu, May 6, 2010 at 5:38 PM, Arun C Murthy  wrote:
> # Shared goals
>  - Hadoop is HDFS & Map-Reduce in this context of this set of slides
> # Priorities
>  * Yahoo
>    - Correctness
>    - Availability: Not the same as high-availability (6 9s. etc.) i.e. SPOFs
>    - API Compatibility
>    - Scalability
>    - Operability
>    - Performance
>    - Innovation
>  * Cloudera
>    - Test coverage, api coverage
>    - APL Licensed codec (lzo replacement)
>    - Security
>    - Wire compatibility
>    - Cluster-wide resource availability
>    - New apis (FileContext, MR Context Objs.), documentation of their
> advantages
>    - HDFS to better support non-MR use-cases
>    - Cluster metrics hooks
>    - MR modularity (package)
>  * Facebook
>    - Correctness
>    - Availability, High Availability, Failover, Continuous Availability
>    - Scalability
> # Bar for patches/features keeps going higher as the project matures
>  - Build consensus (e.g. Python Enhancement Process, JSR etc.)
>  - Run/test on your own to prove the concept/feature or branch and finish
>  - Early versions of libraries should be started outside of the project
> (github etc.) e.g. input-formats, compression-codecs etc.
>    - github for all the above
>    - Prune contrib
> # Maven for packaging
> # Tom: hadoop-0.21 (Tom - can you please post your slides? Thanks!)
> # Owen: Release Manager (see slides)
> # Agenda for next meeting
>  - Eli: Hadoop Enhancement Process (modelled on PEP?)
>  - Branching strategies: Development Models
>
> Arun
>
>
>
>
>


[jira] Created: (HDFS-1135) Please sort the various options alphabetically in the output of "hadoop fs -help"

2010-05-07 Thread Milind Bhandarkar (JIRA)
Please sort the various options alphabetically in the output of "hadoop fs 
-help"
-

 Key: HDFS-1135
 URL: https://issues.apache.org/jira/browse/HDFS-1135
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: scripts
Affects Versions: 0.20.2
 Environment: All
Reporter: Milind Bhandarkar
Assignee: Robert Chansler
Priority: Minor
 Fix For: 0.20.3


The help message printed by "hadoop -fs help" has gotten too big. To make it 
easy to locate options for a particular command is a painful task. Please sort 
the options alphabetically, so that it is easy to locate help for particular 
commands.

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



[jira] Created: (HDFS-1136) FileChecksumServlets.RedirectServlet doesn't carry forward the delegation token

2010-05-07 Thread Boris Shkolnik (JIRA)
 FileChecksumServlets.RedirectServlet doesn't carry forward the delegation token


 Key: HDFS-1136
 URL: https://issues.apache.org/jira/browse/HDFS-1136
 Project: Hadoop HDFS
  Issue Type: Bug
Reporter: Boris Shkolnik


 FileChecksumServlets.RedirectServlet doesn't carry forward the delegation 
token in the redircted URL when redirecting to a random data node to get 
checksum
from there

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



[jira] Created: (HDFS-1137) Name node is using the write-ahead log improperly

2010-05-07 Thread Benjamin Reed (JIRA)
Name node is using the write-ahead log improperly
-

 Key: HDFS-1137
 URL: https://issues.apache.org/jira/browse/HDFS-1137
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: name-node
Reporter: Benjamin Reed


The Name node is doing the write-ahead log (WAL) (aka edit log) improperly. 
Usually when using WAL, changes are written to the log before they are applied 
to the state. Currently the Namenode does the WAL after applying the change. 
This means that read may see changes before they are durable. A client may read 
information and the server fail before the information is written to the WAL, 
which results in the client reading state that disappears. To fix the Namenode 
should write changes before (aka ahead of) applying the change.

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