[jira] [Created] (HDFS-6596) Improve InputStream when read spans two blocks

2014-06-24 Thread Zesheng Wu (JIRA)
Zesheng Wu created HDFS-6596: Summary: Improve InputStream when read spans two blocks Key: HDFS-6596 URL: https://issues.apache.org/jira/browse/HDFS-6596 Project: Hadoop HDFS Issue Type:

RE: [DISCUSS] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Gangumalla, Uma
Thanks Arun. +1 Regards, Uma -Original Message- From: Arun C. Murthy [mailto:a...@hortonworks.com] Sent: Saturday, June 21, 2014 11:07 PM To: hdfs-dev@hadoop.apache.org Cc: common-...@hadoop.apache.org; yarn-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org Subject: Re:

[VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Arun C Murthy
Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will the usual period of 7 days. thanks, Arun [main]$ svn diff Index:

[jira] [Created] (HDFS-6597) New option for namenode upgrade

2014-06-24 Thread Danilo Vunjak (JIRA)
Danilo Vunjak created HDFS-6597: --- Summary: New option for namenode upgrade Key: HDFS-6597 URL: https://issues.apache.org/jira/browse/HDFS-6597 Project: Hadoop HDFS Issue Type: Improvement

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Thomas Graves
+1 Tom On 6/24/14, 3:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will the usual period of 7 days.

Jenkins build is back to normal : Hadoop-Hdfs-trunk #1784

2014-06-24 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1784/changes

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Jitendra Pandey
+1 On Tue, Jun 24, 2014 at 6:42 AM, Thomas Graves tgra...@yahoo-inc.com.invalid wrote: +1 Tom On 6/24/14, 3:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Devaraj K
+1 Thanks Devaraj K On Tue, Jun 24, 2014 at 2:23 PM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will

Re: [VOTE] Release Apache Hadoop 0.23.11

2014-06-24 Thread Devaraj K
+1 (non-binding) Deployed in a two node cluster and ran few M/R Jobs, everything works fine. On Thu, Jun 19, 2014 at 8:44 PM, Thomas Graves tgra...@yahoo-inc.com.invalid wrote: Hey Everyone, There have been various bug fixes that have went into branch-0.23 since the 0.23.10 release.

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Jason Lowe
+1 (binding) Jason On 06/24/2014 03:53 AM, Arun C Murthy wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will the usual period of 7 days.

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Hitesh Shah
+1 (binding) — Hitesh On Jun 24, 2014, at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Steve Loughran
+1 (binding) On 24 June 2014 01:53, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will the usual period

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Tsuyoshi OZAWA
+1(non-binding) On Wed, Jun 25, 2014 at 1:55 AM, Hitesh Shah hit...@apache.org wrote: +1 (binding) — Hitesh On Jun 24, 2014, at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to

[jira] [Created] (HDFS-6598) fix a typo in message issued from explorer.js

2014-06-24 Thread Yongjun Zhang (JIRA)
Yongjun Zhang created HDFS-6598: --- Summary: fix a typo in message issued from explorer.js Key: HDFS-6598 URL: https://issues.apache.org/jira/browse/HDFS-6598 Project: Hadoop HDFS Issue Type:

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Aaron T. Myers
+1 (binding) -- Aaron T. Myers Software Engineer, Cloudera On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Zhijie Shen
+1 (non-binding) On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers a...@cloudera.com wrote: +1 (binding) -- Aaron T. Myers Software Engineer, Cloudera On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Akira AJISAKA
+1 (non-binding) (2014/06/24 10:33), Zhijie Shen wrote: +1 (non-binding) On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers a...@cloudera.com wrote: +1 (binding) -- Aaron T. Myers Software Engineer, Cloudera On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks,

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Jakob Homan
+1 (binding) On Tue, Jun 24, 2014 at 10:33 AM, Zhijie Shen zs...@hortonworks.com wrote: +1 (non-binding) On Wed, Jun 25, 2014 at 1:26 AM, Aaron T. Myers a...@cloudera.com wrote: +1 (binding) -- Aaron T. Myers Software Engineer, Cloudera On Tue, Jun 24, 2014 at 1:53 AM, Arun

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Chris Nauroth
+1 (binding) Chris Nauroth Hortonworks http://hortonworks.com/ On Tue, Jun 24, 2014 at 10:58 AM, Jakob Homan jgho...@gmail.com wrote: +1 (binding) On Tue, Jun 24, 2014 at 10:33 AM, Zhijie Shen zs...@hortonworks.com wrote: +1 (non-binding) On Wed, Jun 25, 2014 at 1:26 AM, Aaron

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Chris Douglas
+1 -C On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will the usual

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Andrew Wang
+1 On Tue, Jun 24, 2014 at 11:13 AM, Chris Douglas cdoug...@apache.org wrote: +1 -C On Tue, Jun 24, 2014 at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've

[jira] [Created] (HDFS-6599) 2.4 addBlock is 10 to 20 times slower compared to 0.23

2014-06-24 Thread Kihwal Lee (JIRA)
Kihwal Lee created HDFS-6599: Summary: 2.4 addBlock is 10 to 20 times slower compared to 0.23 Key: HDFS-6599 URL: https://issues.apache.org/jira/browse/HDFS-6599 Project: Hadoop HDFS Issue Type:

Re: SIMPLE authentication is not enabled error for secured hdfs read

2014-06-24 Thread Chris Nauroth
Hi David, UserGroupInformation.createRemoteUser does not attach credentials to the returned ugi. I expect the server side is rejecting the connection due to lack of credentials. This is actually by design. The UserGroupInformation.createRemoteUser method is primarily intended for use on the

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Arun C Murthy
Andrew, Thanks for starting this thread. I'll edit the wiki to provide more context around rolling-upgrades etc. which, as I pointed out in the original thread, are key IMHO. On Jun 24, 2014, at 11:17 AM, Andrew Wang andrew.w...@cloudera.com wrote:

[jira] [Created] (HDFS-6600) fsck -move fails in secured clusters.

2014-06-24 Thread Chris Nauroth (JIRA)
Chris Nauroth created HDFS-6600: --- Summary: fsck -move fails in secured clusters. Key: HDFS-6600 URL: https://issues.apache.org/jira/browse/HDFS-6600 Project: Hadoop HDFS Issue Type: Bug

[jira] [Created] (HDFS-6601) Issues in finalizing rolling upgrade when there is a layout version change

2014-06-24 Thread Kihwal Lee (JIRA)
Kihwal Lee created HDFS-6601: Summary: Issues in finalizing rolling upgrade when there is a layout version change Key: HDFS-6601 URL: https://issues.apache.org/jira/browse/HDFS-6601 Project: Hadoop HDFS

[jira] [Reopened] (HDFS-6527) Edit log corruption due to defered INode removal

2014-06-24 Thread Jing Zhao (JIRA)
[ https://issues.apache.org/jira/browse/HDFS-6527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao reopened HDFS-6527: - Reopen the jira and wait for [~kihwal] to comment. Edit log corruption due to defered INode removal

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Steve Loughran
That classpath policy was explicitly added because we can't lock down our dependencies for security/bug fix reasons, and also because if we do update something explicitly, their transitive dependencies can change -beyond our control. https://issues.apache.org/jira/browse/HADOOP-9555 is an example

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Vinod Kumar Vavilapalli
Tx for the new thread Andrew, hopefully it can attract more eyes. Here's what I am behind - a modified proposal C. - Overall I wouldn't think about EOL of JDK7 and/or JDK8 specifically given how long it has taken for JDK6 life-cycle to end. We should try to focus on JDK7 only for now. - As we

Re: [VOTE] Change by-laws on release votes: 5 days instead of 7

2014-06-24 Thread Vinod Kumar Vavilapalli
+1 Vinod On Jun 24, 2014, at 1:53 AM, Arun C Murthy a...@hortonworks.com wrote: Folks, As discussed, I'd like to call a vote on changing our by-laws to change release votes from 7 days to 5. I've attached the change to by-laws I'm proposing. Please vote, the vote will the usual

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Andrew Wang
Hi all, On dependencies, we've bumped library versions when we think it's safe and the APIs in the new version are compatible. Or, it's not leaked to the app classpath (e.g the JUnit version bump). I think the JIRAs Arun mentioned fall into one of those categories. Steve can do a better job

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Alejandro Abdelnur
After reading this thread and thinking a bit about it, I think it should be OK such move up to JDK7 in Hadoop 2 for the following reasons: * Existing Hadoop 2 releases and related projects are running on JDK7 in production. * Commercial vendors of Hadoop have already done lot of work to

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Steve Loughran
+1, though I think 2.5 may be premature if we want to send a warning note last ever. That's an issue for followon when in branch 2. Guava and protobuf.jar are two things we have to leave alone, with the first being unfortunate, but their attitude to updates is pretty dramatic. The latter? We all

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Arun Murthy
Alejandro, On Tue, Jun 24, 2014 at 4:44 PM, Alejandro Abdelnur t...@cloudera.com wrote: After reading this thread and thinking a bit about it, I think it should be OK such move up to JDK7 in Hadoop 2 for the following reasons: * Existing Hadoop 2 releases and related projects are running

Re: Moving to JDK7, JDK8 and new major releases

2014-06-24 Thread Arun C Murthy
On Jun 24, 2014, at 4:22 PM, Andrew Wang andrew.w...@cloudera.com wrote: Since Hadoop apps can and do depend on the Hadoop classpath, the classpath is effectively part of our API. I'm sure there are user apps out there that will break if we make incompatible changes to the classpath. I