Re: Thinking ahead to hadoop-2.6

Thanks for initiating the thread Arun. Can we add YARN-1051 to the list? We have most of the patches for the sub-JIRAs under review and have committed a couple. -Subru -- Forwarded message -- From: Arun C Murthy Date: Tue, Aug

Re: [VOTE] Merge fs-encryption branch to trunk

+1 (binding) We have made some great progress in the last few days on some of the issues I raised. I have posted a summary of the followup items that are needed on the Jira today. I am +1ing expecting the team will complete Items 1 (distcp/cp) and 2 (webhdfs) promptly. Before we publish trans

Re: [VOTE] Merge fs-encryption branch to trunk

With 4 binding +1s, 3 non-binding +1s, no -1s, the vote passes. Thanks everyone who gave feedback at this stage, particularly Sanjay and Suresh. I should add that this vote will run for the standard 7 days for a non-release vote, so will close at 12PM Pacific on August 15th. On Fri, Aug 8, 2014 a

[jira] [Created] (HADOOP-10971) Flag to make `hadoop fs -ls` print filenames only

Ryan Williams created HADOOP-10971: -- Summary: Flag to make `hadoop fs -ls` print filenames only Key: HADOOP-10971 URL: https://issues.apache.org/jira/browse/HADOOP-10971 Project: Hadoop Common

Re: [DISCUSS] Switch to log4j 2

Using asynchronous loggers for improved performance sounds reasonable. However, IMO we already log too much at INFO level (particularly YARN). Logging more at DEBUG level and lowering the overhead of enabling DEBUG logging is preferable. One concern is the defaults. Based on what I read on the log

Re: [DISCUSS] Switch to log4j 2

Not necessarily opposed to switching logging frameworks, but I believe we can actually support async logging with today's logging system if we wanted to, e.g. as was done for the HDFS audit logger in this JIRA: https://issues.apache.org/jira/browse/HDFS-5241 -- Aaron T. Myers Software Engineer, C

Re: [DISCUSS] Switch to log4j 2

moving to SLF4J as an API is independent —it's just a better API for logging than commons-logging, was already a dependency and doesn't force anyone to switch to a new log back end. On 15 August 2014 03:34, Tsuyoshi OZAWA wrote: > Hi, > > Steve has started discussion titled "use SLF4J APIs in n

Build failed in Jenkins: Hadoop-Common-0.23-Build #1042

See -- [...truncated 8263 lines...] at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.e