Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1 (binding) - Build & deploy single-node Hadoop from source code - Add/Remove node labels to queues/nodes - Run distributed shell commanding using default/specified node labels Thanks, Wangda On Mon, Dec 21, 2015 at 9:58 AM, Masatake Iwasaki < iwasak...@oss.nttdata.co.jp> wrote: >

Build failed in Jenkins: Hadoop-Yarn-trunk-Java8 #825

See Changes: [wangda] YARN-4454. NM to nodelabel mapping going wrong after RM restart. (Bibin -- [...truncated 5253 lines...] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time

Hadoop-Yarn-trunk-Java8 - Build # 825 - Failure

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/825/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 5446 lines...] Tests run: 1, Failures: 0, Errors:

Hadoop-Yarn-trunk-Java8 - Build # 826 - Still Failing

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/826/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 4866 lines...]

Build failed in Jenkins: Hadoop-Yarn-trunk-Java8 #826

See Changes: [wangda] YARN-4290. Add -showDetails option to YARN Nodes CLI to print all nodes -- [...truncated 4673 lines...] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time

Re: How to debug hadoop(or YARN) locally?

+1 for Chris, remote debug will help you. On Tue, Dec 22, 2015 at 1:54 AM, Chris Nauroth wrote: > If you're running the Hadoop daemons in pseudo-distributed mode (all the > daemons running as separate processes, but on a single dev host), then > another option is to

Build failed in Jenkins: Hadoop-Yarn-trunk #1542

