Re: Thinking ahead

2014-04-13 Thread Sandy Ryza
Reference: http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201401.mbox/%3ccajs6+b4tkupvqfaorf_314xveivryqy-vtryd8+36tu_bc5...@mail.gmail.com%3E This is of course open source, and I have neither the ability nor the desire to compel or pressure anybody to work on anything, but I wanted to

Re: Thinking ahead

2014-04-13 Thread Sandy Ryza
Unfortunately I don't have the bandwidth to take on ATS security at this time. My (I now understand mistaken) impression that it was being worked on, as we had discussed it under the initial criteria for including the AHS in a release. I brought it up as a feature I felt worth waiting for if it m

Re: Thinking ahead

2014-04-13 Thread Arun C Murthy
Sandy, On Apr 12, 2014, at 10:09 AM, Sandy Ryza wrote: > I'm having trouble editing the wiki, but I think Timeline Server stability > (e.g. security and locking down APIs) should go on that list. I'm very glad to see you are very passionate about security for ATS since you've asked about it

Re: Thinking ahead

2014-04-13 Thread Vinod Kumar Vavilapalli
I'm still wading through 2.4.1 critical issues (failing tests, blockers etc) so haven't gotten time to think about the 2.5 list w.r.t YARN. Will do so in the next week. BTW, folks, please refrain from adding items to the list that you yourselves are not volunteering to work on. Anyone keen to see

Re: Thinking ahead

2014-04-13 Thread Arun C. Murthy
> On Apr 12, 2014, at 10:09 AM, Sandy Ryza wrote: > > +1 for starting to think about 2.5. Early June seems a little early to me > - we had talked about a quarterly release cadence and this would be about > half that. We can debate whether or June is too early for hadoop-2.5 and it's contents,

Re: Plans of moving towards JDK7 in trunk

2014-04-13 Thread Raymie Stata
There's an outstanding question addressed to me: "Are there particular features or new dependencies that you would like to contribute (or see contributed) that require using the Java 1.7 APIs?" The question misses the point: We'd figure out how to write something we wanted to contribute to Hadoop

[jira] [Created] (HADOOP-10496) Metrics system FileSink can leak file descriptor.

2014-04-13 Thread Chris Nauroth (JIRA)
Chris Nauroth created HADOOP-10496: -- Summary: Metrics system FileSink can leak file descriptor. Key: HADOOP-10496 URL: https://issues.apache.org/jira/browse/HADOOP-10496 Project: Hadoop Common

[jira] [Created] (HADOOP-10495) TestFileUtil fails on Windows due to bad permission assertions.

2014-04-13 Thread Chris Nauroth (JIRA)
Chris Nauroth created HADOOP-10495: -- Summary: TestFileUtil fails on Windows due to bad permission assertions. Key: HADOOP-10495 URL: https://issues.apache.org/jira/browse/HADOOP-10495 Project: Hadoop

[jira] [Created] (HADOOP-10494) Ensure Jets3tFileSystemStore respects URI path for block files

2014-04-13 Thread Mark J Greene (JIRA)
Mark J Greene created HADOOP-10494: -- Summary: Ensure Jets3tFileSystemStore respects URI path for block files Key: HADOOP-10494 URL: https://issues.apache.org/jira/browse/HADOOP-10494 Project: Hadoop

[jira] [Created] (HADOOP-10493) callid for RPCrequest and RPCresponse should match but they are not always which creates problem for someone like me who consumes these two types of TCP packets

2014-04-13 Thread Charlene Sun (JIRA)
Charlene Sun created HADOOP-10493: - Summary: callid for RPCrequest and RPCresponse should match but they are not always which creates problem for someone like me who consumes these two types of TCP packets Key: HADOOP-10493

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

2014-04-13 Thread Apache Jenkins Server
See Changes: [cnauroth] HDFS-6236. ImageServlet should use Time#monotonicNow to measure latency. Contributed by Chris Nauroth. -- [...truncated 60580 lines...] Adding reference: maven.local.

Re: Plans of moving towards JDK7 in trunk

2014-04-13 Thread Tsuyoshi OZAWA
Hi, +1 for Karthik's idea(non-binding). IMO, we should keep the compatibility between JDK 6 and JDK 7 on both branch-1 and branch-2, because users can be using them. For future releases that we can declare breaking compatibility(e.g. 3.0.0 release), we can use JDK 7 features if we can get benefit