[jira] [Created] (HADOOP-10502) Enhancements to LdapGroupsMapping.java

2014-04-14 Thread Dilli Arumugam (JIRA)
Dilli Arumugam created HADOOP-10502: --- Summary: Enhancements to LdapGroupsMapping.java Key: HADOOP-10502 URL: https://issues.apache.org/jira/browse/HADOOP-10502 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-10501) Server#getHandlers() accesses handlers without synchronization

2014-04-14 Thread Ted Yu (JIRA)
Ted Yu created HADOOP-10501: --- Summary: Server#getHandlers() accesses handlers without synchronization Key: HADOOP-10501 URL: https://issues.apache.org/jira/browse/HADOOP-10501 Project: Hadoop Common

Re: DISCUSS: use SLF4J APIs in new modules?

2014-04-14 Thread Steve Loughran
On 11 April 2014 18:37, Alejandro Abdelnur wrote: > if you dont convert mgs to templates the dont remove the guards, else you > create str mgs obj even when not logging. > > that is -we should have static constants? I like to do that in strings anyway, because tests can stay in sync with messages

Re: Plans of moving towards JDK7 in trunk

2014-04-14 Thread Steve Loughran
On 14 April 2014 17:46, Andrew Purtell wrote: > How well is trunk tested? Does anyone deploy it with real applications > running on top? When will the trunk codebase next be the basis for a > production release? An impromptu diff of hadoop-common trunk against > branch-2 as of today is 38,625 lin

Re: DISCUSS: use SLF4J APIs in new modules?

2014-04-14 Thread Chris Nauroth
+1 for the proposal. Notice also in Steve's examples that there is a lower risk of a format conversion bug compared to printf style with String.format. Chris Nauroth Hortonworks http://hortonworks.com/ On Fri, Apr 11, 2014 at 10:37 AM, Alejandro Abdelnur wrote: > if you dont convert mgs to te

[jira] [Created] (HADOOP-10500) TestDoAsEffectiveUser fails on JDK7 due to failure to reset proxy user configuration.

2014-04-14 Thread Chris Nauroth (JIRA)
Chris Nauroth created HADOOP-10500: -- Summary: TestDoAsEffectiveUser fails on JDK7 due to failure to reset proxy user configuration. Key: HADOOP-10500 URL: https://issues.apache.org/jira/browse/HADOOP-10500

Re: Plans of moving towards JDK7 in trunk

2014-04-14 Thread Sangjin Lee
I would say, to an extent. The current state of the jetty version is *severe*. We're 3 major versions behind, and if my understanding is correct, it was a long time ago they EOF'ed version 6.x. Yes, upgrading jetty could break some customers. However, we need to view it in balance. We're constantl

[jira] [Created] (HADOOP-10499) Removed unused parameter from ProxyUsers.authorize()

2014-04-14 Thread Benoy Antony (JIRA)
Benoy Antony created HADOOP-10499: - Summary: Removed unused parameter from ProxyUsers.authorize() Key: HADOOP-10499 URL: https://issues.apache.org/jira/browse/HADOOP-10499 Project: Hadoop Common

Re: Thinking ahead

2014-04-14 Thread Tsuyoshi OZAWA
Hi, +1 for 2.4.1 release(non-binding). There are some critical issues including YARN-1861 and YARN-1929 about RM-HA. IMO, we should include the fixes. One question is whether we can include RM-HA phase 2(YARN-556) in 2.5 by mid-May. It's still work-in-progress. Thanks, - Tsuyoshi On Mon, Apr 1

Re: Plans of moving towards JDK7 in trunk

2014-04-14 Thread Andrew Purtell
How well is trunk tested? Does anyone deploy it with real applications running on top? When will the trunk codebase next be the basis for a production release? An impromptu diff of hadoop-common trunk against branch-2 as of today is 38,625 lines. Can they be said to be the same animal? I ask becaus

Re: Plans of moving towards JDK7 in trunk

2014-04-14 Thread Colin McCabe
I think the bottom line here is that as long as our stable release uses JDK6, there is going to be a very, very strong disincentive to put any code which can't run on JDK6 into trunk. Like I said earlier, the traditional reason for putting something in trunk but not the stable release is that it n

Hadoop 0.23.11 Release Preparation

2014-04-14 Thread Jonathan Eagles
Hey gang, Heads up. In preparation of a 0.23.11 release, which seems likely in the next couple of weeks (correct me if I'm wrong, Tom). I'm going to begin a triage effort of the open JIRA targeted to the 0.23.x line. Don't be surprised to see comments and questions posted to many of the old JIRA.

[jira] [Created] (HADOOP-10498) Add support for proxy server

2014-04-14 Thread Daryn Sharp (JIRA)
Daryn Sharp created HADOOP-10498: Summary: Add support for proxy server Key: HADOOP-10498 URL: https://issues.apache.org/jira/browse/HADOOP-10498 Project: Hadoop Common Issue Type: New Featur

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

2014-04-14 Thread Apache Jenkins Server
See Changes: [cnauroth] HDFS-6238. TestDirectoryScanner leaks file descriptors. Contributed by Chris Nauroth. [cnauroth] HDFS-6237. TestDFSShell#testGet fails on Windows due to invalid file system path. Contributed by Chris Nauro

Re: Thinking ahead

2014-04-14 Thread Akira AJISAKA
+1 (non-binding) for 2.4.1 release. > We can debate whether or June is too early for hadoop-2.5 and it's > contents, but I recollect there was consensus that releases every 6 > weeks (or so) makes sense. Also, +1 (non-binding) for the 6 weeks (or so) timeline releases. However, I'm thinking it's

[jira] [Created] (HADOOP-10497) Doc NodeGroup-aware(HADOOP Virtualization Extensisons)

2014-04-14 Thread wenwupeng (JIRA)
wenwupeng created HADOOP-10497: -- Summary: Doc NodeGroup-aware(HADOOP Virtualization Extensisons) Key: HADOOP-10497 URL: https://issues.apache.org/jira/browse/HADOOP-10497 Project: Hadoop Common

Re: Thinking ahead

2014-04-14 Thread Zhijie Shen
On Sun, Apr 13, 2014 at 5:50 PM, Arun C Murthy wrote: > > I just opened https://issues.apache.org/jira/browse/YARN-1935. I've just assigned the ticket to me, and opened/linked a number of related tickets. I'll work on the security issues of the timeline server. Thanks, Zhijie -- Zhijie Shen H