[jira] [Created] (YARN-2337) remove duplication function call (setClientRMService) in resource manage class

2014-07-23 Thread zhihai xu (JIRA) 
zhihai xu created YARN-2337:
---

 Summary: remove duplication function call (setClientRMService) in 
resource manage class
 Key: YARN-2337
 URL: https://issues.apache.org/jira/browse/YARN-2337
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: resourcemanager
Reporter: zhihai xu
Priority: Minor


remove duplication function call (setClientRMService) in resource manage class.
rmContext.setClientRMService(clientRM); is duplicate in serviceInit of 
ResourceManager. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (YARN-2338) service assemble so complex

2014-07-23 Thread tangjunjie (JIRA) 
tangjunjie created YARN-2338:


 Summary: service assemble so complex
 Key: YARN-2338
 URL: https://issues.apache.org/jira/browse/YARN-2338
 Project: Hadoop YARN
  Issue Type: Wish
Reporter: tangjunjie


  See ResourceManager
protected void serviceInit(Configuration configuration) throws Exception 

So many service will assembe into resourcemanager.

Use guice or other service assemble framework to refactor this complex code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Failed: YARN-2284 PreCommit Build #4399

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2284
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4399/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 14305 lines...]
  http://issues.apache.org/jira/secure/attachment/12657289/YARN2284-03.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-common-project/hadoop-common 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common:

  org.apache.hadoop.ipc.TestIPC

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/4399//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4399//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
3b4be704fa791f1eb9cf0c0c8182cc61263676d9 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4397
Archived 27 artifacts
Archive block size is 32768
Received 39 blocks and 8125905 bytes
Compression is 13.6%
Took 2.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.ipc.TestIPC.testRetryProxy

Error Message:
test timed out after 6 milliseconds

Stack Trace:
java.lang.Exception: test timed out after 6 milliseconds
at java.net.Inet4AddressImpl.getLocalHostName(Native Method)
at java.net.InetAddress.getLocalHost(InetAddress.java:1374)
at org.apache.hadoop.net.NetUtils.getConnectAddress(NetUtils.java:372)
at org.apache.hadoop.net.NetUtils.getConnectAddress(NetUtils.java:359)
at 
org.apache.hadoop.ipc.TestIPC$TestInvocationHandler.invoke(TestIPC.java:212)
at org.apache.hadoop.ipc.$Proxy11.dummyRun(Unknown Source)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:186)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:101)
at org.apache.hadoop.ipc.$Proxy11.dummyRun(Unknown Source)
at org.apache.hadoop.ipc.TestIPC.testRetryProxy(TestIPC.java:1060)

[jira] [Created] (YARN-2339) service assemble so complex

2014-07-23 Thread tangjunjie (JIRA) 
tangjunjie created YARN-2339:


 Summary: service assemble so complex
 Key: YARN-2339
 URL: https://issues.apache.org/jira/browse/YARN-2339
 Project: Hadoop YARN
  Issue Type: Wish
Reporter: tangjunjie


  See ResourceManager
protected void serviceInit(Configuration configuration) throws Exception 

So many service will assembe into resourcemanager.

Use guice or other service assemble framework to refactor this complex code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (YARN-2339) service assemble so complex

2014-07-23 Thread tangjunjie (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

tangjunjie resolved YARN-2339.
--

Resolution: Duplicate

> service assemble so complex
> ---
>
> Key: YARN-2339
> URL: https://issues.apache.org/jira/browse/YARN-2339
> Project: Hadoop YARN
>  Issue Type: Wish
>Reporter: tangjunjie
>
>   See ResourceManager
> protected void serviceInit(Configuration configuration) throws Exception 
> So many service will assembe into resourcemanager.
> Use guice or other service assemble framework to refactor this complex code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Failed: YARN-2328 PreCommit Build #4400

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2328
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4400/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 10111 lines...]
==
==
Testing patch for YARN-2328.
==
==


Updating '.':
At revision 1612796.
YARN-2328 patch is being downloaded at Wed Jul 23 08:35:28 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12657303/yarn-2328-2.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12657303/yarn-2328-2.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4400//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
de6ea39ea5bb82c11e4463be542ef9050ba66cec logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4397
Archived 2 artifacts
Archive block size is 32768
Received 0 blocks and 68116 bytes
Compression is 0.0%
Took 0.19 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-2337 PreCommit Build #4401

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2337
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4401/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13114 lines...]
  http://issues.apache.org/jira/secure/attachment/12657305/YARN-2337.000.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/4401//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4401//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
