[jira] [Created] (HDFS-4535) port HDFS-1457 to branch-1.1

Xiaobo Peng created HDFS-4535: - Summary: port HDFS-1457 to branch-1.1 Key: HDFS-4535 URL: https://issues.apache.org/jira/browse/HDFS-4535 Project: Hadoop HDFS Issue Type: Bug Reporter

[jira] [Created] (HDFS-4534) Update rename for snapshots

Tsz Wo (Nicholas), SZE created HDFS-4534: Summary: Update rename for snapshots Key: HDFS-4534 URL: https://issues.apache.org/jira/browse/HDFS-4534 Project: Hadoop HDFS Issue Type: Sub

[jira] [Created] (HDFS-4533) start-dfs.sh ignored additional parameters besides -upgrade

Fengdong Yu created HDFS-4533: - Summary: start-dfs.sh ignored additional parameters besides -upgrade Key: HDFS-4533 URL: https://issues.apache.org/jira/browse/HDFS-4533 Project: Hadoop HDFS Issu

Re: VOTE: HDFS-347 merge

On Feb 20, 2013, at 5:12 PM, Aaron T. Myers wrote: > On Wed, Feb 20, 2013 at 4:29 PM, Chris Douglas wrote: > >> Given that HDFS-347 is a strictly better approach, once committed, >> there will be ample motivation to add support for other OSes and >> remove HDFS-2246 entirely. Nobody is confused

Re: VOTE: HDFS-347 merge

> > Suresh, if you're willing to "support and maintain" HDFS-2246, do you > have cycles to propose a patch to the HDFS-347 branch reintegrating > HDFS-2246 with the simplifications you outlined? In your review, did > you find anything else you'd like to address prior to the merge, or is > this the

Re: VOTE: HDFS-347 merge

Eli, you've sent the same email a half dozen times in the last ~24 hours. You might try a different tactic. Suresh, if you're willing to "support and maintain" HDFS-2246, do you have cycles to propose a patch to the HDFS-347 branch reintegrating HDFS-2246 with the simplifications you outlined? In

Re: VOTE: HDFS-347 merge

Hi Bikas, I completely agree with you in principle -- short circuit reads end up ceding control of the data path from the DataNode to the user applications. This has a few disadvantages which you've mentioned, and have been brought up in the JIRA as well: particularly QoS, metrics, the flexibility

[jira] [Resolved] (HDFS-4523) Fix INodeFile replacement, TestQuota and javac error

[ https://issues.apache.org/jira/browse/HDFS-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-4523. -- Resolution: Fixed Fix Version/s: Snapshot (HDFS-2802) Hadoop Flags: R

Re: VOTE: HDFS-347 merge

On Tue, Feb 26, 2013 at 11:35 AM, Suresh Srinivas wrote: >> >> >> I assume you mean in trunk? Given that ATM's proposal is to only >> remove HDFS-2246 from branch-2 once (a) we're confident in HDFS-347 >> and (b) adds Windows support, and we won't be releasing from trunk any >> time soon - from

RE: VOTE: HDFS-347 merge

Hi, In my opinion, this feature of short circuit reads (HDFS-347 or HDFS-2246) is not a desirable feature for HDFS. We should be working towards removing this feature instead of enhancing it and making it popular. Maybe short-circuit reads were something that HBase needed for performance at a poi

2.0.4-alpha bug-fix release

Hi Folks, Looks like I'll need to roll out a bug-fix 2.0.4-alpha release just to get other projects unblocked. FYI. Thanks for pointing this out Ted! thanks, Arun Begin forwarded message: > From: Siddharth Seth > Date: February 26, 2013 11:55:38 AM PST > To: "yarn-...@hadoop.apache.org" >

[jira] [Created] (HDFS-4532) RPC call queue may fill due to current user lookup

Daryn Sharp created HDFS-4532: - Summary: RPC call queue may fill due to current user lookup Key: HDFS-4532 URL: https://issues.apache.org/jira/browse/HDFS-4532 Project: Hadoop HDFS Issue Type: Bu

Re: VOTE: HDFS-347 merge

> > > I assume you mean in trunk? Given that ATM's proposal is to only > remove HDFS-2246 from branch-2 once (a) we're confident in HDFS-347 > and (b) adds Windows support, and we won't be releasing from trunk any > time soon - from a user perspective - HDFS-2246 will only be replaced > with HDFS

Re: VOTE: HDFS-347 merge

On Tue, Feb 26, 2013 at 9:33 AM, Suresh Srinivas wrote: >> >> >> There's no reason to maintain multiple implementations of the same >> feature, that's why per the 2246 jira it was proposed as a "good short >> term solution till HDFS-347 is completed". Why is ATM's compromise >> unacceptable? >>

Re: VOTE: HDFS-347 merge

> > > There's no reason to maintain multiple implementations of the same > feature, that's why per the 2246 jira it was proposed as a "good short > term solution till HDFS-347 is completed". Why is ATM's compromise > unacceptable? > We have already discussed this. Here is the recap: HDFS-347 do

Hadoop-Hdfs-trunk - Build # 1328 - Failure

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1328/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10803 lines...] Running org.apache.hadoop.fs.viewfs.TestV

Build failed in Jenkins: Hadoop-Hdfs-trunk #1328

See Changes: [sseth] YARN-365. Change NM heartbeat handling to not generate a scheduler event on each heartbeat. (Contributed by Xuan Gong) [atm] HADOOP-7487. DF should throw a more reasonable exception when mount cannot be determi

[jira] [Created] (HDFS-4531) Cover package org.apache.hadoop.yarn.webapp.hamlet with unit tests

Vadim Bondarev created HDFS-4531: Summary: Cover package org.apache.hadoop.yarn.webapp.hamlet with unit tests Key: HDFS-4531 URL: https://issues.apache.org/jira/browse/HDFS-4531 Project: Hadoop HDFS