See Changes: [wangda] YARN-4454. NM to nodelabel mapping going wrong after RM restart. (Bibin [wangda] YARN-4290. Add -showDetails option to YARN Nodes CLI to print all nodes -- [...truncated

Hadoop-Yarn-trunk - Build # 1542 - Still Failing

See https://builds.apache.org/job/Hadoop-Yarn-trunk/1542/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10786 lines...] at

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1 (binding) Thanks Xuan Gong > On Dec 21, 2015, at 4:25 PM, Chen He wrote: > > +1 (non-binding) > > deploy to a 2-node cluster > run loadgen and wc without problem > > > Kindly ask a silly question, why we separate 2.6.x from 2.7.x? > > On Mon, Dec 21, 2015 at 11:51

Re: How to debug hadoop(or YARN) locally?

If you're running the Hadoop daemons in pseudo-distributed mode (all the daemons running as separate processes, but on a single dev host), then another option is to launch the daemon's JVM with the JDWP arguments and attach a "remote" debugger. This can be either the jdb CLI debugger that ships

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1(non-binding) - verified mds and signature of source and binary tarball - started 3 node cluster and ran example jobs such as wordcount and terasort - built from source tarball with -Pnative on CentOS 7 and OpenJDK 7 - built site documentation and skimmed the contents Thanks, Masatake Iwasaki

Build failed in Jenkins: Hadoop-Yarn-trunk-Java8 #823

See -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H9 (Mapreduce Falcon Hadoop Pig Zookeeper Tez Hdfs) in workspace

Hadoop-Yarn-trunk-Java8 - Build # 823 - Still Failing

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/823/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 82 lines...] at

[jira] [Created] (YARN-4494) Recover completed apps asynchronously

Jun Gong created YARN-4494: -- Summary: Recover completed apps asynchronously Key: YARN-4494 URL: https://issues.apache.org/jira/browse/YARN-4494 Project: Hadoop YARN Issue Type: Improvement

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1 (Non Binding) * Built tar ball from source and deployed * Ran few MR Jobs successfully. Also tested preemption, node labels sanity scenarios including HA. * Verified RM Web UI and ran few REST queries. Seems fine. * CLI commands related to refresh are also working fine. Thanks and Regards

Re: Highlighting communication on releases

Thanks Karthik to bring up the topic. Comparing with small enhancement on email distribution for release/branch news, I think a more important thing is to make our community (contributor & committer) to be more aware on ongoing releases/branches. I can see two improvements could be helpful

Build failed in Jenkins: Hadoop-Yarn-trunk #1541

See Changes: [aajisaka] HDFS-9505. HDFS Architecture documentation needs to be refreshed. [aajisaka] Move HDFS-8914 from 2.8.0 to 2.7.3 in CHANGES.txt. -- [...truncated 10712 lines...] Tests

Hadoop-Yarn-trunk - Build # 1541 - Failure

See https://builds.apache.org/job/Hadoop-Yarn-trunk/1541/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10905 lines...] Building index for all the packages and

Re: How to debug hadoop(or YARN) locally?

oh, so cool. awesome. Thanks At 2015-12-22 11:01:55, "Jeff Zhang" wrote: >If you want to change the yarn internal code, you can use MiniYarnCluster >for testing. >

RE: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1(non-binding) -Built from source and deployed in 3 node cluster -Tested with combination of RMRestart/RM HA/RM work preserving restart/NM work preserving restart modes. -Ran MR and distributed shell sample applications. -Verified signature and md5 of binary Thanks & Regards Rohith Sharma K S

[jira] [Created] (YARN-4495) add a way to tell AM container increase/decrease request is invalid

sandflee created YARN-4495: -- Summary: add a way to tell AM container increase/decrease request is invalid Key: YARN-4495 URL: https://issues.apache.org/jira/browse/YARN-4495 Project: Hadoop YARN

Re: How to debug hadoop(or YARN) locally?

so, does it to mean that, if I change or add some code, I have to re-tarball the whole project using "mvn clean package -Pdist -DskipTests -Dtar", and then, deploy it to somewhere to remote debug? if yes, I think it is so inconvincence. if no, can you guys explain more in this way?

Hadoop-Yarn-trunk - Build # 1543 - Still Failing

See https://builds.apache.org/job/Hadoop-Yarn-trunk/1543/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10786 lines...] at

Build failed in Jenkins: Hadoop-Yarn-trunk #1543

See Changes: [cnauroth] YARN-3458. CPU resource monitoring in Windows. Contributed by Inigo -- [...truncated 10593 lines...] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

Thanks for putting together this release Vinod. +1 (binding) - Verified signatures - Started pseudo-cluster with binary distribution, verified git commit ID - Built sources, deployed pseudo-cluster and ran example map reduce jobs, DistributedShell, HDFS commands. PS: Extra file

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1 - downloaded src and bin tar balls and verified signatures. - built Tez and Spark with 2.7.2 artifacts and JDK7. - ran tests of Tez with 2.7.2 artifacts, it passed. FYI: YARN-4348, reported by Jian, is one of critical issues of 2.7.2 release.It's better to release 2.7.3 as soon as possible

[jira] [Resolved] (YARN-4165) An outstanding container request makes all nodes to be reserved causing all jobs pending

[ https://issues.apache.org/jira/browse/YARN-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved YARN-4165. --- Resolution: Invalid > An outstanding container request makes all nodes to be reserved causing all >

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1 (binding) - Downloaded source tarball - Verified signatures and checksums - Compiled and built a single node cluster - Confirmed commons-collections is upgraded to 3.2.2 - Compiled Hive 1.2.1 and Tez 0.7.0/0.8.1-alpha using Hadoop 2.7.2 pom successfully - Ran some Hive on Tez/MRv2 queries

Re: How to debug hadoop(or YARN) locally?

If you want to change the yarn internal code, you can use MiniYarnCluster for testing. https://github.com/apache/hadoop/blob/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/MiniYARNCluster.java On Tue, Dec 22, 2015 at

Jenkins build is back to normal : Hadoop-Yarn-trunk-Java8 #827

See

RE: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1 (Non binding) * Release notes and CHANGES.txt looked fine * Verified md5 checksums for both source and binary tar balls * Ran `mvn apache-rat:check` on source tarball, passed * Installed pseudo cluster * Did some basic filesystem operations * Ran a grep, sleepjob, word count successfully *

Jenkins build is back to normal : Hadoop-Yarn-trunk-Java8 #824

See

Re: How to debug hadoop(or YARN) locally?

Your best bet is to find a test that includes all the bits you want and execute that test in debug mode. (You can also change an existing test to include what you want, but in most cases it is easier to start with an existing test than to start from scratch.) Daniel On 12/20/15 6:01 PM,

[jira] [Resolved] (YARN-4469) yarn application -status should not show a stack trace for an unknown application ID

[ https://issues.apache.org/jira/browse/YARN-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton resolved YARN-4469. Resolution: Not A Problem Fix Version/s: 2.7.0 > yarn application -status should not

[jira] [Resolved] (YARN-4469) yarn application -status should not show a stack trace for an unknown application ID

[ https://issues.apache.org/jira/browse/YARN-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe resolved YARN-4469. -- Resolution: Duplicate Fixing resolution type. Normally fix version is only set for JIRAs that have

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

+1 (binding)- Verified the signature/digest. - I've built the dist tree with the native support from the source.- Brought up a single node cluster and ran a set of basic tests. From: Vinod Kumar Vavilapalli To: Hadoop Common ;