3ab64d3be22913957f0d5043580ec38d54897647 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4397
Archived 17 artifacts
Archive block size is 32768
Received 44 blocks and 6779495 bytes
Compression is 17.5%
Took 4.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) 
##
All tests passed

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

2014-07-23 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Yarn-trunk/621/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 15340 lines...]
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-yarn ... SUCCESS [  3.326 s]
[INFO] hadoop-yarn-api ... SUCCESS [02:20 min]
[INFO] hadoop-yarn-common  SUCCESS [02:09 min]
[INFO] hadoop-yarn-server  SUCCESS [  0.090 s]
[INFO] hadoop-yarn-server-common . SUCCESS [ 37.732 s]
[INFO] hadoop-yarn-server-nodemanager  SUCCESS [05:02 min]
[INFO] hadoop-yarn-server-web-proxy .. FAILURE [01:13 min]
[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: 11:29 min
[INFO] Finished at: 2014-07-23T10:57:14+00:00
[INFO] Final Memory: 80M/995M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on 
project hadoop-yarn-server-web-proxy: 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-server/hadoop-yarn-server-web-proxy/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  -rf :hadoop-yarn-server-web-proxy
Build step 'Execute shell' marked build as failure
Archiving artifacts
Updating YARN-2273
Updating YARN-2313
Updating HDFS-6703
Updating YARN-2295
Updating HADOOP-10826
Updating HDFS-6704
Updating HDFS-6701
Updating HDFS-6712
Updating HDFS-6731
Updating HADOOP-10855
Updating HADOOP-10881
Updating YARN-2131
Updating HADOOP-10864
Updating MAPREDUCE-5963
Updating YARN-2319
Updating YARN-2242
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 #621

2014-07-23 Thread Apache Jenkins Server 
See 

Changes:

[sandy] YARN-2313. Livelock can occur in FairScheduler when there are lots of 
running apps (Tsuyoshi Ozawa via Sandy Ryza)

[wang] HADOOP-10881. Clarify usage of encryption and encrypted encryption key 
in KeyProviderCryptoExtension. (wang)

[todd] HADOOP-10855. Allow Text to be read with a known Length. Contributed by 
Todd Lipcon.

[kasha] YARN-2273. NPE in ContinuousScheduling thread when we lose a node. (Wei 
Yan via kasha)

[brandonli] HDFS-6731. Run 'hdfs zkfc -formatZK' on a server in a non-namenode 
will cause a null pointer exception. Contributed by Masatake Iwasaki

[brandonli] HDFS-6703. NFS: Files can be deleted from a read-only mount. 
Contributed by Srikanth Upputuri

[arp] HDFS-6712. Document HDFS Multihoming Settings. (Contributed by Arpit 
Agarwal)

[jlowe] MAPREDUCE-5963. ShuffleHandler DB schema should be versioned with 
compatible/incompatible changes. Contributed by Junping Du

[kasha] YARN-2131. Addendum2: Document -format-state-store. Add a way to format 
the RMStateStore. (Robert Kanter via kasha)

[jianhe] YARN-2295. Refactored DistributedShell to use public APIs of protocol 
records. Contributed by Li Lu

[wang] HDFS-6701. Make seed optional in NetworkTopology#sortByDistance. 
Contributed by Ashwin Shankar.

[jing9] HDFS-6704. Fix the command to launch JournalNode in HDFS-HA document. 
Contributed by Akira AJISAKA.

[arp] HADOOP-10864. Tool documentenation is broken. (Contributed by Akira 
Ajisaka)

[tucu] HADOOP-10826. Iteration on KeyProviderFactory.serviceLoader is 
thread-unsafe. (benoyantony viat tucu)

[zjshen] YARN-2319. Made the MiniKdc instance start/close before/after the 
class of TestRMWebServicesDelegationTokens. Contributed by Wenwu Peng.

[junping_du] YARN-2242. Addendum patch. Improve exception information on AM 
launch crashes. (Contributed by Li Lu)

--
[...truncated 15147 lines...]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:408)
at java.net.ServerSocket.implAccept(ServerSocket.java:462)
at java.net.ServerSocket.accept(ServerSocket.java:430)
at org.mortbay.jetty.bio.SocketConnector.accept(SocketConnector.java:99)
at 
org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:708)
at 
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
"main"  prio=5 tid=1 runnable
java.lang.Thread.State: RUNNABLE
at java.lang.Thread.dumpThreads(Native Method)
at java.lang.Thread.getAllStackTraces(Thread.java:1530)
at 
org.apache.hadoop.test.TimedOutTestsListener.buildThreadDump(TimedOutTestsListener.java:86)
at 
org.apache.hadoop.test.TimedOutTestsListener.buildThreadDiagnosticString(TimedOutTestsListener.java:72)
at 
org.apache.hadoop.test.TimedOutTestsListener.testFailure(TimedOutTestsListener.java:61)
at 
org.junit.runner.notification.RunNotifier$4.notifyListener(RunNotifier.java:139)
at 
org.junit.runner.notification.RunNotifier$SafeNotifier.run(RunNotifier.java:61)
at 
org.junit.runner.notification.RunNotifier.fireTestFailures(RunNotifier.java:134)
at 
org.junit.runner.notification.RunNotifier.fireTestFailure(RunNotifier.java:128)
at 
org.junit.internal.runners.model.EachTestNotifier.addFailure(EachTestNotifier.java:23)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:275)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
"Thread-3"  prio=5 tid=11 runnable
java.lang.Thread.State: RUNN

