[jira] [Created] (HDFS-2316) webhdfs: a complete FileSystem implementation for accessing HDFS over HTTP

webhdfs: a complete FileSystem implementation for accessing HDFS over HTTP -- Key: HDFS-2316 URL: https://issues.apache.org/jira/browse/HDFS-2316 Project: Hadoop HDFS Is

[jira] [Created] (HDFS-2317) Read access to HDFS using HTTP REST

Read access to HDFS using HTTP REST --- Key: HDFS-2317 URL: https://issues.apache.org/jira/browse/HDFS-2317 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Tsz Wo (Nicholas), SZE As

[jira] [Created] (HDFS-2318) Provide authentication to webhdfs using SPNEGO

Provide authentication to webhdfs using SPNEGO -- Key: HDFS-2318 URL: https://issues.apache.org/jira/browse/HDFS-2318 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Tsz Wo (Nichola

[jira] [Created] (HDFS-2319) Add test cases for FSshell -stat

Add test cases for FSshell -stat Key: HDFS-2319 URL: https://issues.apache.org/jira/browse/HDFS-2319 Project: Hadoop HDFS Issue Type: Test Components: test Affects Versions: 0.24.0 R

Hadoop-Hdfs-22-branch - Build # 82 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-22-branch/82/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 1944 lines...] signanddeploy: simpledeploy: [artifact

Re: questions regarding fuse_dfs_read

Hi Aastha, A read-ahead buffer is a common technique to trade higher bandwidth for lower latency for a number of common read patterns. Your OS does something similar (a much more advanced technique though). By reading ahead, HDFS is betting that your reads have a pattern to it. I think the 1

Hadoop-Hdfs-trunk - Build # 786 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/786/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 6835 lines...] main: [copy] Copying 15 files to /ho

[jira] [Created] (HDFS-2320) Make merged protocol changes from 0.20-append to 0.20-security compatible with previous releases.

Make merged protocol changes from 0.20-append to 0.20-security compatible with previous releases. - Key: HDFS-2320 URL: https://issues.apache.org/jira/browse/HDFS-2320

[jira] [Created] (HDFS-2321) HDFS Build failure due to unresolved commons.daemon.os.name & commons.daemon.os.arch properties in Windows 7

HDFS Build failure due to unresolved commons.daemon.os.name & commons.daemon.os.arch properties in Windows 7 Key: HDFS-2321 URL: https://issues.apache.org

Merging trunk, 0.23.0, HA?

Hey all, I'm trying to reconcile some of the recent changes in trunk, HA, and 0.23. In particular, I'm hoping to merge HDFS-2197 back into both of those branches. If we don't perform this merge, then any modification to the RPC methods in the NameNode will require manual re-application. At this p

Re: Merging trunk, 0.23.0, HA?

Assuming this is OK, I have a candidate merge here: https://github.com/toddlipcon/hadoop-common/tree/hdfs-1623-merged-trunk-20110907 This carries over Suresh's changes from HDFS-1974 into the refactored NameNodeRpcServer. Thanks, -Todd On Wed, Sep 7, 2011 at 3:03 PM, Todd Lipcon wrote:

Re: Merging trunk, 0.23.0, HA?

On Wed, Sep 7, 2011 at 3:03 PM, Todd Lipcon wrote: > At this point, I'm thinking of doing the following: > - merge all of the recent trunk commits into HA branch > - cherry-pick just this commit from trunk into 0.23. > +1, this seems to me like the appropriate way to go. Thanks a lot for volunte

Re: Merging trunk, 0.23.0, HA?

On Wed, Sep 7, 2011 at 3:03 PM, Todd Lipcon wrote: > Hey all, > > I'm trying to reconcile some of the recent changes in trunk, HA, and > 0.23. In particular, I'm hoping to merge HDFS-2197 back into both of > those branches. If we don't perform this merge, then any modification > to the RPC methods

Re: Merging trunk, 0.23.0, HA?

+1 Todd.

Re: Merging trunk, 0.23.0, HA?

Tests passed, so I committed this merge to the HA branch. Sometimes the git mirror is slow in picking up these merges until the next non-merge commit happens on the branch. If it hasn't picked it up in a few hours, I'll do some kind of no-op commit to kick the git mirror :) -Todd On Wed, Sep 7, 2