Build failed in Jenkins: Hadoop-Common-trunk #1025

See Changes: [arp] HDFS-5844. Fix broken link in WebHDFS.apt.vm (Contributed by Akira Ajisaka) [arp] HADOOP-10291. TestSecurityUtil#testSocketAddrWithIP fails due to test order dependency. (Contributed by Mit Desai) [sandy] YARN

Re: Re-swizzle 2.3

Mostly ready for a jira perspective. Committers - Henceforth, please use extreme caution while committing to branch-2.3. Please commit *only* blockers to 2.3. thanks, Arun On Jan 28, 2014, at 3:30 PM, Arun C Murthy wrote: > Fixing up stuff now, thanks to Andrew for volunteering to help with

regression in 2.4? YARN severs on secure cluster startup

I'm just switching over to use the 2.4-SNAPSHOT in a secured pseudo-dist cluster, and now the services are failing to come up because the web principals haven't been defined. Example 2014-01-29 15:42:58,558 INFO org.apache.hadoop.http.HttpServer2: Added filter static_user_filter (class=org.apache

Re: regression in 2.4? YARN severs on secure cluster startup

The RM issue should be fixed by YARN-1600 which I just committed this morning. Jason On 01/29/2014 10:33 AM, Steve Loughran wrote: I'm just switching over to use the 2.4-SNAPSHOT in a secured pseudo-dist cluster, and now the services are failing to come up because the web principals haven't be

Re: regression in 2.4? YARN severs on secure cluster startup

On 29 January 2014 17:13, Jason Lowe wrote: > The RM issue should be fixed by YARN-1600 which I just committed this > morning. if that's morning US time then hopefully yes. my build dates from about 13:00 GMT -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the indivi

[jira] [Created] (HADOOP-10307) Support multiple Authentication mechanisms for HTTP

Benoy Antony created HADOOP-10307: - Summary: Support multiple Authentication mechanisms for HTTP Key: HADOOP-10307 URL: https://issues.apache.org/jira/browse/HADOOP-10307 Project: Hadoop Common

[jira] [Created] (HADOOP-10308) Remove from core-defaulit.xml unsupported 'classic' and add 'yarn-tez' as value for mapreduce.framework.name property

Eric Charles created HADOOP-10308: - Summary: Remove from core-defaulit.xml unsupported 'classic' and add 'yarn-tez' as value for mapreduce.framework.name property Key: HADOOP-10308 URL: https://issues.apache.org/j

[jira] [Reopened] (HADOOP-10112) har file listing doesn't work with wild card

[ https://issues.apache.org/jira/browse/HADOOP-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-10112: -- > har file listing doesn't work with wild card > - >

[jira] [Resolved] (HADOOP-10112) har file listing doesn't work with wild card

[ https://issues.apache.org/jira/browse/HADOOP-10112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang resolved HADOOP-10112. -- Resolution: Invalid > har file listing doesn't work with wild card > ---

[jira] [Resolved] (HADOOP-10233) RPC lacks output flow control

[ https://issues.apache.org/jira/browse/HADOOP-10233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved HADOOP-10233. - Resolution: Duplicate > RPC lacks output flow control > - > >

Re: Re-swizzle 2.3

I noticed that somehow the target version field in JIRA was invisibly cleared on most of the Blocker/Critical JIRAs that were originally targeted for 2.3.0/2.4.0. I happened to have an old browser tab lying around from an earlier query for these and I tried to fix them up, marking some for 2.4

Re: Re-swizzle 2.3

On Wed, Jan 29, 2014 at 12:30 PM, Jason Lowe wrote: > It is a bit concerning that the JIRA history showed that the target version > was set at some point in the past but no record of it being cleared. Perhaps the version itself was renamed? Doug

[jira] [Created] (HADOOP-10309) S3 block filesystem should more aggressively delete temporary files

Joe Kelley created HADOOP-10309: --- Summary: S3 block filesystem should more aggressively delete temporary files Key: HADOOP-10309 URL: https://issues.apache.org/jira/browse/HADOOP-10309 Project: Hadoop C

Re: Re-swizzle 2.3

I just finished tuning up branch-2.3 and fixing up the HDFS and Common CHANGES.txt in trunk, branch-2, and branch-2.3. I had to merge back a few JIRAs committed between the swizzle and now where the fix version was 2.3 but weren't in branch-2.3. I think the only two HDFS and Common JIRAs that are

[jira] [Created] (HADOOP-10310) SaslRpcServer should be initialized even when no secret manager present

Aaron T. Myers created HADOOP-10310: --- Summary: SaslRpcServer should be initialized even when no secret manager present Key: HADOOP-10310 URL: https://issues.apache.org/jira/browse/HADOOP-10310 Proje

Re: Re-swizzle 2.3

I just filed this JIRA as a blocker for 2.3: https://issues.apache.org/jira/browse/HADOOP-10310 The tl;dr is that JNs will not work with security enabled without this fix. If others don't think that supporting QJM with security enabled warrants a blocker for 2.3, then we can certainly lower the pr

Re: Re-swizzle 2.3

I filed https://issues.apache.org/jira/browse/HDFS-5852 as a blocker. See what ye all think. Thanks, St.Ack On Wed, Jan 29, 2014 at 3:52 PM, Aaron T. Myers wrote: > I just filed this JIRA as a blocker for 2.3: > https://issues.apache.org/jira/browse/HADOOP-10310 > > The tl;dr is that JNs will

Re: Maintaining documentation

Hi JIRA and Wiki admins, I would like permission to assign JIRA issues to myself and edit Hadoop Wiki pages. I have already fixed some on HADOOP-10086 and I think there is further work. My username is "iwasakims" on JIRA and "MasatakeIwasaki" on Hadoop Wiki. Regards, Masatake Iwasaki (2014/0

[jira] [Created] (HADOOP-10311) Cleanup vendor names in the code base

Suresh Srinivas created HADOOP-10311: Summary: Cleanup vendor names in the code base Key: HADOOP-10311 URL: https://issues.apache.org/jira/browse/HADOOP-10311 Project: Hadoop Common Issue

Re: Re-swizzle 2.3

Okay, I'll look at YARN and MR CHANGES.txt problems. Seems like they aren't addressed yet. +Vinod On Jan 29, 2014, at 3:24 PM, Andrew Wang wrote: > I just finished tuning up branch-2.3 and fixing up the HDFS and Common > CHANGES.txt in trunk, branch-2, and branch-2.3. I had to merge back a f