Failed: YARN-2328 PreCommit Build #4402

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2328
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4402/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13145 lines...]
  http://issues.apache.org/jira/secure/attachment/12657329/yarn-2328-2.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-server/hadoop-yarn-server-resourcemanager:

  
org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/4402//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4402//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
c757c2288f8c954ce9e1cd301d8c7d14b226 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4397
Archived 17 artifacts
Archive block size is 32768
Received 42 blocks and 6865735 bytes
Compression is 16.7%
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.
REGRESSION:  
org.apache.hadoop.yarn.server.resourcemanager.TestWorkPreservingRMRestart.testRecoverSchedulerAppAndAttemptSynchronously[0]

Error Message:
test timed out after 2 milliseconds

Stack Trace:
java.lang.Exception: test timed out after 2 milliseconds
at java.net.Inet4AddressImpl.getLocalHostName(Native Method)
at java.net.InetAddress.getLocalHost(InetAddress.java:1374)
at org.apache.hadoop.net.NetUtils.getConnectAddress(NetUtils.java:372)
at 
org.apache.hadoop.yarn.webapp.util.WebAppUtils.getResolvedAddress(WebAppUtils.java:154)
at 
org.apache.hadoop.yarn.webapp.util.WebAppUtils.getResolvedRMWebAppURLWithoutScheme(WebAppUtils.java:150)
at 
org.apache.hadoop.yarn.webapp.util.WebAppUtils.getResolvedRMWebAppURLWithoutScheme(WebAppUtils.java:132)
at 
org.apache.hadoop.yarn.webapp.util.WebAppUtils.getProxyHostAndPort(WebAppUtils.java:121)
at 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl.generateProxyUriWithScheme(RMAppAttemptImpl.java:522)
at 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl.(RMAppAttemptImpl.java:426)
at 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.createNewAttempt(RMAppImpl.java:683)
at 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.recover(RMAppImpl.java:675)
at 
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recoverApplication(RMAppManager.java:312)
at 
org.apache.hadoop.yarn.server.resourcemanager.RMAppManager.recover(RMAppManager.java:425)
at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.recover(ResourceManager.java:1030)
at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMActiveServices.serviceStart(ResourceManager.java:489)
at 
org.apache.hadoop.service.AbstractService.start(AbstractService.java:193)
at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.startActiveServices(ResourceManage

Re: [DISCUSS] Assume Private-Unstable for classes that are not annotated

2014-07-23 Thread Tsuyoshi OZAWA 
+1 for Karthik's suggestion.

- Tsuyoshi

On Wed, Jul 23, 2014 at 6:54 AM, Karthik Kambatla  wrote:
> Hi devs
>
> As you might have noticed, we have several classes and methods in them that
> are not annotated at all. This is seldom intentional. Avoiding incompatible
> changes to all these classes can be considerable baggage.
>
> I was wondering if we should add an explicit disclaimer in our
> compatibility guide that says, "Classes without annotations are to
> considered @Private"
>
> For methods, is it reasonable to say - "Class members without specific
> annotations inherit the annotations of the class"?
>
> Thanks
> Karthik



-- 
- Tsuyoshi

Success: YARN-2336 PreCommit Build #4403

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2336
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4403/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13116 lines...]


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12657339/YARN-2336-2.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/4403//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4403//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
93f29f91d27e7a0a5b686ae01c0a8a653a8d8e5c logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4397
Archived 17 artifacts
Archive block size is 32768
Received 42 blocks and 6864818 bytes
Compression is 16.7%
Took 2.3 sec
Description set: YARN-2336
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

