Failed: YARN-2088 PreCommit Build #4253
Jira: https://issues.apache.org/jira/browse/YARN-2088
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4253/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13021 lines...]
http://issues.apache.org/jira/secure/attachment/12646030/YARN-2088.v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:
org.apache.hadoop.yarn.util.TestFSDownload
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4253//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4253//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
93104ed96080a5a51692241d02fa9a3d1829e573 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4252
Archived 17 artifacts
Archive block size is 32768
Received 48 blocks and 6697753 bytes
Compression is 19.0%
Took 5.2 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
1 tests failed.
FAILED:
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache(TestFSDownload.java:363)
Failed: YARN-2208 PreCommit Build #4254
Jira: https://issues.apache.org/jira/browse/YARN-2208
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4254/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13274 lines...]
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.util.TestFSDownload
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4254//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4254//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
eb4fe9050c82c66ee10ae1548a20a1ba6635 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4252
Archived 22 artifacts
Archive block size is 32768
Received 220 blocks and 1346649 bytes
Compression is 84.3%
Took 2.5 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
2 tests failed.
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart.testShouldNotCountFailureToMaxAttemptRetry
Error Message:
AppAttempt state is not correct (timedout) expected:ALLOCATED but
was:SCHEDULED
Stack Trace:
java.lang.AssertionError: AppAttempt state is not correct (timedout)
expected:ALLOCATED but was:SCHEDULED
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at
org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:414)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAM(MockRM.java:569)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAndRegisterAM(MockRM.java:576)
at
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart.testShouldNotCountFailureToMaxAttemptRetry(TestAMRestart.java:401)
FAILED:
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache(TestFSDownload.java:363)
Success: YARN-2181 PreCommit Build #4255
Jira: https://issues.apache.org/jira/browse/YARN-2181
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4255/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13088 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12654947/YARN-2181.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4255//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4255//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
5bae7daa326fd71b781128c6d5069d8ea84a787c logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4252
Archived 17 artifacts
Archive block size is 32768
Received 51 blocks and 6827294 bytes
Compression is 19.7%
Took 2.3 sec
Description set: YARN-2181
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Resolved] (YARN-2258) Aggregation of MR job logs failing when Resourcemanager switches
[ https://issues.apache.org/jira/browse/YARN-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-2258. -- Resolution: Duplicate Assignee: Wangda Tan Aggregation of MR job logs failing when Resourcemanager switches Key: YARN-2258 URL: https://issues.apache.org/jira/browse/YARN-2258 Project: Hadoop YARN Issue Type: Sub-task Components: log-aggregation, nodemanager Affects Versions: 2.4.0 Reporter: Nishan Shetty Assignee: Wangda Tan 1.Install RM in HA mode 2.Run a job with more tasks 3.Induce RM switchover while job is in progress Observe that log aggregation fails for the job which is running when Resourcemanager switchover is induced. -- This message was sent by Atlassian JIRA (v6.2#6252)
Hadoop-Yarn-trunk - Build # 609 - Still Failing
See https://builds.apache.org/job/Hadoop-Yarn-trunk/609/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 13583 lines...] Results : Failed tests: TestFSDownload.testDownloadPublicWithStatCache:363 null Tests run: 150, Failures: 1, Errors: 0, Skipped: 1 [INFO] [INFO] Reactor Summary: [INFO] [INFO] hadoop-yarn ... SUCCESS [ 4.281 s] [INFO] hadoop-yarn-api ... SUCCESS [02:14 min] [INFO] hadoop-yarn-common FAILURE [ 53.421 s] [INFO] hadoop-yarn-server SKIPPED [INFO] hadoop-yarn-server-common . SKIPPED [INFO] hadoop-yarn-server-nodemanager SKIPPED [INFO] hadoop-yarn-server-web-proxy .. SKIPPED [INFO] hadoop-yarn-server-applicationhistoryservice .. SKIPPED [INFO] hadoop-yarn-server-resourcemanager SKIPPED [INFO] hadoop-yarn-server-tests .. SKIPPED [INFO] hadoop-yarn-client SKIPPED [INFO] hadoop-yarn-applications .. SKIPPED [INFO] hadoop-yarn-applications-distributedshell . SKIPPED [INFO] hadoop-yarn-applications-unmanaged-am-launcher SKIPPED [INFO] hadoop-yarn-site .. SKIPPED [INFO] hadoop-yarn-project ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 03:13 min [INFO] Finished at: 2014-07-10T10:34:53+00:00 [INFO] Final Memory: 77M/1041M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project hadoop-yarn-common: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/target/surefire-reports for the individual test results. [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :hadoop-yarn-common Build step 'Execute shell' marked build as failure Archiving artifacts Updating YARN-2131 Updating HADOOP-10801 Updating YARN-1366 Updating HADOOP-10812 Updating HDFS-6643 Updating HDFS-6618 Updating HDFS-6622 Updating HDFS-6645 Sending e-mails to: yarn-dev@hadoop.apache.org Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
Build failed in Jenkins: Hadoop-Yarn-trunk #609
See https://builds.apache.org/job/Hadoop-Yarn-trunk/609/changes Changes: [wang] HADOOP-10812. Delegate KeyProviderExtension#toString to underlying KeyProvider. (wang) [szetszwo] HDFS-6643. Refactor INodeWithAdditionalFields.PermissionStatusFormat and INodeFile.HeaderFormat. [jing9] HDFS-6645. Add test for successive Snapshots between XAttr modifications. Contributed by Stephen Chu. [cmccabe] HDFS-6622. Rename and AddBlock may race and produce invalid edits (kihwal via cmccabe) [cmccabe] HDFS-6618. FSNamesystem#delete drops the FSN lock between removing INodes from the tree and deleting them from the inode map (kihwal via cmccabe) [kasha] YARN-2131. Add a way to format the RMStateStore. (Robert Kanter via kasha) [jianhe] YARN-1366. Changed AMRMClient to re-register with RM and send outstanding requests back to RM on work-preserving RM restart. Contributed by Rohith [stevel] HADOOP-10801 dead link in site.xml -- [...truncated 13390 lines...] Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/org/apache/hadoop/yarn/factory/providers//package-use.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/org/apache/hadoop/yarn/proto//package-use.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/org/apache/hadoop/yarn/server/api//package-use.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/org/apache/hadoop/yarn/server/api/protocolrecords//package-use.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/org/apache/hadoop/yarn/util//package-use.html... Building index for all the packages and classes... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/overview-tree.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/index-all.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/deprecated-list.html... Building index for all classes... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/allclasses-frame.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/allclasses-noframe.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/index.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/overview-summary.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/help-doc.html... Generating https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/stylesheet.css... 1 warning [WARNING] Javadoc Warnings [WARNING] https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java:1011: warning - Tag @link: reference not found: DEFAULT_YARN_CROSS_PLATFORM_APPLICATION_CLASSPATH [INFO] Building jar: https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/hadoop-yarn-api-3.0.0-SNAPSHOT-javadoc.jar [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (depcheck) @ hadoop-yarn-api --- [INFO] [INFO] --- maven-checkstyle-plugin:2.6:checkstyle (default-cli) @ hadoop-yarn-api --- [INFO] [INFO] There are 3023 checkstyle errors. [WARNING] Unable to locate Source XRef to link to - DISABLED [INFO] [INFO] --- findbugs-maven-plugin:2.3.2:findbugs (default-cli) @ hadoop-yarn-api --- [INFO] ** FindBugsMojo execute *** [INFO] canGenerate is true [INFO] ** FindBugsMojo executeFindbugs *** [INFO] Temp File is https://builds.apache.org/job/Hadoop-Yarn-trunk/ws/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/findbugsTemp.xml [INFO] Fork Value is true [INFO] xmlOutput is true [INFO] [INFO] [INFO] Building hadoop-yarn-common 3.0.0-SNAPSHOT [INFO] [WARNING] The POM for org.eclipse.m2e:lifecycle-mapping:jar:1.0.0 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for
[jira] [Created] (YARN-2272) UI issues in timeline server
Nishan Shetty created YARN-2272: --- Summary: UI issues in timeline server Key: YARN-2272 URL: https://issues.apache.org/jira/browse/YARN-2272 Project: Hadoop YARN Issue Type: Bug Components: timelineserver Affects Versions: 2.4.0 Reporter: Nishan Shetty Links to nodemanager is not working in timeline server -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (YARN-2272) UI issues in timeline server
[ https://issues.apache.org/jira/browse/YARN-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nishan Shetty resolved YARN-2272. - Resolution: Duplicate UI issues in timeline server Key: YARN-2272 URL: https://issues.apache.org/jira/browse/YARN-2272 Project: Hadoop YARN Issue Type: Bug Components: timelineserver Affects Versions: 2.4.0 Reporter: Nishan Shetty Priority: Minor Links to nodemanager is not working in timeline server -- This message was sent by Atlassian JIRA (v6.2#6252)
Failed: YARN-1408 PreCommit Build #4259
Jira: https://issues.apache.org/jira/browse/YARN-1408
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4259/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 10151 lines...]
==
==
Determining number of patched javac warnings.
==
==
/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests
-DHadoopPatchProcess -Pnative -Ptest-patch
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/patchprocess/patchJavacWarnings.txt
21
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12655007/Yarn-1408.8.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:red}-1 javac{color:red}. The patch appears to cause the build to
fail.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4259//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
a5876e831e70d3b98410cc0515d84891a9d48089 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4255
Archived 5 artifacts
Archive block size is 32768
Received 18 blocks and 2806679 bytes
Compression is 17.4%
Took 2.6 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
Failed: YARN-2228 PreCommit Build #4257
Jira: https://issues.apache.org/jira/browse/YARN-2228
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4257/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13238 lines...]
http://issues.apache.org/jira/secure/attachment/12654999/YARN-2228.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice:
org.apache.hadoop.yarn.util.TestFSDownload
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4257//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4257//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
11db60b696204a9a882d96bf95c46f4a7a5c806b logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4255
Archived 27 artifacts
Archive block size is 32768
Received 43 blocks and 7039207 bytes
Compression is 16.7%
Took 2.2 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
1 tests failed.
FAILED:
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache(TestFSDownload.java:363)
Failed: YARN-1994 PreCommit Build #4258
Jira: https://issues.apache.org/jira/browse/YARN-1994
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4258/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 14116 lines...]
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.util.TestFSDownload
org.apache.hadoop.yarn.server.applicationhistoryservice.TestMemoryApplicationHistoryStore
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4258//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4258//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
cba32cfab1131e7fd34bdf5715dbf3661acf8f49 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4255
Archived 52 artifacts
Archive block size is 32768
Received 46 blocks and 8064207 bytes
Compression is 15.7%
Took 2.7 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
2 tests failed.
REGRESSION:
org.apache.hadoop.yarn.server.applicationhistoryservice.TestMemoryApplicationHistoryStore.testMassiveWriteContainerHistory
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.server.applicationhistoryservice.TestMemoryApplicationHistoryStore.testMassiveWriteContainerHistory(TestMemoryApplicationHistoryStore.java:201)
FAILED:
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache(TestFSDownload.java:363)
Re: Jenkins Build Slaves
Thanks, Giri, for taking care of pkgconfig. It looks like most (all?) pre-commit builds have some new failing tests: https://builds.apache.org/job/PreCommit-HADOOP-Build/4247/testReport/ On the symlink tests, is there any chance that the new hosts have a different version/different behavior for the ln command? The TestIPC failure is in a stress test that checks behavior after spamming a lot of connections at an RPC server. Maybe the new hosts have something different in the TCP stack, such as TCP backlog? I likely won't get a chance to investigate any more today, but I wanted to raise the issue in case someone else gets an opportunity to look. Chris Nauroth Hortonworks http://hortonworks.com/ On Wed, Jul 9, 2014 at 10:33 AM, Giridharan Kesavan gkesa...@hortonworks.com wrote: I dont think so, let me fix that. Thanks Chris for pointing that out. -giri On Wed, Jul 9, 2014 at 9:50 AM, Chris Nauroth cnaur...@hortonworks.com wrote: Hi Giri, Is pkgconfig deployed on the new Jenkins slaves? I noticed this build failed: https://builds.apache.org/job/PreCommit-HADOOP-Build/4237/ Looking in the console output, it appears the HDFS native code failed to build due to missing pkgconfig. [exec] CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message): [exec] Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Chris Nauroth Hortonworks http://hortonworks.com/ On Wed, Jul 9, 2014 at 7:08 AM, Giridharan Kesavan gkesa...@hortonworks.com wrote: Build jobs are now configured to run on the newer set of slaves. -giri On Mon, Jul 7, 2014 at 4:12 PM, Giridharan Kesavan gkesa...@hortonworks.com wrote: All Yahoo is in the process of retiring all the hadoop jenkins build slaves, *hadoop[1-9]* and replace them with a newer set of beefier hosts. These new machines are configured with *ubuntu-14.04*. Over the next couple of days I will be configuring the build jobs to run on these newly configured build slaves. To automate the installation of tools and build libraries I have put together ansible scripts and here is the link to the toolchain repo. *https://github.com/apache/toolchain https://github.com/apache/toolchain * During the transition, the old build slave will be accessible, and expected to be shutdown by 07/15. I will send out an update later this week when this transition is complete. *Mean while, I would like to request the project owners to remove/cleanup any stale * *jenkins job for their respective project and help with any builds issue to make this * *transition seamless. * Thanks - Giri -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
[jira] [Created] (YARN-2273) Flapping node caused NPE in FairScheduler
Andy Skelton created YARN-2273:
--
Summary: Flapping node caused NPE in FairScheduler
Key: YARN-2273
URL: https://issues.apache.org/jira/browse/YARN-2273
Project: Hadoop YARN
Issue Type: Bug
Components: fairscheduler, resourcemanager
Affects Versions: 2.3.0
Environment: cdh5.0.2 wheezy
Reporter: Andy Skelton
One DN experienced memory errors and entered a cycle of rebooting and rejoining
the cluster. After the second time the node went away, the RM produced this:
{code}
2014-07-09 21:47:36,571 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler:
Application attempt appattempt_1404858438119_4352_01 released container
container_1404858438119_4352_01_04 on node: host:
node-A16-R09-19.hadoop.dfw.wordpress.com:8041 #containers=0
available=memory:8192, vCores:8 used=memory:0, vCores:0 with event: KILL
2014-07-09 21:47:36,571 INFO
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler:
Removed node node-A16-R09-19.hadoop.dfw.wordpress.com:8041 cluster capacity:
memory:335872, vCores:328
2014-07-09 21:47:36,571 ERROR
org.apache.hadoop.yarn.YarnUncaughtExceptionHandler: Thread
Thread[ContinuousScheduling,5,main] threw an Exception.
java.lang.NullPointerException
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler$NodeAvailableResourceComparator.compare(FairScheduler.java:1044)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler$NodeAvailableResourceComparator.compare(FairScheduler.java:1040)
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:329)
at java.util.TimSort.sort(TimSort.java:203)
at java.util.TimSort.sort(TimSort.java:173)
at java.util.Arrays.sort(Arrays.java:659)
at java.util.Collections.sort(Collections.java:217)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.continuousScheduling(FairScheduler.java:1012)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler.access$600(FairScheduler.java:124)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler$2.run(FairScheduler.java:1306)
at java.lang.Thread.run(Thread.java:744)
{code}
A few minutes later YARN was crippled. The RM was running and jobs could be
submitted but containers were not assigned and no progress was made. Restarting
the RM resolved it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: Jenkins Build Slaves
Chris, Newer hosts are on ubuntu-14.04 and I'm not aware of any ln related change there. Please let me know if you need any help with debugging the hosts. -giri On Thu, Jul 10, 2014 at 9:53 AM, Chris Nauroth cnaur...@hortonworks.com wrote: Thanks, Giri, for taking care of pkgconfig. It looks like most (all?) pre-commit builds have some new failing tests: https://builds.apache.org/job/PreCommit-HADOOP-Build/4247/testReport/ On the symlink tests, is there any chance that the new hosts have a different version/different behavior for the ln command? The TestIPC failure is in a stress test that checks behavior after spamming a lot of connections at an RPC server. Maybe the new hosts have something different in the TCP stack, such as TCP backlog? I likely won't get a chance to investigate any more today, but I wanted to raise the issue in case someone else gets an opportunity to look. Chris Nauroth Hortonworks http://hortonworks.com/ On Wed, Jul 9, 2014 at 10:33 AM, Giridharan Kesavan gkesa...@hortonworks.com wrote: I dont think so, let me fix that. Thanks Chris for pointing that out. -giri On Wed, Jul 9, 2014 at 9:50 AM, Chris Nauroth cnaur...@hortonworks.com wrote: Hi Giri, Is pkgconfig deployed on the new Jenkins slaves? I noticed this build failed: https://builds.apache.org/job/PreCommit-HADOOP-Build/4237/ Looking in the console output, it appears the HDFS native code failed to build due to missing pkgconfig. [exec] CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message): [exec] Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) Chris Nauroth Hortonworks http://hortonworks.com/ On Wed, Jul 9, 2014 at 7:08 AM, Giridharan Kesavan gkesa...@hortonworks.com wrote: Build jobs are now configured to run on the newer set of slaves. -giri On Mon, Jul 7, 2014 at 4:12 PM, Giridharan Kesavan gkesa...@hortonworks.com wrote: All Yahoo is in the process of retiring all the hadoop jenkins build slaves, *hadoop[1-9]* and replace them with a newer set of beefier hosts. These new machines are configured with *ubuntu-14.04*. Over the next couple of days I will be configuring the build jobs to run on these newly configured build slaves. To automate the installation of tools and build libraries I have put together ansible scripts and here is the link to the toolchain repo. *https://github.com/apache/toolchain https://github.com/apache/toolchain * During the transition, the old build slave will be accessible, and expected to be shutdown by 07/15. I will send out an update later this week when this transition is complete. *Mean while, I would like to request the project owners to remove/cleanup any stale * *jenkins job for their respective project and help with any builds issue to make this * *transition seamless. * Thanks - Giri -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.
Success: YARN-2181 PreCommit Build #4261
Jira: https://issues.apache.org/jira/browse/YARN-2181
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4261/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13079 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12655043/YARN-2181.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4261//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4261//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
52a87af1c49cb52212651716f9c61f6d22283984 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4260
Archived 17 artifacts
Archive block size is 32768
Received 40 blocks and 7196233 bytes
Compression is 15.4%
Took 2.3 sec
Description set: YARN-2181
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-2274) FairScheduler: Add debug information about cluster capacity, availability and reservations
Karthik Kambatla created YARN-2274: -- Summary: FairScheduler: Add debug information about cluster capacity, availability and reservations Key: YARN-2274 URL: https://issues.apache.org/jira/browse/YARN-2274 Project: Hadoop YARN Issue Type: Bug Components: fairscheduler Affects Versions: 2.4.1 Reporter: Karthik Kambatla Assignee: Karthik Kambatla FairScheduler logs have little information on cluster capacity and availability. Need this information to debug production issues. -- This message was sent by Atlassian JIRA (v6.2#6252)
Failed: YARN-2274 PreCommit Build #4262
Jira: https://issues.apache.org/jira/browse/YARN-2274
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4262/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13086 lines...]
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4262//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4262//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
7eed44c31daa9a29eeeb8a04cfa2ad6df49bb941 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4261
Archived 17 artifacts
Archive block size is 32768
Received 49 blocks and 6602181 bytes
Compression is 19.6%
Took 2.6 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
1 tests failed.
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart.testShouldNotCountFailureToMaxAttemptRetry
Error Message:
AppAttempt state is not correct (timedout) expected:ALLOCATED but
was:SCHEDULED
Stack Trace:
java.lang.AssertionError: AppAttempt state is not correct (timedout)
expected:ALLOCATED but was:SCHEDULED
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at
org.apache.hadoop.yarn.server.resourcemanager.MockAM.waitForState(MockAM.java:82)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.sendAMLaunched(MockRM.java:414)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAM(MockRM.java:569)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.launchAndRegisterAM(MockRM.java:576)
at
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart.testShouldNotCountFailureToMaxAttemptRetry(TestAMRestart.java:401)
Failed: YARN-2208 PreCommit Build #4263
Jira: https://issues.apache.org/jira/browse/YARN-2208
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4263/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13266 lines...]
http://issues.apache.org/jira/secure/attachment/12655103/YARN-2208.7.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.util.TestFSDownload
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4263//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4263//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
a7c4b30905e541e06d47a79266bfc0e78992c914 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4261
Archived 22 artifacts
Archive block size is 32768
Received 40 blocks and 7267352 bytes
Compression is 15.3%
Took 2.1 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
1 tests failed.
FAILED:
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache(TestFSDownload.java:363)
Success: YARN-2244 PreCommit Build #4264
Jira: https://issues.apache.org/jira/browse/YARN-2244
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4264/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13069 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12655104/YARN-2244.002.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4264//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4264//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
1db9facc4d0f54ead56e94870df64b43dad26ecd logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4261
Archived 17 artifacts
Archive block size is 32768
Received 45 blocks and 6753991 bytes
Compression is 17.9%
Took 1.8 sec
Description set: YARN-2244
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Resolved] (YARN-2263) CSQueueUtils.computeMaxActiveApplicationsPerUser may cause deadlock for nested MapReduce jobs
[
https://issues.apache.org/jira/browse/YARN-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen He resolved YARN-2263.
---
Resolution: Won't Fix
CSQueueUtils.computeMaxActiveApplicationsPerUser may cause deadlock for
nested MapReduce jobs
-
Key: YARN-2263
URL: https://issues.apache.org/jira/browse/YARN-2263
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 0.23.10, 2.4.1
Reporter: Chen He
computeMaxActiveApplicationsPerUser() has a lower bound 1. For a nested
MapReduce job which files new mapreduce jobs in its mapper/reducer, it will
cause job stuck.
public static int computeMaxActiveApplicationsPerUser(
int maxActiveApplications, int userLimit, float userLimitFactor) {
return Math.max(
(int)Math.ceil(
maxActiveApplications * (userLimit / 100.0f) * userLimitFactor),
1);
}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Failed: YARN-611 PreCommit Build #4265
Jira: https://issues.apache.org/jira/browse/YARN-611
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4265/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13362 lines...]
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.util.TestFSDownload
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4265//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4265//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
b20a0502835d025a0105bb623fd30f9322fa5473 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4264
Archived 27 artifacts
Archive block size is 32768
Received 201 blocks and 2394816 bytes
Compression is 73.3%
Took 1.9 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
2 tests failed.
FAILED:
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.util.TestFSDownload.testDownloadPublicWithStatCache(TestFSDownload.java:363)
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartWaitForPreviousAMToFinish
Error Message:
expected:4 but was:3
Stack Trace:
java.lang.AssertionError: expected:4 but was:3
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testRMRestartWaitForPreviousAMToFinish(TestRMRestart.java:557)
[jira] [Created] (YARN-2276) Branch-2 cannot build
Fengdong Yu created YARN-2276: - Summary: Branch-2 cannot build Key: YARN-2276 URL: https://issues.apache.org/jira/browse/YARN-2276 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.5.0 Reporter: Fengdong Yu [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/yufengdong/svn/letv-hadoop/hadoop-2.0/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/RMAppAttemptMetrics.java:[61,18] error: cannot find symbol -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Issues with documentation on YARN
Thanks for the report! You can create a issue to https://issues.apache.org/jira/browse/YARN and submit a patch. The wiki page describes how to contribute to Apache Hadoop. https://wiki.apache.org/hadoop/HowToContribute Thanks, Akira (2014/07/08 19:54), Никитин Константин wrote: Hi! I'm trying to write my first YARN application using a doc http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/WritingYarnApplications.html . This page is said to describe Apache Hadoop 2.3.0. But a method ``appMasterRequest.setApplicationAttemptId(appAttemptID);`` mentioned there was removed about a year ago https://issues.apache.org/jira/browse/YARN-918 , so Writing Yarn Application is not actual. How can I help with actualizing documentation? Thank you!
[jira] [Resolved] (YARN-2276) Branch-2 cannot build
[ https://issues.apache.org/jira/browse/YARN-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-2276. --- Resolution: Fixed Assignee: Zhijie Shen Merged YARN-2022 into branch-2. Branch-2 cannot build - Key: YARN-2276 URL: https://issues.apache.org/jira/browse/YARN-2276 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.5.0 Reporter: Fengdong Yu Assignee: Zhijie Shen [ERROR] COMPILATION ERROR : [INFO] - [ERROR] hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmapp/attempt/RMAppAttemptMetrics.java:[61,18] error: cannot find symbol -- This message was sent by Atlassian JIRA (v6.2#6252)
Failed: YARN-2274 PreCommit Build #4266
Jira: https://issues.apache.org/jira/browse/YARN-2274
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4266/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 13072 lines...]
http://issues.apache.org/jira/secure/attachment/12655131/yarn-2274-2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4266//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4266//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
5a4579623d9c488dbb37f47edc05fd9dee2ad6fa logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4264
Archived 17 artifacts
Archive block size is 32768
Received 217 blocks and 1110320 bytes
Compression is 86.5%
Took 0.87 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
Re: Issues with documentation on YARN
Hi, To edit the document you mentioned, please edit hadoop-common/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt/WritingYarnApplications.apt.vm The document of apt.vm is written in APT format, which is described in the following document: http://maven.apache.org/doxia/references/apt-format.html After editing, please run the following command and open /tmp/hadoop-site/index.html $ mvn site site:stage -DstagingDirectory=/tmp/hadoop-site $ open /tmp/hadoop-site/hadoop-project/index.html Feel free to ask us if you have any questions about the contribution! Thanks, - Tsuyoshi On Fri, Jul 11, 2014 at 11:14 AM, Akira AJISAKA ajisa...@oss.nttdata.co.jp wrote: Thanks for the report! You can create a issue to https://issues.apache.org/jira/browse/YARN and submit a patch. The wiki page describes how to contribute to Apache Hadoop. https://wiki.apache.org/hadoop/HowToContribute Thanks, Akira (2014/07/08 19:54), Никитин Константин wrote: Hi! I'm trying to write my first YARN application using a doc http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/WritingYarnApplications.html . This page is said to describe Apache Hadoop 2.3.0. But a method ``appMasterRequest.setApplicationAttemptId(appAttemptID);`` mentioned there was removed about a year ago https://issues.apache.org/jira/browse/YARN-918 , so Writing Yarn Application is not actual. How can I help with actualizing documentation? Thank you! -- - Tsuyoshi
[jira] [Created] (YARN-2277) Add JSONP support to the ATS REST API
Jonathan Eagles created YARN-2277: - Summary: Add JSONP support to the ATS REST API Key: YARN-2277 URL: https://issues.apache.org/jira/browse/YARN-2277 Project: Hadoop YARN Issue Type: Sub-task Reporter: Jonathan Eagles As the Application Timeline Server is provided with built-in UI, it may make sense to enable JSONP Rest API capabilities to allow for remote UI to access the data directly via javascript without cross side server browser blocks coming into play. Example client may be like http://api.jquery.com/jQuery.getJSON/ This can alleviate the need to create a local proxy cache. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (YARN-1421) Node managers will not receive application finish event where containers ran before RM restart
[
https://issues.apache.org/jira/browse/YARN-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli resolved YARN-1421.
---
Resolution: Duplicate
Yes, closing as duplicate..
Node managers will not receive application finish event where containers ran
before RM restart
--
Key: YARN-1421
URL: https://issues.apache.org/jira/browse/YARN-1421
Project: Hadoop YARN
Issue Type: Bug
Reporter: Omkar Vinit Joshi
Assignee: Omkar Vinit Joshi
Priority: Critical
Problem :- Today for every application we track the node managers where
containers ran. So when application finishes it notifies all those node
managers about application finish event (via node manager heartbeat). However
if rm restarts then we forget this past information and those node managers
will never get application finish event and will keep reporting finished
applications.
Proposed Solution :- Instead of remembering the node managers where
containers ran for this particular application it would be better if we
depend on node manager heartbeat to take this decision. i.e. when node
manager heartbeats saying it is running application (app1, app2) then we
should check those application's status in RM's memory
{code}rmContext.getRMApps(){code} and if either they are not found (very old
applications) or they are in their final state (FINISHED, KILLED, FAILED)
then we should immediately notify the node manager about the application
finish event. By doing this we are reducing the state which we need to store
at RM after restart.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
