Re: Hadoop 2.6.1 Release process thread

It might have been because we thought that HDFS-7704 was going to make it. It's both make it or neither does. Now that we know HDFS-7704 is out, HDFS-7916 should definitely be out. I hope that clarifies. On Tue, Aug 11, 2015 at 6:26 PM, Vinod Kumar Vavilapalli < vino...@hortonworks.com> wrote: >

Re: Hadoop 2.6.1 Release process thread

I earlier removed HDFS-7916 from the list given HDFS-7704 was only in 2.7.0. Chris Trezzo added it back and so it appeared in my lists. I removed it again, Chris, please comment on why you added it back. If you want it included, please comment here and we can add it after we figure out the why

[jira] [Created] (HADOOP-12315) hbaseprotoc_postapply in the test-patch hbase personality can return a wrong status

Kengo Seki created HADOOP-12315: --- Summary: hbaseprotoc_postapply in the test-patch hbase personality can return a wrong status Key: HADOOP-12315 URL: https://issues.apache.org/jira/browse/HADOOP-12315 P

[jira] [Created] (HADOOP-12314) check_unittests in test-patch.sh can return a wrong status

Kengo Seki created HADOOP-12314: --- Summary: check_unittests in test-patch.sh can return a wrong status Key: HADOOP-12314 URL: https://issues.apache.org/jira/browse/HADOOP-12314 Project: Hadoop Common

Re: Hadoop 2.6.1 Release process thread

Could you double check HDFS-7916? HDFS-7916 is needed only if HDFS-7704 makes it. However, I see commits for HDFS-7916 in this list, but not for HDFS-7704. If HDFS-7704 is not in the list, we should not backport HDFS-7916 as it fixes an issue introduced by HDFS-7704. On Tue, Aug 11, 2015 at 4:10 P

Re: Hadoop 2.6.1 Release process thread

Put the list here: https://wiki.apache.org/hadoop/Release-2.6.1-Working-Notes. And started figuring out ways to fast-path the cherry-picks. Thanks +Vinod On Aug 11, 2015, at 1:15 PM, Vinod Kumar Vavilapalli mailto:vino...@apache.org>> wrote: (2) With Wangda's help offline, I prepared an orde

[DISCUSS] git rebase vs. git merge for branch development

Hi all, We are currently working on a pretty substantial new feature in a branch over at HDFS-7285. As the # of commits has grown, running `git rebase` and fixing conflicts in the 180+ commits has become untenable. As you may recall, we voted to use a rebase workflow when we did the switch from SV

Re: Planning Hadoop 2.6.1 release

Jason Lowe just filed YARN-4047 ( patch available too ) which probably is also a good candidate for 2.6.1 or 2.6.2 if the list is frozen. I have labelled the jira as a 2.6.1 candidate. Feel free to switch to 2.6.2 if needed. thanks — Hitesh On Aug 10, 2015, at 4:15 PM, Vinod Kumar Vavilapalli

Re: Hadoop 2.6.1 Release process thread

This is done. Thanks +Vinod On Aug 11, 2015, at 1:15 PM, Vinod Kumar Vavilapalli mailto:vino...@apache.org>> wrote: (1) Create 2.6.1 branch and prep branch-2.6 for 2.6.2. I am doing this today.

Hadoop 2.6.1 Release process thread

Hi all, We had a long release-related discussion for 2.6.1 [1], and we pooled in a big list of patches [2]. Together with Akira and Sangjin who offered help with the release, I am starting the release process. Things to do (1) Create 2.6.1 branch and prep branch-2.6 for 2.6.2. I am doing this

Build failed in Jenkins: Hadoop-common-trunk-Java8 #284

See Changes: [wangda] YARN-3873. PendingApplications in LeafQueue should also use OrderingPolicy. (Sunil G via wangda) [szetszwo] HDFS-8818. Changes the global moveExecutor to per datanode executors and changes MAX_SIZE_TO_M

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

See Changes: [wangda] YARN-3873. PendingApplications in LeafQueue should also use OrderingPolicy. (Sunil G via wangda) [szetszwo] HDFS-8818. Changes the global moveExecutor to per datanode executors and changes MAX_SIZE_TO_MOVE t

[jira] [Resolved] (HADOOP-9654) IPC timeout doesn't seem to be kicking in

[ https://issues.apache.org/jira/browse/HADOOP-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajith S resolved HADOOP-9654. - Resolution: Duplicate Closing the issues, if anyone disagree, please feel free to reopen > IPC timeout d