Re: [DISCUSS] Assume Private-Unstable for classes that are not annotated

2014-07-23 Thread Jason Lowe 
I think that's a reasonable proposal as long as we understand it changes 
the burden from finding all the things that should be marked @Private to 
finding all the things that should be marked @Public. As Tom Graves 
pointed out in an earlier discussion about @LimitedPrivate, it may be 
impossible to do a straightforward task and use only interfaces marked 
@Public.  If users can't do basic things without straying from @Public 
interfaces then tons of code can break if we assume it's always fair 
game to change anything not marked @Public.  The "well you shouldn't 
have used a non-@Public interface" argument is not very useful in that 
context.


So as long as we're good about making sure officially supported features 
have corresponding @Public interfaces to wield them then I agree it will 
be easier to track those rather than track all the classes that should 
be @Private.  Hopefully if users understand that's how things work 
they'll help file JIRAs for interfaces that need to be @Public to get 
their work done.


Jason

On 07/22/2014 04:54 PM, Karthik Kambatla wrote:

Hi devs

As you might have noticed, we have several classes and methods in them that
are not annotated at all. This is seldom intentional. Avoiding incompatible
changes to all these classes can be considerable baggage.

I was wondering if we should add an explicit disclaimer in our
compatibility guide that says, "Classes without annotations are to
considered @Private"

For methods, is it reasonable to say - "Class members without specific
annotations inherit the annotations of the class"?

Thanks
Karthik

Failed: YARN-1063 PreCommit Build #4404

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-1063
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4404/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 10111 lines...]
==
==
Testing patch for YARN-1063.
==
==


Updating '.':
At revision 1612840.
YARN-1063 patch is being downloaded at Wed Jul 23 14:31:13 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12657356/YARN-1063.5.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12657356/YARN-1063.5.patch
  against trunk revision .

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4404//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
19db146f681bf0b60b3d90bb631578db79bd9a01 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4403
Archived 2 artifacts
Archive block size is 32768
Received 0 blocks and 197966 bytes
Compression is 0.0%
Took 0.38 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.

[jira] [Created] (YARN-2340) NPE thrown when RM restart after queue is STOPPED

2014-07-23 Thread Nishan Shetty (JIRA) 
Nishan Shetty created YARN-2340:
---

 Summary: NPE thrown when RM restart after queue is STOPPED
 Key: YARN-2340
 URL: https://issues.apache.org/jira/browse/YARN-2340
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager, scheduler
Affects Versions: 2.4.1
 Environment: Capacityscheduler with Queue a, b

Reporter: Nishan Shetty
Priority: Critical


While job is in progress make Queue  state as STOPPED and then restart RM 

Observe that standby RM fails to come up as acive throwing below NPE

2014-07-23 18:43:24,432 INFO 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: 
appattempt_1406116264351_0014_02 State change from NEW to SUBMITTED
2014-07-23 18:43:24,433 FATAL 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in 
handling event type APP_ATTEMPT_ADDED to the scheduler
java.lang.NullPointerException
 at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.addApplicationAttempt(CapacityScheduler.java:568)
 at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:916)
 at 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:101)
 at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:602)
 at java.lang.Thread.run(Thread.java:662)
2014-07-23 18:43:24,434 INFO 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Exiting, bbye..





--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (YARN-2340) NPE thrown when RM restart after queue is STOPPED

2014-07-23 Thread Nishan Shetty (JIRA) 

 [ 
https://issues.apache.org/jira/browse/YARN-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishan Shetty resolved YARN-2340.
-

Resolution: Unresolved

> NPE thrown when RM restart after queue is STOPPED
> -
>
> Key: YARN-2340
> URL: https://issues.apache.org/jira/browse/YARN-2340
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: resourcemanager, scheduler
>Affects Versions: 2.4.1
> Environment: Capacityscheduler with Queue a, b
>Reporter: Nishan Shetty
>Priority: Critical
>
> While job is in progress make Queue  state as STOPPED and then restart RM 
> Observe that standby RM fails to come up as acive throwing below NPE
> 2014-07-23 18:43:24,432 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: 
> appattempt_1406116264351_0014_02 State change from NEW to SUBMITTED
> 2014-07-23 18:43:24,433 FATAL 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in 
> handling event type APP_ATTEMPT_ADDED to the scheduler
> java.lang.NullPointerException
>  at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.addApplicationAttempt(CapacityScheduler.java:568)
>  at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:916)
>  at 
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.handle(CapacityScheduler.java:101)
>  at 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher$EventProcessor.run(ResourceManager.java:602)
>  at java.lang.Thread.run(Thread.java:662)
> 2014-07-23 18:43:24,434 INFO 
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Exiting, bbye..



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Success: YARN-1342 PreCommit Build #4406

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-1342
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4406/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13252 lines...]

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12657361/YARN-1342v6.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 4 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-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/4406//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4406//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
1d7f84c3913452d2d14eb7bad2dbea4fafa9e7cb logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4403
Archived 22 artifacts
Archive block size is 32768
Received 220 blocks and 1185783 bytes
Compression is 85.9%
Took 0.69 sec
Description set: YARN-1342
Recording test results
Publish JUnit test result report is waiting for a checkpoint on 
PreCommit-YARN-Build #4405
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

Success: YARN-2247 PreCommit Build #4405

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2247
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4405/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13458 lines...]


{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12657359/apache-yarn-2247.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 2 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-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common 
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/4405//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4405//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
e8e3ea77897718fe513eb6c03fe83d21e1735344 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4403
Archived 32 artifacts
Archive block size is 32768
Received 48 blocks and 7445916 bytes
Compression is 17.4%
Took 2.8 sec
Description set: YARN-2247
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

Re: [DISCUSS] Assume Private-Unstable for classes that are not annotated

2014-07-23 Thread Karthik Kambatla 
Fair points, Jason.

The fact that we include this in the compatibility guideline "should not"
affect how developers go about this. We should still strive to annotate
every new class we add, and reviewers should continue to check for them.
However, in case we miss annotations, we won't be burdened to support those
APIs for essentially eternity.

I am aware of downstream projects that use @Private APIs, but I have also
seen that improve in the recent past with compatible 2.x releases. So, I am
hoping they will let us know of APIs they would like to see and eventually
use only Public-Stable APIs.


On Wed, Jul 23, 2014 at 7:22 AM, Jason Lowe 
wrote:

> I think that's a reasonable proposal as long as we understand it changes
> the burden from finding all the things that should be marked @Private to
> finding all the things that should be marked @Public. As Tom Graves pointed
> out in an earlier discussion about @LimitedPrivate, it may be impossible to
> do a straightforward task and use only interfaces marked @Public.  If users
> can't do basic things without straying from @Public interfaces then tons of
> code can break if we assume it's always fair game to change anything not
> marked @Public.  The "well you shouldn't have used a non-@Public
> interface" argument is not very useful in that context.
>
> So as long as we're good about making sure officially supported features
> have corresponding @Public interfaces to wield them then I agree it will be
> easier to track those rather than track all the classes that should be
> @Private.  Hopefully if users understand that's how things work they'll
> help file JIRAs for interfaces that need to be @Public to get their work
> done.
>
> Jason
>
>
> On 07/22/2014 04:54 PM, Karthik Kambatla wrote:
>
>> Hi devs
>>
>> As you might have noticed, we have several classes and methods in them
>> that
>> are not annotated at all. This is seldom intentional. Avoiding
>> incompatible
>> changes to all these classes can be considerable baggage.
>>
>> I was wondering if we should add an explicit disclaimer in our
>> compatibility guide that says, "Classes without annotations are to
>> considered @Private"
>>
>> For methods, is it reasonable to say - "Class members without specific
>> annotations inherit the annotations of the class"?
>>
>> Thanks
>> Karthik
>>
>>
>

[jira] [Created] (YARN-2343) Improve

2014-07-23 Thread Li Lu (JIRA) 
Li Lu created YARN-2343:
---

 Summary: Improve
 Key: YARN-2343
 URL: https://issues.apache.org/jira/browse/YARN-2343
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Li Lu
Priority: Trivial






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (YARN-2345) yarn rmadin -report

2014-07-23 Thread Allen Wittenauer (JIRA) 
Allen Wittenauer created YARN-2345:
--

 Summary: yarn rmadin -report
 Key: YARN-2345
 URL: https://issues.apache.org/jira/browse/YARN-2345
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Allen Wittenauer


It would be good to have an equivalent of hdfs dfsadmin -report in YARN.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (YARN-2346) Add a 'status' command to yarn-daemon.sh

2014-07-23 Thread Nikunj Bansal (JIRA) 
Nikunj Bansal created YARN-2346:
---

 Summary: Add a 'status' command to yarn-daemon.sh
 Key: YARN-2346
 URL: https://issues.apache.org/jira/browse/YARN-2346
 Project: Hadoop YARN
  Issue Type: Improvement
Affects Versions: 2.4.1, 2.4.0, 2.3.0, 2.2.0
Reporter: Nikunj Bansal
Priority: Minor


Adding a 'status' command to yarn-daemon.sh will be useful for finding out the 
status of yarn daemons.

Running the 'status' command should exit with a 0 exit code if the target 
daemon is running and non-zero code in case its not.




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Failed: YARN-2343 PreCommit Build #4407

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2343
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4407/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13150 lines...]
  
http://issues.apache.org/jira/secure/attachment/12657437/YARN-2343-072314.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-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/4407//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4407//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
f97f34b7b6cdb1f0772e71023275043c21c98655 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4406
Archived 17 artifacts
Archive block size is 32768
Received 47 blocks and 6642034 bytes
Compression is 18.8%
Took 5.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) 
##
All tests passed

Failed: YARN-415 PreCommit Build #4408

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-415
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4408/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13690 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 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: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-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  org.apache.hadoop.yarn.client.TestApplicationMasterServiceOnHA
  
org.apache.hadoop.yarn.server.resourcemanager.rmapp.TestRMAppTransitions

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/4408//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4408//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
488ed80ffa813fea60eb5e2e2235bac4cd49f28e logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4406
Archived 37 artifacts
Archive block size is 32768
Received 219 blocks and 2269161 bytes
Compression is 76.0%
Took 2.3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
5 tests failed.
FAILED:  
org.apache.hadoop.yarn.client.TestApplicationMasterServiceOnHA.testAllocateOnHA

Error Message:
Given AMRMToken for application : appattempt_1000_0001_00 seems to have 
been generated illegally.

Stack Trace:
org.apache.hadoop.security.token.SecretManager$InvalidToken: Given AMRMToken 
for application : appattempt_1000_0001_00 seems to have been generated 
illegally.
at org.apache.hadoop.ipc.Client.call(Client.java:1411)
at org.apache.hadoop.ipc.Client.call(Client.java:1364)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:206)
at com.sun.proxy.$Proxy85.allocate(Unknown Source)
at 
org.apache.hadoop.yarn.api.impl.pb.client.ApplicationMasterProtocolPBClientImpl.allocate(ApplicationMasterProtocolPBClientImpl.java:77)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:186)
at 
org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:101)
at com.sun.proxy.$Proxy86.allocate(Unknown Source)
at 
org.apache.hadoop.yarn.client.TestApplicationMasterServiceOnHA.testAllocateOnHA(TestApplicationMasterServiceOnHA.java:84)


FAILED:  
org.apache.hadoop.yarn.server.resourcemanager.rmapp.TestRMAppTransitions.testAppRunningKill[0]

Error Message:
application finish time is not greater then 0

Stack Trace:
java.lang.AssertionError: application finish time is not greater then 0
at org

[jira] [Created] (YARN-2347) Consolidate RMStateVersion and NMDBSchemaVersion into StateVersion in yarn-server-common

2014-07-23 Thread Junping Du (JIRA) 
Junping Du created YARN-2347:


 Summary: Consolidate RMStateVersion and NMDBSchemaVersion into 
StateVersion in yarn-server-common
 Key: YARN-2347
 URL: https://issues.apache.org/jira/browse/YARN-2347
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Junping Du
Assignee: Junping Du


We have similar things for version state for RM, NM, TS (TimelineServer), etc. 
I think we should consolidate them into a common object.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (YARN-2348) ResourceManager web UI should display locale time instead of UTC time

2014-07-23 Thread Leitao Guo (JIRA) 
Leitao Guo created YARN-2348:


 Summary: ResourceManager web UI should display locale time instead 
of UTC time
 Key: YARN-2348
 URL: https://issues.apache.org/jira/browse/YARN-2348
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.4.1
Reporter: Leitao Guo
 Attachments: 1.before-change.jpg, 2.after-change.jpg

ResourceManager web UI, including application list and scheduler, displays UTC 
time in default,  this will confuse users who do not use UTC time. This web UI 
should display local time of users.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Failed: YARN-2347 PreCommit Build #4409

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2347
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4409/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13635 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12657521/YARN-2347.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 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: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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 
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/4409//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/4409//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-nodemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4409//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
a7dc0d3d4202f0aa5b7d1ac2c21ab65393a3aeff logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4406
Archived 37 artifacts
Archive block size is 32768
Received 210 blocks and 2050685 bytes
Compression is 77.0%
Took 2.3 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

[jira] [Created] (YARN-2349) InvalidStateTransitonException after RM switch

2014-07-23 Thread Nishan Shetty (JIRA) 
Nishan Shetty created YARN-2349:
---

 Summary: InvalidStateTransitonException after RM switch
 Key: YARN-2349
 URL: https://issues.apache.org/jira/browse/YARN-2349
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.4.1
Reporter: Nishan Shetty


{code}
2014-07-23 19:22:28,272 INFO org.apache.hadoop.ipc.Server: IPC Server 
Responder: starting
2014-07-23 19:22:28,273 INFO org.apache.hadoop.ipc.Server: IPC Server listener 
on 45018: starting
2014-07-23 19:22:28,266 ERROR 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl: Can't handle 
this event at current state
org.apache.hadoop.yarn.state.InvalidStateTransitonException: Invalid event: 
APP_REJECTED at ACCEPTED
 at 
org.apache.hadoop.yarn.state.StateMachineFactory.doTransition(StateMachineFactory.java:305)
 at 
org.apache.hadoop.yarn.state.StateMachineFactory.access$300(StateMachineFactory.java:46)
 at 
org.apache.hadoop.yarn.state.StateMachineFactory$InternalStateMachine.doTransition(StateMachineFactory.java:448)
 at 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:635)
 at 
org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppImpl.handle(RMAppImpl.java:83)
 at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationEventDispatcher.handle(ResourceManager.java:706)
 at 
org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationEventDispatcher.handle(ResourceManager.java:690)
 at 
org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:173)
 at org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:106)
 at java.lang.Thread.run(Thread.java:662)
2014-07-23 19:22:28,283 INFO org.mortbay.log: Stopped 
SelectChannelConnector@10.18.40.84:45020
2014-07-23 19:22:28,291 ERROR 
org.apache.hadoop.yarn.server.applicationhistoryservice.FileSystemApplicationHistoryStore:
 Error when openning history file of application application_1406116264351_0007
{code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Failed: YARN-2348 PreCommit Build #4410

2014-07-23 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2348
Build: https://builds.apache.org/job/PreCommit-YARN-Build/4410/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 13058 lines...]
  http://issues.apache.org/jira/secure/attachment/12657526/YARN-2348.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-common.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/4410//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4410//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
a32a631f8bdebf6fe1a9b5d20875b7805fa1d08e logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4406
Archived 17 artifacts
Archive block size is 32768
Received 44 blocks and 6796113 bytes
Compression is 17.5%
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) 
##
All tests passed