Failed: YARN-2616 PreCommit Build #6508
Jira: https://issues.apache.org/jira/browse/YARN-2616
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6508/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3116 lines...]
/bin/grep:
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/patch:
No such file or directory
cat: /tmp/tmp.modules.8206: No such file or directory
rm: cannot remove '/tmp/tmp.modules.8206': No such file or directory
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696489/YARN-2616-008.patch
against trunk revision ba58da2.
{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:red}-1 eclipse:eclipse{color}. The patch failed to build 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 .
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6508//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6508//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
5025ef13a8dc185eb66a04a88fab94fd4621cdbd logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[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-3094 PreCommit Build #6506
Jira: https://issues.apache.org/jira/browse/YARN-3094
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6506/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3656 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696477/YARN-3094.4.patch
against trunk revision 42548f4.
{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
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestMoveApplication
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6506//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6506//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
e520e5aaa4e7026031e0be82dcc9222a548b53d7 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6493
Archived 20 artifacts
Archive block size is 32768
Received 29 blocks and 8342692 bytes
Compression is 10.2%
Took 1.8 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.server.resourcemanager.TestMoveApplication.testMoveSuccessful
Error Message:
test timed out after 1 milliseconds
Stack Trace:
java.lang.Exception: test timed out after 1 milliseconds
at java.lang.Thread.sleep(Native Method)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.waitForState(MockRM.java:131)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:422)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:314)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:306)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:297)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:290)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:259)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:247)
at
org.apache.hadoop.yarn.server.resourcemanager.MockRM.submitApp(MockRM.java:242)
at
org.apache.hadoop.yarn.server.resourcemanager.TestMoveApplication.testMoveSuccessful(TestMoveApplication.java:128)
Failed: YARN-2683 PreCommit Build #6507
Jira: https://issues.apache.org/jira/browse/YARN-2683
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6507/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4522 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696480/YARN-2683-006.patch
against trunk revision 42548f4.
{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-common-project/hadoop-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6507//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6507//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
2cb1fba0777af93b9606714f1b2e4f816d43b7c9 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6493
Archived 20 artifacts
Archive block size is 32768
Received 10 blocks and 9436086 bytes
Compression is 3.4%
Took 2.4 sec
[description-setter] Could not determine description.
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6506
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-3137) CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock
Jason Lowe created YARN-3137: Summary: CapacityScheduler.checkAccess unnecessarily grabs the scheduler lock Key: YARN-3137 URL: https://issues.apache.org/jira/browse/YARN-3137 Project: Hadoop YARN Issue Type: Bug Affects Versions: 2.5.0 Reporter: Jason Lowe The queues are stored in a ConcurrentHashMap and the code already checks for a null queue. At best we need to lock individual queues when processing the access check, but I don't see why we need to grab the highly-contested scheduler lock to lookup which queue to use for the hasAccess call. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration
Jason Lowe created YARN-3136: Summary: getTransferredContainers can be a bottleneck during AM registration Key: YARN-3136 URL: https://issues.apache.org/jira/browse/YARN-3136 Project: Hadoop YARN Issue Type: Bug Components: scheduler Affects Versions: 2.6.0 Reporter: Jason Lowe While examining RM stack traces on a busy cluster I noticed a pattern of AMs stuck waiting for the scheduler lock trying to call getTransferredContainers. The scheduler lock is highly contended, especially on a large cluster with many nodes heartbeating, and it would be nice if we could find a way to eliminate the need to grab this lock during this call. We've already done similar work during AM allocate calls to make sure they don't needlessly grab the scheduler lock, and it would be good to do so here as well, if possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3138) TestFairScheduler#testContinuousScheduling fails intermittently on trunk
Anubhav Dhoot created YARN-3138: --- Summary: TestFairScheduler#testContinuousScheduling fails intermittently on trunk Key: YARN-3138 URL: https://issues.apache.org/jira/browse/YARN-3138 Project: Hadoop YARN Issue Type: Bug Components: fairscheduler Reporter: Anubhav Dhoot This test failed randomly in a precheckin and passed on rerun https://builds.apache.org/job/PreCommit-YARN-Build/6497//testReport/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3142) Improve locks in AppSchedulingInfo
Wangda Tan created YARN-3142: Summary: Improve locks in AppSchedulingInfo Key: YARN-3142 URL: https://issues.apache.org/jira/browse/YARN-3142 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager, scheduler Reporter: Wangda Tan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-3089 PreCommit Build #6513
Jira: https://issues.apache.org/jira/browse/YARN-3089
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6513/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3110 lines...]
/bin/grep:
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patch:
No such file or directory
cat: /tmp/tmp.modules.17373: No such file or directory
rm: cannot remove '/tmp/tmp.modules.17373': No such file or directory
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696560/YARN-3089.v3.txt
against trunk revision e04e8fa.
{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:red}-1 eclipse:eclipse{color}. The patch failed to build 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 .
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6513//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6513//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
96b65e6cce5c2539e93b663324b40c65d4ad68a5 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[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.
Success: YARN-3101 PreCommit Build #6511
Jira: https://issues.apache.org/jira/browse/YARN-3101
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6511/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3426 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696541/YARN-3101.004.patch
against trunk revision 40a4157.
{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.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6511//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6511//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
bda5df1ae576549fa8d146acfbc0b1699a2ec669 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6509
Archived 15 artifacts
Archive block size is 32768
Received 1 blocks and 8958316 bytes
Compression is 0.4%
Took 4 sec
Description set: YARN-3101
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-2694 PreCommit Build #6510
Jira: https://issues.apache.org/jira/browse/YARN-2694
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6510/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4188 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696524/YARN-2694-20150204-1.patch
against trunk revision 064e077.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 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-client
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.client.TestResourceTrackerOnHA
org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6510//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6510//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
0911df8fb11613361778b4050c18d8016d0ce250 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6509
Archived 30 artifacts
Archive block size is 32768
Received 2 blocks and 9682333 bytes
Compression is 0.7%
Took 2.4 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
11 tests failed.
FAILED:
org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA.testGetContainersOnHA
Error Message:
Call From asf905.gq1.ygridcore.net/67.195.81.149 to
asf905.gq1.ygridcore.net:28032 failed on connection exception:
java.net.ConnectException: Connection refused; For more details see:
http://wiki.apache.org/hadoop/ConnectionRefused
Stack Trace:
java.net.ConnectException: Call From asf905.gq1.ygridcore.net/67.195.81.149 to
asf905.gq1.ygridcore.net:28032 failed on connection exception:
java.net.ConnectException: Connection refused; For more details see:
http://wiki.apache.org/hadoop/ConnectionRefused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
at
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:530)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:494)
at
org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:607)
at
org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:705)
at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:368)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1527)
at org.apache.hadoop.ipc.Client.call(Client.java:1444)
at org.apache.hadoop.ipc.Client.call(Client.java:1405)
at
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
at com.sun.proxy.$Proxy17.getContainers(Unknown Source)
at
org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getContainers(ApplicationClientProtocolPBClientImpl.java:410
[jira] [Resolved] (YARN-3138) TestFairScheduler#testContinuousScheduling fails intermittently on trunk
[ https://issues.apache.org/jira/browse/YARN-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot resolved YARN-3138. - Resolution: Duplicate TestFairScheduler#testContinuousScheduling fails intermittently on trunk Key: YARN-3138 URL: https://issues.apache.org/jira/browse/YARN-3138 Project: Hadoop YARN Issue Type: Bug Components: fairscheduler Reporter: Anubhav Dhoot This test failed randomly in a precheckin and passed on rerun https://builds.apache.org/job/PreCommit-YARN-Build/6497//testReport/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (YARN-3139) Improve locks in AbstractYarnScheduler/CapacityScheduler/FairScheduler
Wangda Tan created YARN-3139: Summary: Improve locks in AbstractYarnScheduler/CapacityScheduler/FairScheduler Key: YARN-3139 URL: https://issues.apache.org/jira/browse/YARN-3139 Project: Hadoop YARN Issue Type: Sub-task Components: resourcemanager, scheduler Reporter: Wangda Tan Assignee: Li Lu Enhance locks in AbstractYarnScheduler/CapacityScheduler/FairScheduler, as mentioned in YARN-3091, a possible solution is using read/write lock. Other fine-graind locks for specific purposes / bugs should be addressed in separated tickets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-2896 PreCommit Build #6512
Jira: https://issues.apache.org/jira/browse/YARN-2896
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6512/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3415 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696539/0005-YARN-2896.patch
against trunk revision 40a4157.
{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:red}-1 findbugs{color}. The patch appears to introduce 1 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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6512//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6512//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-api.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6512//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
151b1ea95983bb63701f862fcc5d9de26dbcf9e9 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6509
Archived 25 artifacts
Archive block size is 32768
Received 1 blocks and 11103283 bytes
Compression is 0.3%
Took 2.9 sec
[description-setter] Could not determine description.
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6511
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-3144) Configuration for making delegation token failures to timeline server not-fatal
Jonathan Eagles created YARN-3144: - Summary: Configuration for making delegation token failures to timeline server not-fatal Key: YARN-3144 URL: https://issues.apache.org/jira/browse/YARN-3144 Project: Hadoop YARN Issue Type: Improvement Reporter: Jonathan Eagles Assignee: Jonathan Eagles Posting events to the timeline server is best-effort. However, getting the delegation tokens from the timeline server will kill the job. This patch adds a configuration to make get delegation token operations best-effort. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Failed: YARN-3143 PreCommit Build #6514
Jira: https://issues.apache.org/jira/browse/YARN-3143
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6514/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3438 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696592/YARN-3143.001.patch
against trunk revision 5f4ef2d.
{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-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6514//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6514//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
bbce7434dd76bce644ee2b189844bffa59ef85bb logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6511
Archived 15 artifacts
Archive block size is 32768
Received 55 blocks and 7190808 bytes
Compression is 20.0%
Took 1.8 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.server.resourcemanager.scheduler.fair.TestFairScheduler.testContinuousScheduling
Error Message:
expected:2 but was:1
Stack Trace:
java.lang.AssertionError: expected:2 but was:1
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.scheduler.fair.TestFairScheduler.testContinuousScheduling(TestFairScheduler.java:3518)
Success: YARN-3144 PreCommit Build #6515
Jira: https://issues.apache.org/jira/browse/YARN-3144
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6515/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3296 lines...]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696603/YARN-3144.1.patch
against trunk revision 5f4ef2d.
{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-api
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6515//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6515//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
4b6308e33429f3fe474ab17d5d6d2585bc6fa8b4 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6511
Archived 20 artifacts
Archive block size is 32768
Received 60 blocks and 7156637 bytes
Compression is 21.6%
Took 2.2 sec
Description set: YARN-3144
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #6514
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-3094 PreCommit Build #6516
Jira: https://issues.apache.org/jira/browse/YARN-3094
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6516/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3123 lines...]
{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 .
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6516//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6516//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
9add81a67e420ecf281c9473ecd2a3d132f561c3 logged out
==
==
Finished build.
==
==
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6515
ERROR: Failed to archive
{patchprocess/patchJavacWarnings.txt=patchprocess/patchJavacWarnings.txt,
patchprocess/trunkJavacWarnings.txt=patchprocess/trunkJavacWarnings.txt,
patchprocess/patchJavadocWarnings.txt=patchprocess/patchJavadocWarnings.txt,
patchprocess/patchFindBugsOutput.txt=patchprocess/patchFindBugsOutput.txt,
patchprocess/masterJavacWarnings.txt=patchprocess/masterJavacWarnings.txt,
patchprocess/trunkJavadocWarnings.txt=patchprocess/trunkJavadocWarnings.txt,
patchprocess/patchReleaseAuditOutput.txt=patchprocess/patchReleaseAuditOutput.txt,
patchprocess/patchReleaseAuditWarnings.txt=patchprocess/patchReleaseAuditWarnings.txt,
patchprocess/masterJavadocWarnings.txt=patchprocess/masterJavadocWarnings.txt,
patchprocess/filteredPatchJavacWarnings.txt=patchprocess/filteredPatchJavacWarnings.txt,
patchprocess/patchEclipseOutput.txt=patchprocess/patchEclipseOutput.txt,
patchprocess/diffJavadocWarnings.txt=patchprocess/diffJavadocWarnings.txt,
patchprocess/filteredmasterJavacWarnings.txt=patchprocess/filteredmasterJavacWarnings.txt,
patchprocess/filteredTrunkJavacWarnings.txt=patchprocess/filteredTrunkJavacWarnings.txt}
due to internal error; falling back to full archiving
java.lang.IllegalStateException: checksum mismatch after transfer
(6577874794637500426 vs. 2360665305);
/x1/jenkins/jenkins-home/jobs/PreCommit-YARN-Build/builds/2015-02-05_01-30-22/archive/patchprocess/patchFindBugsOutput.txt
may be corrupted
at jsync.protocol.FileSequenceReader.read(FileSequenceReader.java:45)
at
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.remoteSync(JSyncArtifactManager.java:145)
at
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.archive(JSyncArtifactManager.java:68)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
at
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
at hudson.model.Build$BuildExecution.post2(Build.java:182)
at
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
at hudson.model.Run.execute(Run.java:1731)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Description set: YARN-3094
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
Failed: YARN-3145 PreCommit Build #6517
Jira: https://issues.apache.org/jira/browse/YARN-3145
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6517/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3439 lines...]
http://issues.apache.org/jira/secure/attachment/12696681/YARN-3145.001.patch
against trunk revision 0b567f4.
{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.recovery.TestFSRMStateStore
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6517//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6517//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
230d590a01c549186d5b9d538e972505d4dbb8c5 logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6515
Archived 15 artifacts
Archive block size is 32768
Received 50 blocks and 7352532 bytes
Compression is 18.2%
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)
##
1 tests failed.
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry
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.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry(TestFSRMStateStore.java:289)
Hadoop-Yarn-trunk - Build # 828 - Failure
See https://builds.apache.org/job/Hadoop-Yarn-trunk/828/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7297 lines...] [INFO] [INFO] hadoop-yarn ... SUCCESS [ 3.693 s] [INFO] hadoop-yarn-api ... SUCCESS [03:21 min] [INFO] hadoop-yarn-common SUCCESS [02:43 min] [INFO] hadoop-yarn-server SUCCESS [ 0.091 s] [INFO] hadoop-yarn-server-common . SUCCESS [ 41.103 s] [INFO] hadoop-yarn-server-nodemanager FAILURE [05:14 min] [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-server-sharedcachemanager . 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-registry .. SKIPPED [INFO] hadoop-yarn-project ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 12:05 min [INFO] Finished at: 2015-02-04T10:44:21+00:00 [INFO] Final Memory: 86M/1148M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project hadoop-yarn-server-nodemanager: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/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-server-nodemanager Build step 'Execute shell' marked build as failure Archiving artifacts Recording test results Updating YARN-3098 Updating YARN-3085 Updating YARN-2543 Updating HDFS-7707 Updating HDFS-7712 Updating YARN-1393 Updating MAPREDUCE-5800 Updating YARN-3058 Updating YARN-3022 Updating HDFS-7721 Updating HADOOP-11529 Updating YARN-3056 Updating HADOOP-11045 Updating YARN-3075 Sending e-mails to: yarn-dev@hadoop.apache.org Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 5 tests failed. REGRESSION: org.apache.hadoop.yarn.server.nodemanager.TestNodeManagerResync.testNMshutdownWhenResyncThrowException Error Message: java.net.BindException: Problem binding to [localhost:12345] java.net.BindException: Address already in use; For more details see: http://wiki.apache.org/hadoop/BindException Stack Trace: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: java.net.BindException: Problem binding to [localhost:12345] java.net.BindException: Address already in use; For more details see: http://wiki.apache.org/hadoop/BindException at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:444) at sun.nio.ch.Net.bind(Net.java:436) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at org.apache.hadoop.ipc.Server.bind(Server.java:411) at org.apache.hadoop.ipc.Server$Listener.init(Server.java:577) at org.apache.hadoop.ipc.Server.init(Server.java:2300) at org.apache.hadoop.ipc.RPC$Server.init(RPC.java:942) at org.apache.hadoop.ipc.ProtobufRpcEngine$Server.init(ProtobufRpcEngine.java:534) at org.apache.hadoop.ipc.ProtobufRpcEngine.getServer(ProtobufRpcEngine.java:509) at org.apache.hadoop.ipc.RPC$Builder.build(RPC.java:787) at
Build failed in Jenkins: Hadoop-Yarn-trunk #828
See https://builds.apache.org/job/Hadoop-Yarn-trunk/828/changes Changes: [jlowe] YARN-3085. Application summary should include the application type. Contributed by Rohith [ozawa] HADOOP-11045. Introducing a tool to detect flaky tests of hadoop jenkins testing job. Contributed by Yongjun Zhang and Todd Lipcon. [rkanter] YARN-3022. Expose Container resource information from NodeManager for monitoring (adhoot via ranter) [wheat9] HADOOP-11529. Fix findbugs warnings in hadoop-archives. Contributed by Masatake Iwasaki. [cmccabe] HDFS-7721. The HDFS BlockScanner may run fast during the first hour (cmccabe) [jianhe] YARN-3098. Created common QueueCapacities class in Capacity Scheduler to track capacities-by-labels of queues. Contributed by Wangda Tan [kihwal] HDFS-7707. Edit log corruption due to delayed block removal again. Contributed by Yongjun Zhang [wangda] YARN-3075. NodeLabelsManager implementation to retrieve label to node mapping (Varun Saxena via wangda) [kasha] YARN-1393. SLS: Add how-to-use instructions. (Wei Yan via kasha) [aajisaka] MAPREDUCE-5800. Use Job#getInstance instead of deprecated constructors. (aajisaka) [wang] HDFS-7712. Switch blockStateChangeLog to use slf4j. [xgong] YARN-3056. Add verification for containerLaunchDuration in [zjshen] YARN-2543. Made resource usage be published to the timeline server too. Contributed by Naganarasimha G R. [ozawa] YARN-3058. Fix error message of tokens' activation delay configuration. Contributed by Yi Liu. -- [...truncated 7104 lines...] at sun.nio.ch.Net.bind(Net.java:444) at sun.nio.ch.Net.bind(Net.java:436) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at org.apache.hadoop.ipc.Server.bind(Server.java:411) at org.apache.hadoop.ipc.Server$Listener.init(Server.java:577) at org.apache.hadoop.ipc.Server.init(Server.java:2300) at org.apache.hadoop.ipc.RPC$Server.init(RPC.java:942) at org.apache.hadoop.ipc.ProtobufRpcEngine$Server.init(ProtobufRpcEngine.java:534) at org.apache.hadoop.ipc.ProtobufRpcEngine.getServer(ProtobufRpcEngine.java:509) at org.apache.hadoop.ipc.RPC$Builder.build(RPC.java:787) at org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.createServer(RpcServerFactoryPBImpl.java:169) at org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.getServer(RpcServerFactoryPBImpl.java:132) at org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC.getServer(HadoopYarnProtoRPC.java:65) at org.apache.hadoop.yarn.ipc.YarnRPC.getServer(YarnRPC.java:54) at org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.serviceStart(ContainerManagerImpl.java:420) at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193) at org.apache.hadoop.service.CompositeService.serviceStart(CompositeService.java:120) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceStart(NodeManager.java:264) at org.apache.hadoop.service.AbstractService.start(AbstractService.java:193) at org.apache.hadoop.yarn.server.nodemanager.TestNodeManagerResync.testBlockNewContainerRequestsOnStartAndResync(TestNodeManagerResync.java:170) testKillContainersOnResync(org.apache.hadoop.yarn.server.nodemanager.TestNodeManagerResync) Time elapsed: 0.089 sec ERROR! org.apache.hadoop.yarn.exceptions.YarnRuntimeException: java.net.BindException: Problem binding to [localhost:12345] java.net.BindException: Address already in use; For more details see: http://wiki.apache.org/hadoop/BindException at sun.nio.ch.Net.bind0(Native Method) at sun.nio.ch.Net.bind(Net.java:444) at sun.nio.ch.Net.bind(Net.java:436) at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) at org.apache.hadoop.ipc.Server.bind(Server.java:411) at org.apache.hadoop.ipc.Server$Listener.init(Server.java:577) at org.apache.hadoop.ipc.Server.init(Server.java:2300) at org.apache.hadoop.ipc.RPC$Server.init(RPC.java:942) at org.apache.hadoop.ipc.ProtobufRpcEngine$Server.init(ProtobufRpcEngine.java:534) at org.apache.hadoop.ipc.ProtobufRpcEngine.getServer(ProtobufRpcEngine.java:509) at org.apache.hadoop.ipc.RPC$Builder.build(RPC.java:787) at org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.createServer(RpcServerFactoryPBImpl.java:169) at org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl.getServer(RpcServerFactoryPBImpl.java:132) at org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC.getServer(HadoopYarnProtoRPC.java:65) at org.apache.hadoop.yarn.ipc.YarnRPC.getServer(YarnRPC.java:54) at
Build failed in Jenkins: Hadoop-Yarn-trunk-Java8 #94
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/94/changes Changes: [jlowe] YARN-3085. Application summary should include the application type. Contributed by Rohith [ozawa] HADOOP-11045. Introducing a tool to detect flaky tests of hadoop jenkins testing job. Contributed by Yongjun Zhang and Todd Lipcon. [rkanter] YARN-3022. Expose Container resource information from NodeManager for monitoring (adhoot via ranter) [wheat9] HADOOP-11529. Fix findbugs warnings in hadoop-archives. Contributed by Masatake Iwasaki. [cmccabe] HDFS-7721. The HDFS BlockScanner may run fast during the first hour (cmccabe) [jianhe] YARN-3098. Created common QueueCapacities class in Capacity Scheduler to track capacities-by-labels of queues. Contributed by Wangda Tan [kihwal] HDFS-7707. Edit log corruption due to delayed block removal again. Contributed by Yongjun Zhang [wangda] YARN-3075. NodeLabelsManager implementation to retrieve label to node mapping (Varun Saxena via wangda) [kasha] YARN-1393. SLS: Add how-to-use instructions. (Wei Yan via kasha) [aajisaka] MAPREDUCE-5800. Use Job#getInstance instead of deprecated constructors. (aajisaka) [wang] HDFS-7712. Switch blockStateChangeLog to use slf4j. [xgong] YARN-3056. Add verification for containerLaunchDuration in [zjshen] YARN-2543. Made resource usage be published to the timeline server too. Contributed by Naganarasimha G R. [ozawa] YARN-3058. Fix error message of tokens' activation delay configuration. Contributed by Yi Liu. -- [...truncated 4160 lines...] Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.container.TestContainer Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.691 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.container.TestContainer Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.TestNMProxy Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.206 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.TestNMProxy Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestLogAggregationService Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 30.652 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.logaggregation.TestLogAggregationService Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.799 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainerMetrics Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.844 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainerMetrics Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainersMonitor Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.787 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainersMonitor Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.TestNonAggregatingLogHandler Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.231 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.TestNonAggregatingLogHandler Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.TestAuxServices Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.728 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.TestAuxServices Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManagerRecovery Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.536 sec - in org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManagerRecovery Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; support was removed in 8.0 Running
Re: QueueMetrics.AppsKilled/Failed metrics and failure reasons
Thanks for your inputs. The cluster Metrics API is giving correct numbers for the failed/killed apps and is matching with the RM audit logs and we are planning to use that instead. Suma On Wed, Feb 4, 2015 at 12:04 PM, Rohith Sharma K S rohithsharm...@huawei.com wrote: There are several ways to confirm from YARN that total number of Killed/Failed applications in cluster 1. Get from RM web UI lists OR 2. From admin try using this to get numbers of failed and killed applications: ./yarn application -list -appStates FAILED,KILLED 3. Using client API's Since metrics values are displayed in ganglia is incorrect, I get doubt that 1. does ganglia is pointing out to correct RM cluster? Or 2. what is the method ganglia uses to retrieve QueueMetrics? 3. Any client program calculates you have written retrieve apps and calculate it? Thanks Regards Rohith Sharma K S -Original Message- From: Suma Shivaprasad [mailto:sumasai.shivapra...@gmail.com] Sent: 04 February 2015 11:03 To: u...@hadoop.apache.org Cc: yarn-dev@hadoop.apache.org Subject: Re: QueueMetrics.AppsKilled/Failed metrics and failure reasons Using hadoop 2.4.0. #of Applications running on average is small ~ 40 -60. The metrics in Ganglia shows around around 10-30 apps killed every 5 mins which is very high wrt to the apps running at any given time(40-60). The RM logs though show 0 failed apps in audit logs during that hour. The RM UI also doesnt show any apps in Applications-Failed tab . The logs are getting rolled over at a slower rate ..every 1-2 hours. Am searching for Application Finished - Failed to find the apps failed. Please let me know if I am missing something here. Thanks Suma On Wed, Feb 4, 2015 at 10:03 AM, Rohith Sharma K S rohithsharm...@huawei.com wrote: Hi Could you give more information, which version of hadoop are you using? QueueMetrics.AppsKilled/Failed metrics shows much higher nos i.e ~100. However RMAuditLogger shows 1 or 2 Apps as Killed/Failed in the logs. May be I suspect that Logs might be rolled out. Does more applications are running? All the applications history will be displayed on RM web UI (provided RM is not restarted or RM recovery enabled). May be you can check these applications lists. For finding reasons for application killed/failed, one way is you can check in NodeManager logs also. Here you need to check using container_id for corresponding application. Thanks Regards Rohith Sharma K S *From:* Suma Shivaprasad [mailto:sumasai.shivapra...@gmail.com] *Sent:* 03 February 2015 21:35 *To:* u...@hadoop.apache.org; yarn-dev@hadoop.apache.org *Subject:* QueueMetrics.AppsKilled/Failed metrics and failure reasons Hello, Was trying to debug reasons for Killed/Failed apps and was checking for the applications that were killed/failed in RM logs - from RMAuditLogger. QueueMetrics.AppsKilled/Failed metrics shows much higher nos i.e ~100. However RMAuditLogger shows 1 or 2 Apps as Killed/Failed in the logs. Is it possible that some logs are missed by AuditLogger or is it the other way round and metrics are being reported higher ? Thanks Suma
[jira] [Created] (YARN-3135) There should be an easier way to submit Java-based YARN applications
Jens Rabe created YARN-3135:
---
Summary: There should be an easier way to submit Java-based YARN
applications
Key: YARN-3135
URL: https://issues.apache.org/jira/browse/YARN-3135
Project: Hadoop YARN
Issue Type: Improvement
Components: api
Reporter: Jens Rabe
Since YARN is designed to not only work with Java, it is quite difficult and
cumbersome to correctly setup a YARN application. For Java-based ones, it
should be easier; there should be something like the MR2 Job API. My proposal
is the following:
# Have a basic Job / Application object, e.g. YarnApplication, which could be
instantiated and configured the following:
{code:java}
final Configuration conf = ...
final YarnApplication app = YarnApplication.getInstance(conf);
app.setContainerClassName(MyContainer.class);
app.setJarByClass(MyContainer.class);
{code}
# There should be a means to send and receive messages between container and
AppMaster
# The container should be able to report progress and state to the AppMaster
# Bonus: A simplified WebAppMaster should start a web application and have its
URL automatically proxied when run
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (YARN-3145) ConcurrentModificationException on ParentQueue#getQueueUserAclInfo
Jian He created YARN-3145:
-
Summary: ConcurrentModificationException on
ParentQueue#getQueueUserAclInfo
Key: YARN-3145
URL: https://issues.apache.org/jira/browse/YARN-3145
Project: Hadoop YARN
Issue Type: Bug
Reporter: Jian He
{code}
ava.util.ConcurrentModificationException(java.util.ConcurrentModificationException
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1115)
at java.util.TreeMap$KeyIterator.next(TreeMap.java:1169)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.getQueueUserAclInfo(ParentQueue.java:347)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue.getQueueUserAclInfo(ParentQueue.java:348)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.getQueueUserAclInfo(CapacityScheduler.java:850)
at
org.apache.hadoop.yarn.server.resourcemanager.ClientRMService.getQueueUserAcls(ClientRMService.java:844)
at
org.apache.hadoop.yarn.api.impl.pb.service.ApplicationClientProtocolPBServiceImpl.getQueueUserAcls(ApplicationClientProtocolPBServiceImpl.java:250)
at
org.apache.hadoop.yarn.proto.ApplicationClientProtocol$ApplicationClientProtocolService$2.callBlockingMethod(ApplicationClientProtocol.java:335)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
