[jira] [Created] (HADOOP-12783) TestWebDelegationToken failure: login options not compatible with IBM JDK

2016-02-09 Thread Devendra Vishwakarma (JIRA)
Devendra Vishwakarma created HADOOP-12783: - Summary: TestWebDelegationToken failure: login options not compatible with IBM JDK Key: HADOOP-12783 URL: https://issues.apache.org/jira/browse/HADOOP-12783

[jira] [Created] (HADOOP-12784) TestKMS failure: login options not compatible with IBM JDK

2016-02-09 Thread Devendra Vishwakarma (JIRA)
Devendra Vishwakarma created HADOOP-12784: - Summary: TestKMS failure: login options not compatible with IBM JDK Key: HADOOP-12784 URL: https://issues.apache.org/jira/browse/HADOOP-12784 Project

[jira] [Created] (HADOOP-12785) [Handling exceptions] LdapGroupsMapping.getGroups() do not provide information about root cause

2016-02-09 Thread Mukhadin Buzdov (JIRA)
Mukhadin Buzdov created HADOOP-12785: Summary: [Handling exceptions] LdapGroupsMapping.getGroups() do not provide information about root cause Key: HADOOP-12785 URL: https://issues.apache.org/jira/browse/HADOO

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

2016-02-09 Thread Wangda Tan
Hi Eric, replaceLabelsOnNode CLI syntax is different between 2.6 and 2.7. As mentioned by Naga, In 2.6, you should use "node1<:port>,label node2,label ..." And in 2.7, you can use either "," or "=" to separate host and label. So 2.7 is backward-compatible to 2.6, but it's not guaranteed that 2.7

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

2016-02-09 Thread Wangda Tan
+1 (binding) - Deployed a local cluster. - Configured node labels on queues/nodes. * Run job with node labels successfully. Regards, Wangda On Tue, Feb 9, 2016 at 10:36 PM, Wangda Tan wrote: > Hi Eric, > > replaceLabelsOnNode CLI syntax is different between 2.6 and 2.7. > > As mentioned by Nag

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

2016-02-09 Thread Kuhu Shukla
+1 (non-binding) - Built source- Deployed a single node cluster- Ran a sample streaming job- Ran basic hadoop fs commands. Thanks Junping!Regards,Kuhu On Tuesday, February 9, 2016 8:46 AM, Wangda Tan wrote: +1 (binding) - Deployed a local cluster. - Configured node labels on queues/no

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

2016-02-09 Thread Apache Jenkins Server
See Changes: [jlowe] Update CHANGES.txt to reflect recent commits to branch-2.7 and -- [...truncated 5588 lines...] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSiz

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

2016-02-09 Thread Sunil Govind
+1 (non-binding) with one note, - Installed tar ball from source and brought up the cluster - Ran few MR jobs and those are working fine. - UI and REST apis are also looks fine. Ran few rest queries for this test. - Tested node label feature and works fine. (one observation during this testing) O

Jenkins build is back to normal : Hadoop-Common-trunk #2352

2016-02-09 Thread Apache Jenkins Server
See

[jira] [Created] (HADOOP-12786) "hadoop key" command usage is not documented

2016-02-09 Thread Akira AJISAKA (JIRA)
Akira AJISAKA created HADOOP-12786: -- Summary: "hadoop key" command usage is not documented Key: HADOOP-12786 URL: https://issues.apache.org/jira/browse/HADOOP-12786 Project: Hadoop Common Is

Re: [Release thread] 2.8.0 release activities

2016-02-09 Thread Vinod Kumar Vavilapalli
Sure. The last time I checked, there were 20 odd blocker/critical tickets too that’ll need some of my time. Given that, if you can get them in before a week, we should be good. +Vinod > On Feb 5, 2016, at 1:19 PM, Subramaniam V K wrote: > > Vinod, > > Thanks for initiating the 2.8 release th

Jenkins build is back to normal : Hadoop-common-trunk-Java8 #1055

2016-02-09 Thread Apache Jenkins Server
See

[jira] [Created] (HADOOP-12787) KMS SPNEGO sequence does not work with WEBHDFS

2016-02-09 Thread Xiaoyu Yao (JIRA)
Xiaoyu Yao created HADOOP-12787: --- Summary: KMS SPNEGO sequence does not work with WEBHDFS Key: HADOOP-12787 URL: https://issues.apache.org/jira/browse/HADOOP-12787 Project: Hadoop Common Issue

[jira] [Created] (HADOOP-12788) OpensslAesCtrCryptoCodec should log what random number generator is used.

2016-02-09 Thread Wei-Chiu Chuang (JIRA)
Wei-Chiu Chuang created HADOOP-12788: Summary: OpensslAesCtrCryptoCodec should log what random number generator is used. Key: HADOOP-12788 URL: https://issues.apache.org/jira/browse/HADOOP-12788 P

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

2016-02-09 Thread Tsuyoshi Ozawa
+1(binding) - Verified signatures. - Ran tests for Apache Tez with the artifacts. All tests passed. - Ran local cluster and ran some examples on it. - Tsuyoshi On Wed, Feb 10, 2016 at 2:18 AM, Sunil Govind wrote: > +1 (non-binding) with one note, > > - Installed tar ball from source and brought

Re: [VOTE] Release Apache Hadoop 2.6.4 RC0

2016-02-09 Thread Junping Du
Thanks Yongjun for identifying and proposing this change to 2.6.4. I think this is the right thing to do and check for following releases. For 2.6.4, it seems unnecessary to create another release candidate for this issue as we only kicking off a new RC build when last RC has serious problem in

[GitHub] hadoop pull request: Merge pull request #1 from apache/trunk

2016-02-09 Thread 2899722744
GitHub user 2899722744 opened a pull request: https://github.com/apache/hadoop/pull/74 Merge pull request #1 from apache/trunk sync You can merge this pull request into a Git repository by running: $ git pull https://github.com/2899722744/hadoop trunk Alternatively you can rev

[GitHub] hadoop pull request: Merge pull request #1 from apache/trunk

2016-02-09 Thread 2899722744
Github user 2899722744 closed the pull request at: https://github.com/apache/hadoop/pull/74 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is e

[GitHub] hadoop pull request: Merge pull request #1 from apache/trunk

2016-02-09 Thread 2899722744
Github user 2899722744 commented on the pull request: https://github.com/apache/hadoop/pull/74#issuecomment-182214122 sync --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled