[jira] [Commented] (YARN-53) Add protocol to YARN to support GetGroups

2012-09-04 Thread Arun C Murthy (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13447893#comment-13447893
 ] 

Arun C Murthy commented on YARN-53:
---

Yes, it's fine to port get* commands from bin/mapred to bin/yarn as they make 
sense.

 Add protocol to YARN to support GetGroups
 -

 Key: YARN-53
 URL: https://issues.apache.org/jira/browse/YARN-53
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.1.0-alpha
Reporter: Alejandro Abdelnur
Assignee: Bo Wang
 Attachments: MAPREDUCE-4268.patch


 This is a regression from Hadoop1, as hadoop mrgroups fails with:
 {code}
 Exception in thread main java.lang.UnsupportedOperationException
   at 
 org.apache.hadoop.mapred.tools.GetGroups.getProtocolAddress(GetGroups.java:50)
   at 
 org.apache.hadoop.tools.GetGroupsBase.getUgmProtocol(GetGroupsBase.java:98)
   at org.apache.hadoop.tools.GetGroupsBase.run(GetGroupsBase.java:71)
   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
   at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
   at org.apache.hadoop.mapred.tools.GetGroups.main(GetGroups.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-57) Plugable process tree

2012-09-04 Thread Radim Kolar (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448024#comment-13448024
 ] 

Radim Kolar commented on YARN-57:
-

where is log with javac errors?

 Plugable process tree
 -

 Key: YARN-57
 URL: https://issues.apache.org/jira/browse/YARN-57
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: nodemanager
 Environment: FreeBSD 64 bit
Reporter: Radim Kolar
Assignee: Radim Kolar
 Attachments: plugable-pstree-1.txt, plugable-pstree-2.txt, 
 plugable-pstree-3.txt, plugable-pstree-4.txt, 
 plugable-pstree-4-with-whitespace.txt, plugable-pstree-5-with-whitespace.txt, 
 plugable-pstree-6-typofix.txt, plugable-pstree-trunk-merge-7.txt, 
 plugable-pstree-trunk-merge-7.txt, plugable-pstree.txt


 Trunk version of Pluggable process tree. Work based on MAPREDUCE-4204

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-10) dist-shell shouldn't have a (test) dependency on hadoop-mapreduce-client-core

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448055#comment-13448055
 ] 

Hudson commented on YARN-10:


Integrated in Hadoop-Hdfs-trunk-Commit #2738 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2738/])
YARN-10. Fix DistributedShell module to not have a dependency on 
hadoop-mapreduce-client-core. Contributed by Hitesh Shah. (Revision 1380879)

 Result = SUCCESS
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380879
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/test/java/org/apache/hadoop/yarn/applications/distributedshell/TestDistributedShell.java


 dist-shell shouldn't have a (test) dependency on hadoop-mapreduce-client-core
 -

 Key: YARN-10
 URL: https://issues.apache.org/jira/browse/YARN-10
 Project: Hadoop YARN
  Issue Type: Improvement
Affects Versions: 2.2.0-alpha
Reporter: Arun C Murthy
Assignee: Hitesh Shah
 Fix For: 2.1.0-alpha

 Attachments: YARN-10.1.patch


 dist-shell shouldn't have a (test) dependency on 
 hadoop-mapreduce-client-core, this should be removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-82) YARN local-dirs defaults to /tmp/nm-local-dir

2012-09-04 Thread Andy Isaacson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448088#comment-13448088
 ] 

Andy Isaacson commented on YARN-82:
---

bq. Let's be careful, we don't need to introduce explicit deps on configs from 
HDFS/MR. Let's keep a separate namespace.
Thanks for the idea, Arun. Can you suggest a good name or existing variable I 
should depend on?

 YARN local-dirs defaults to /tmp/nm-local-dir
 -

 Key: YARN-82
 URL: https://issues.apache.org/jira/browse/YARN-82
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Andy Isaacson
Assignee: Andy Isaacson
Priority: Minor

 {{yarn.nodemanager.local-dirs}} defaults to {{/tmp/nm-local-dir}}.  It should 
 be {hadoop.tmp.dir}/nm-local-dir or similar.  Among other problems, this can 
 prevent multiple test clusters from starting on the same machine.
 Thanks to Hemanth Yamijala for reporting this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-10) dist-shell shouldn't have a (test) dependency on hadoop-mapreduce-client-core

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448093#comment-13448093
 ] 

Hudson commented on YARN-10:


Integrated in Hadoop-Mapreduce-trunk-Commit #2700 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2700/])
YARN-10. Fix DistributedShell module to not have a dependency on 
hadoop-mapreduce-client-core. Contributed by Hitesh Shah. (Revision 1380879)

 Result = FAILURE
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380879
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/test/java/org/apache/hadoop/yarn/applications/distributedshell/TestDistributedShell.java


 dist-shell shouldn't have a (test) dependency on hadoop-mapreduce-client-core
 -

 Key: YARN-10
 URL: https://issues.apache.org/jira/browse/YARN-10
 Project: Hadoop YARN
  Issue Type: Improvement
Affects Versions: 2.2.0-alpha
Reporter: Arun C Murthy
Assignee: Hitesh Shah
 Fix For: 2.1.0-alpha

 Attachments: YARN-10.1.patch


 dist-shell shouldn't have a (test) dependency on 
 hadoop-mapreduce-client-core, this should be removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-83) Change package of YarnClient to include apache

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448104#comment-13448104
 ] 

Vinod Kumar Vavilapalli commented on YARN-83:
-

+1, it was a mistake on my behalf.

 Change package of YarnClient to include apache
 --

 Key: YARN-83
 URL: https://issues.apache.org/jira/browse/YARN-83
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Bikas Saha

 Currently its org.hadoop.* instead of org.apache.hadoop.*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Moved] (YARN-84) Use Builder to get RPC server in Map/Reduce

2012-09-04 Thread Suresh Srinivas (JIRA)

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

Suresh Srinivas moved MAPREDUCE-4628 to YARN-84:


  Component/s: (was: test)
 Assignee: (was: Brandon Li)
Affects Version/s: (was: 3.0.0)
  Key: YARN-84  (was: MAPREDUCE-4628)
  Project: Hadoop YARN  (was: Hadoop Map/Reduce)

 Use Builder to get RPC server in Map/Reduce
 ---

 Key: YARN-84
 URL: https://issues.apache.org/jira/browse/YARN-84
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Brandon Li
Priority: Minor
 Attachments: MAPREDUCE-4628.patch


 In HADOOP-8736, a Builder is introduced to replace all the getServer() 
 variants. This JIRA is the change in Map/Reduce.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Assigned] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli reassigned YARN-79:
---

Assignee: Vinod Kumar Vavilapalli

 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
   at 
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
 ===

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-79:


Attachment: YARN-79-20120904.txt

Fixing this.

One client-impl also had the same problem. Fixing that too.

Corrected the formatting issues with all the client-impls also. This makes the 
patch slightly larger than it is required to be.

 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
   at 
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
 ===

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448140#comment-13448140
 ] 

Vinod Kumar Vavilapalli commented on YARN-78:
-

Makes sense.

But you still need to fix the run() method to make sure client is stopped 
correctly. I think instead of my earlier suggestion of extending 
YarnClientImpl, implementing Service is better for you since you can then shut 
down client as part of {{stop()}} and create it as part of {{start()}}.

 Change UnmanagedAMLauncher to use YarnClientImpl
 

 Key: YARN-78
 URL: https://issues.apache.org/jira/browse/YARN-78
 Project: Hadoop YARN
  Issue Type: Bug
Affects Versions: 2.1.0-alpha, 2.2.0-alpha
Reporter: Bikas Saha
Assignee: Bikas Saha
 Attachments: YARN-78.1.patch


 YARN-29 added a common client impl to talk to the RM. Use that in the 
 UnmanagedAMLauncher.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Assigned] (YARN-84) Use Builder to get RPC server in Map/Reduce

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli reassigned YARN-84:
---

Assignee: Brandon Li

 Use Builder to get RPC server in Map/Reduce
 ---

 Key: YARN-84
 URL: https://issues.apache.org/jira/browse/YARN-84
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Brandon Li
Assignee: Brandon Li
Priority: Minor
 Attachments: MAPREDUCE-4628.patch


 In HADOOP-8736, a Builder is introduced to replace all the getServer() 
 variants. This JIRA is the change in Map/Reduce.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (YARN-84) Use Builder to get RPC server in YARN

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-84:


Description: In HADOOP-8736, a Builder is introduced to replace all the 
getServer() variants. This JIRA is the change in YARN.  (was: In HADOOP-8736, a 
Builder is introduced to replace all the getServer() variants. This JIRA is the 
change in Map/Reduce.)
Summary: Use Builder to get RPC server in YARN  (was: Use Builder to 
get RPC server in Map/Reduce)

 Use Builder to get RPC server in YARN
 -

 Key: YARN-84
 URL: https://issues.apache.org/jira/browse/YARN-84
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Brandon Li
Assignee: Brandon Li
Priority: Minor
 Attachments: MAPREDUCE-4628.patch


 In HADOOP-8736, a Builder is introduced to replace all the getServer() 
 variants. This JIRA is the change in YARN.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Bikas Saha (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448153#comment-13448153
 ] 

Bikas Saha commented on YARN-79:


Looks ok +1. Surprising that the AMRMProtocol.close() did not implement 
Closeable. I guess all users explicitly called close().

 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
   at 
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
 ===

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-84) Use Builder to get RPC server in YARN

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448170#comment-13448170
 ] 

Hudson commented on YARN-84:


Integrated in Hadoop-Common-trunk-Commit #2677 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2677/])
YARN-84. Use Builder to build RPC server. Contributed by Brandon Li 
(Revision 1380921)

 Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380921
Files : 
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/security/TestUmbilicalProtocolWithJobToken.java
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/factories/impl/pb/RpcServerFactoryPBImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNMAuditLogger.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMAuditLogger.java


 Use Builder to get RPC server in YARN
 -

 Key: YARN-84
 URL: https://issues.apache.org/jira/browse/YARN-84
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Brandon Li
Assignee: Brandon Li
Priority: Minor
 Attachments: MAPREDUCE-4628.patch


 In HADOOP-8736, a Builder is introduced to replace all the getServer() 
 variants. This JIRA is the change in YARN.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-84) Use Builder to get RPC server in YARN

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448181#comment-13448181
 ] 

Hudson commented on YARN-84:


Integrated in Hadoop-Hdfs-trunk-Commit #2740 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2740/])
YARN-84. Use Builder to build RPC server. Contributed by Brandon Li 
(Revision 1380921)

 Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380921
Files : 
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/security/TestUmbilicalProtocolWithJobToken.java
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/factories/impl/pb/RpcServerFactoryPBImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNMAuditLogger.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestRMAuditLogger.java


 Use Builder to get RPC server in YARN
 -

 Key: YARN-84
 URL: https://issues.apache.org/jira/browse/YARN-84
 Project: Hadoop YARN
  Issue Type: Improvement
Reporter: Brandon Li
Assignee: Brandon Li
Priority: Minor
 Attachments: MAPREDUCE-4628.patch


 In HADOOP-8736, a Builder is introduced to replace all the getServer() 
 variants. This JIRA is the change in YARN.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448230#comment-13448230
 ] 

Vinod Kumar Vavilapalli commented on YARN-79:
-

bq. Surprising that the AMRMProtocol.close() did not implement Closeable. I 
guess all users explicitly called close().
The close() code-path gets triggered only if clients (here AMs) explicity 
shutdown the RPC client, seems like we aren't doing that in MR AM for e.g.

Pushing this in.

 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
   at 
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
 ===

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-79:


  Component/s: client
Affects Version/s: 2.1.0-alpha

 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.1.0-alpha
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Fix For: 2.1.0-alpha

 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
   at 
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
   at 
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
 ===

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448244#comment-13448244
 ] 

Hudson commented on YARN-79:


Integrated in Hadoop-Hdfs-trunk-Commit #2743 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2743/])
YARN-79. Implement close on all clients to YARN so that RPC clients don't 
throw exceptions on shut-down. Contributed by Vinod Kumar Vavilapalli. 
(Revision 1380942)

 Result = SUCCESS
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380942
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/hadoop/yarn/client/TestYarnClient.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/AMRMProtocolPBClientImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/ClientRMProtocolPBClientImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/ContainerManagerPBClientImpl.java


 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.1.0-alpha
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Fix For: 2.1.0-alpha

 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165

[jira] [Commented] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448246#comment-13448246
 ] 

Hudson commented on YARN-79:


Integrated in Hadoop-Common-trunk-Commit #2680 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2680/])
YARN-79. Implement close on all clients to YARN so that RPC clients don't 
throw exceptions on shut-down. Contributed by Vinod Kumar Vavilapalli. 
(Revision 1380942)

 Result = SUCCESS
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380942
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/hadoop/yarn/client/TestYarnClient.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/AMRMProtocolPBClientImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/ClientRMProtocolPBClientImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/ContainerManagerPBClientImpl.java


 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.1.0-alpha
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Fix For: 2.1.0-alpha

 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165

[jira] [Assigned] (YARN-42) Node Manager throws NPE on startup

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli reassigned YARN-42:
---

Assignee: Devaraj K

 Node Manager throws NPE on startup
 --

 Key: YARN-42
 URL: https://issues.apache.org/jira/browse/YARN-42
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Attachments: MAPREDUCE-4254.patch


 NM throws NPE on startup if it doesn't have persmission's on nm local dir's
 {code:xml}
 2012-05-14 16:32:13,468 FATAL 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager: Error starting 
 NodeManager
 org.apache.hadoop.yarn.YarnException: Failed to initialize LocalizationService
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:202)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.init(ContainerManagerImpl.java:183)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:166)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:268)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:284)
 Caused by: java.io.IOException: mkdir of /mrv2/tmp/nm-local-dir/usercache 
 failed
   at org.apache.hadoop.fs.FileSystem.primitiveMkdir(FileSystem.java:907)
   at 
 org.apache.hadoop.fs.DelegateToFileSystem.mkdir(DelegateToFileSystem.java:143)
   at org.apache.hadoop.fs.FilterFs.mkdir(FilterFs.java:189)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:706)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:703)
   at 
 org.apache.hadoop.fs.FileContext$FSLinkResolver.resolve(FileContext.java:2325)
   at org.apache.hadoop.fs.FileContext.mkdir(FileContext.java:703)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:188)
   ... 6 more
 2012-05-14 16:32:13,472 INFO org.apache.hadoop.yarn.service.CompositeService: 
 Error stopping 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler
 java.lang.NullPointerException
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler.stop(NonAggregatingLogHandler.java:82)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.stop(ContainerManagerImpl.java:266)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.stop(NodeManager.java:182)
   at 
 org.apache.hadoop.yarn.service.CompositeService$CompositeServiceShutdownHook.run(CompositeService.java:122)
   at 
 org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-42) Node Manager throws NPE on startup

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448283#comment-13448283
 ] 

Vinod Kumar Vavilapalli commented on YARN-42:
-

This should be a harmless exception, and the current error message is clear 
enough.

Don't have a problem avoiding this unnecessary NPE, +1.

Will resubmit to Jenkins and check this in once it's blessed.

 Node Manager throws NPE on startup
 --

 Key: YARN-42
 URL: https://issues.apache.org/jira/browse/YARN-42
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Attachments: MAPREDUCE-4254.patch


 NM throws NPE on startup if it doesn't have persmission's on nm local dir's
 {code:xml}
 2012-05-14 16:32:13,468 FATAL 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager: Error starting 
 NodeManager
 org.apache.hadoop.yarn.YarnException: Failed to initialize LocalizationService
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:202)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.init(ContainerManagerImpl.java:183)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:166)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:268)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:284)
 Caused by: java.io.IOException: mkdir of /mrv2/tmp/nm-local-dir/usercache 
 failed
   at org.apache.hadoop.fs.FileSystem.primitiveMkdir(FileSystem.java:907)
   at 
 org.apache.hadoop.fs.DelegateToFileSystem.mkdir(DelegateToFileSystem.java:143)
   at org.apache.hadoop.fs.FilterFs.mkdir(FilterFs.java:189)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:706)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:703)
   at 
 org.apache.hadoop.fs.FileContext$FSLinkResolver.resolve(FileContext.java:2325)
   at org.apache.hadoop.fs.FileContext.mkdir(FileContext.java:703)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:188)
   ... 6 more
 2012-05-14 16:32:13,472 INFO org.apache.hadoop.yarn.service.CompositeService: 
 Error stopping 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler
 java.lang.NullPointerException
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler.stop(NonAggregatingLogHandler.java:82)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.stop(ContainerManagerImpl.java:266)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.stop(NodeManager.java:182)
   at 
 org.apache.hadoop.yarn.service.CompositeService$CompositeServiceShutdownHook.run(CompositeService.java:122)
   at 
 org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-42) Node Manager throws NPE on startup

2012-09-04 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448284#comment-13448284
 ] 

Hadoop QA commented on YARN-42:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12527814/MAPREDUCE-4254.patch
  against trunk revision .

-1 patch.  The patch command could not apply the patch.

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

This message is automatically generated.

 Node Manager throws NPE on startup
 --

 Key: YARN-42
 URL: https://issues.apache.org/jira/browse/YARN-42
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Attachments: MAPREDUCE-4254.patch


 NM throws NPE on startup if it doesn't have persmission's on nm local dir's
 {code:xml}
 2012-05-14 16:32:13,468 FATAL 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager: Error starting 
 NodeManager
 org.apache.hadoop.yarn.YarnException: Failed to initialize LocalizationService
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:202)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.init(ContainerManagerImpl.java:183)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:166)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:268)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:284)
 Caused by: java.io.IOException: mkdir of /mrv2/tmp/nm-local-dir/usercache 
 failed
   at org.apache.hadoop.fs.FileSystem.primitiveMkdir(FileSystem.java:907)
   at 
 org.apache.hadoop.fs.DelegateToFileSystem.mkdir(DelegateToFileSystem.java:143)
   at org.apache.hadoop.fs.FilterFs.mkdir(FilterFs.java:189)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:706)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:703)
   at 
 org.apache.hadoop.fs.FileContext$FSLinkResolver.resolve(FileContext.java:2325)
   at org.apache.hadoop.fs.FileContext.mkdir(FileContext.java:703)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:188)
   ... 6 more
 2012-05-14 16:32:13,472 INFO org.apache.hadoop.yarn.service.CompositeService: 
 Error stopping 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler
 java.lang.NullPointerException
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler.stop(NonAggregatingLogHandler.java:82)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.stop(ContainerManagerImpl.java:266)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.stop(NodeManager.java:182)
   at 
 org.apache.hadoop.yarn.service.CompositeService$CompositeServiceShutdownHook.run(CompositeService.java:122)
   at 
 org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-79) Calling YarnClientImpl.close throws Exception

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448369#comment-13448369
 ] 

Hudson commented on YARN-79:


Integrated in Hadoop-Mapreduce-trunk-Commit #2704 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2704/])
YARN-79. Implement close on all clients to YARN so that RPC clients don't 
throw exceptions on shut-down. Contributed by Vinod Kumar Vavilapalli. 
(Revision 1380942)

 Result = FAILURE
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380942
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/pom.xml
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/hadoop/yarn/client/TestYarnClient.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/AMRMProtocolPBClientImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/ClientRMProtocolPBClientImpl.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/api/impl/pb/client/ContainerManagerPBClientImpl.java


 Calling YarnClientImpl.close throws Exception
 -

 Key: YARN-79
 URL: https://issues.apache.org/jira/browse/YARN-79
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.1.0-alpha
Reporter: Bikas Saha
Assignee: Vinod Kumar Vavilapalli
 Fix For: 2.1.0-alpha

 Attachments: YARN-79-20120904.txt


 The following exception is thrown
 ===
 *org.apache.hadoop.HadoopIllegalArgumentException: Cannot close proxy - is 
 not Closeable or does not provide closeable invocation handler class 
 org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl*
   *at org.apache.hadoop.ipc.RPC.stopProxy(RPC.java:624)*
   *at org.hadoop.yarn.client.YarnClientImpl.stop(YarnClientImpl.java:102)*
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.UnmanagedAMLauncher.run(UnmanagedAMLauncher.java:336)
   at 
 org.apache.hadoop.yarn.applications.unmanagedamlauncher.TestUnmanagedAMLauncher.testDSShell(TestUnmanagedAMLauncher.java:156)
   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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
   at 
 org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
   at 
 org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
   at 
 org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
   at 
 org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
   at 
 org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
   at 
 org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
   at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
   at 
 org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
   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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
   at 
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165

[jira] [Updated] (YARN-42) Node Manager throws NPE on startup

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-42:


Attachment: YARN-42.txt

Forgot that I manually fixed the paths in the patch to reflect YARN-1. 
Uploading the patch myself.

 Node Manager throws NPE on startup
 --

 Key: YARN-42
 URL: https://issues.apache.org/jira/browse/YARN-42
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Attachments: MAPREDUCE-4254.patch, YARN-42.txt


 NM throws NPE on startup if it doesn't have persmission's on nm local dir's
 {code:xml}
 2012-05-14 16:32:13,468 FATAL 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager: Error starting 
 NodeManager
 org.apache.hadoop.yarn.YarnException: Failed to initialize LocalizationService
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:202)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.init(ContainerManagerImpl.java:183)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:166)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:268)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:284)
 Caused by: java.io.IOException: mkdir of /mrv2/tmp/nm-local-dir/usercache 
 failed
   at org.apache.hadoop.fs.FileSystem.primitiveMkdir(FileSystem.java:907)
   at 
 org.apache.hadoop.fs.DelegateToFileSystem.mkdir(DelegateToFileSystem.java:143)
   at org.apache.hadoop.fs.FilterFs.mkdir(FilterFs.java:189)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:706)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:703)
   at 
 org.apache.hadoop.fs.FileContext$FSLinkResolver.resolve(FileContext.java:2325)
   at org.apache.hadoop.fs.FileContext.mkdir(FileContext.java:703)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:188)
   ... 6 more
 2012-05-14 16:32:13,472 INFO org.apache.hadoop.yarn.service.CompositeService: 
 Error stopping 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler
 java.lang.NullPointerException
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler.stop(NonAggregatingLogHandler.java:82)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.stop(ContainerManagerImpl.java:266)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.stop(NodeManager.java:182)
   at 
 org.apache.hadoop.yarn.service.CompositeService$CompositeServiceShutdownHook.run(CompositeService.java:122)
   at 
 org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-42) Node Manager throws NPE on startup

2012-09-04 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448379#comment-13448379
 ] 

Hadoop QA commented on YARN-42:
---

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12543785/YARN-42.txt
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 new or modified test 
files.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

+1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

+1 core tests.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

+1 contrib tests.  The patch passed contrib unit tests.

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

This message is automatically generated.

 Node Manager throws NPE on startup
 --

 Key: YARN-42
 URL: https://issues.apache.org/jira/browse/YARN-42
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Attachments: MAPREDUCE-4254.patch, YARN-42.txt


 NM throws NPE on startup if it doesn't have persmission's on nm local dir's
 {code:xml}
 2012-05-14 16:32:13,468 FATAL 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager: Error starting 
 NodeManager
 org.apache.hadoop.yarn.YarnException: Failed to initialize LocalizationService
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:202)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.init(ContainerManagerImpl.java:183)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:166)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:268)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:284)
 Caused by: java.io.IOException: mkdir of /mrv2/tmp/nm-local-dir/usercache 
 failed
   at org.apache.hadoop.fs.FileSystem.primitiveMkdir(FileSystem.java:907)
   at 
 org.apache.hadoop.fs.DelegateToFileSystem.mkdir(DelegateToFileSystem.java:143)
   at org.apache.hadoop.fs.FilterFs.mkdir(FilterFs.java:189)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:706)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:703)
   at 
 org.apache.hadoop.fs.FileContext$FSLinkResolver.resolve(FileContext.java:2325)
   at org.apache.hadoop.fs.FileContext.mkdir(FileContext.java:703)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:188)
   ... 6 more
 2012-05-14 16:32:13,472 INFO org.apache.hadoop.yarn.service.CompositeService: 
 Error stopping 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler
 java.lang.NullPointerException
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler.stop(NonAggregatingLogHandler.java:82)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.stop(ContainerManagerImpl.java:266)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.stop(NodeManager.java:182)
   at 
 org.apache.hadoop.yarn.service.CompositeService$CompositeServiceShutdownHook.run(CompositeService.java:122)
   at 
 org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, 

[jira] [Updated] (YARN-83) Change package of YarnClient to include apache

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-83:


Attachment: YARN-83.3.YARN.patch

Looks good. +1.

Let me re-upload the YARN only patch so that Jenkins can pick up YARN changes 
first.

 Change package of YarnClient to include apache
 --

 Key: YARN-83
 URL: https://issues.apache.org/jira/browse/YARN-83
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Bikas Saha
 Attachments: YARN-83.1.patch, YARN-83.2.patch, 
 YARN-83.3.combined.patch, YARN-83.3.MR.patch, YARN-83.3.YARN.patch, 
 YARN-83.3.YARN.patch


 Currently its org.hadoop.* instead of org.apache.hadoop.*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-83) Change package of YarnClient to include apache

2012-09-04 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448420#comment-13448420
 ] 

Hadoop QA commented on YARN-83:
---

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12543795/YARN-83.3.YARN.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 new or modified test 
files.

-1 javac.  The patch appears to cause the build to fail.

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

This message is automatically generated.

 Change package of YarnClient to include apache
 --

 Key: YARN-83
 URL: https://issues.apache.org/jira/browse/YARN-83
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Bikas Saha
 Attachments: YARN-83.1.patch, YARN-83.2.patch, 
 YARN-83.3.combined.patch, YARN-83.3.MR.patch, YARN-83.3.YARN.patch, 
 YARN-83.3.YARN.patch


 Currently its org.hadoop.* instead of org.apache.hadoop.*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-42) Node Manager throws NPE on startup

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448425#comment-13448425
 ] 

Hudson commented on YARN-42:


Integrated in Hadoop-Hdfs-trunk-Commit #2744 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2744/])
YARN-42. Modify NM's non-aggregating logs' handler to stop properly so that 
NMs don't get NPEs on startup errors. Contributed by Devaraj K. (Revision 
1380954)

 Result = SUCCESS
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380954
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/loghandler/NonAggregatingLogHandler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/loghandler/TestNonAggregatingLogHandler.java


 Node Manager throws NPE on startup
 --

 Key: YARN-42
 URL: https://issues.apache.org/jira/browse/YARN-42
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Fix For: 2.1.0-alpha

 Attachments: MAPREDUCE-4254.patch, YARN-42.txt


 NM throws NPE on startup if it doesn't have persmission's on nm local dir's
 {code:xml}
 2012-05-14 16:32:13,468 FATAL 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager: Error starting 
 NodeManager
 org.apache.hadoop.yarn.YarnException: Failed to initialize LocalizationService
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:202)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.init(ContainerManagerImpl.java:183)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:166)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:268)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:284)
 Caused by: java.io.IOException: mkdir of /mrv2/tmp/nm-local-dir/usercache 
 failed
   at org.apache.hadoop.fs.FileSystem.primitiveMkdir(FileSystem.java:907)
   at 
 org.apache.hadoop.fs.DelegateToFileSystem.mkdir(DelegateToFileSystem.java:143)
   at org.apache.hadoop.fs.FilterFs.mkdir(FilterFs.java:189)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:706)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:703)
   at 
 org.apache.hadoop.fs.FileContext$FSLinkResolver.resolve(FileContext.java:2325)
   at org.apache.hadoop.fs.FileContext.mkdir(FileContext.java:703)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:188)
   ... 6 more
 2012-05-14 16:32:13,472 INFO org.apache.hadoop.yarn.service.CompositeService: 
 Error stopping 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler
 java.lang.NullPointerException
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler.stop(NonAggregatingLogHandler.java:82)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.stop(ContainerManagerImpl.java:266)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.stop(NodeManager.java:182)
   at 
 org.apache.hadoop.yarn.service.CompositeService$CompositeServiceShutdownHook.run(CompositeService.java:122)
   at 
 org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (YARN-83) Change package of YarnClient to include apache

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated YARN-83:


Attachment: YARN-83.3.combined.patch

Cannot appease Jenkins, here goes the combined patch again..

 Change package of YarnClient to include apache
 --

 Key: YARN-83
 URL: https://issues.apache.org/jira/browse/YARN-83
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Bikas Saha
 Attachments: YARN-83.1.patch, YARN-83.2.patch, 
 YARN-83.3.combined.patch, YARN-83.3.combined.patch, YARN-83.3.MR.patch, 
 YARN-83.3.YARN.patch, YARN-83.3.YARN.patch


 Currently its org.hadoop.* instead of org.apache.hadoop.*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Moved] (YARN-85) Allow per job log aggregation configuration

2012-09-04 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli moved MAPREDUCE-3905 to YARN-85:


  Component/s: (was: mrv2)
   nodemanager
 Target Version/s:   (was: 0.23.3, 2.0.0-alpha, 3.0.0)
Affects Version/s: (was: 0.23.0)
  Key: YARN-85  (was: MAPREDUCE-3905)
  Project: Hadoop YARN  (was: Hadoop Map/Reduce)

 Allow per job log aggregation configuration
 ---

 Key: YARN-85
 URL: https://issues.apache.org/jira/browse/YARN-85
 Project: Hadoop YARN
  Issue Type: Improvement
  Components: nodemanager
Reporter: Siddharth Seth
Assignee: Siddharth Seth

 Currently, if log aggregation is enabled for a cluster - logs for all jobs 
 will be aggregated - leading to a whole bunch of files on hdfs which users 
 may not want.
 Users should be able to control this along with the aggregation policy - 
 failed only, all, etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-42) Node Manager throws NPE on startup

2012-09-04 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448431#comment-13448431
 ] 

Hudson commented on YARN-42:


Integrated in Hadoop-Common-trunk-Commit #2681 (See 
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2681/])
YARN-42. Modify NM's non-aggregating logs' handler to stop properly so that 
NMs don't get NPEs on startup errors. Contributed by Devaraj K. (Revision 
1380954)

 Result = SUCCESS
vinodkv : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1380954
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/loghandler/NonAggregatingLogHandler.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/loghandler/TestNonAggregatingLogHandler.java


 Node Manager throws NPE on startup
 --

 Key: YARN-42
 URL: https://issues.apache.org/jira/browse/YARN-42
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Fix For: 2.1.0-alpha

 Attachments: MAPREDUCE-4254.patch, YARN-42.txt


 NM throws NPE on startup if it doesn't have persmission's on nm local dir's
 {code:xml}
 2012-05-14 16:32:13,468 FATAL 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager: Error starting 
 NodeManager
 org.apache.hadoop.yarn.YarnException: Failed to initialize LocalizationService
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:202)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.init(ContainerManagerImpl.java:183)
   at 
 org.apache.hadoop.yarn.service.CompositeService.init(CompositeService.java:58)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.init(NodeManager.java:166)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:268)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:284)
 Caused by: java.io.IOException: mkdir of /mrv2/tmp/nm-local-dir/usercache 
 failed
   at org.apache.hadoop.fs.FileSystem.primitiveMkdir(FileSystem.java:907)
   at 
 org.apache.hadoop.fs.DelegateToFileSystem.mkdir(DelegateToFileSystem.java:143)
   at org.apache.hadoop.fs.FilterFs.mkdir(FilterFs.java:189)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:706)
   at org.apache.hadoop.fs.FileContext$4.next(FileContext.java:703)
   at 
 org.apache.hadoop.fs.FileContext$FSLinkResolver.resolve(FileContext.java:2325)
   at org.apache.hadoop.fs.FileContext.mkdir(FileContext.java:703)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService.init(ResourceLocalizationService.java:188)
   ... 6 more
 2012-05-14 16:32:13,472 INFO org.apache.hadoop.yarn.service.CompositeService: 
 Error stopping 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler
 java.lang.NullPointerException
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.loghandler.NonAggregatingLogHandler.stop(NonAggregatingLogHandler.java:82)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl.stop(ContainerManagerImpl.java:266)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
   at 
 org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
   at 
 org.apache.hadoop.yarn.server.nodemanager.NodeManager.stop(NodeManager.java:182)
   at 
 org.apache.hadoop.yarn.service.CompositeService$CompositeServiceShutdownHook.run(CompositeService.java:122)
   at 
 org.apache.hadoop.util.ShutdownHookManager$1.run(ShutdownHookManager.java:54)
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-40) Provide support for missing yarn commands

2012-09-04 Thread Devaraj K (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448439#comment-13448439
 ] 

Devaraj K commented on YARN-40:
---

Thanks Vinod for looking into the patch. I will update the patch.

 Provide support for missing yarn commands
 -

 Key: YARN-40
 URL: https://issues.apache.org/jira/browse/YARN-40
 Project: Hadoop YARN
  Issue Type: Bug
  Components: client
Affects Versions: 2.1.0-alpha
Reporter: Devaraj K
Assignee: Devaraj K
 Attachments: MAPREDUCE-4155-1.patch, MAPREDUCE-4155.patch


 1. status app-id
 2. kill app-id (Already issue present with Id : MAPREDUCE-3793)
 3. list-apps [all]
 4. nodes-report

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-83) Change package of YarnClient to include apache

2012-09-04 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448448#comment-13448448
 ] 

Hadoop QA commented on YARN-83:
---

+1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12543799/YARN-83.3.combined.patch
  against trunk revision .

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 1 new or modified test 
files.

+1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

+1 javadoc.  The javadoc tool did not generate any warning messages.

+1 eclipse:eclipse.  The patch built with eclipse:eclipse.

+1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) 
warnings.

+1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

+1 core tests.  The patch passed unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

+1 contrib tests.  The patch passed contrib unit tests.

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

This message is automatically generated.

 Change package of YarnClient to include apache
 --

 Key: YARN-83
 URL: https://issues.apache.org/jira/browse/YARN-83
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Bikas Saha
Assignee: Bikas Saha
 Attachments: YARN-83.1.patch, YARN-83.2.patch, 
 YARN-83.3.combined.patch, YARN-83.3.combined.patch, YARN-83.3.MR.patch, 
 YARN-83.3.YARN.patch, YARN-83.3.YARN.patch


 Currently its org.hadoop.* instead of org.apache.hadoop.*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (YARN-82) YARN local-dirs defaults to /tmp/nm-local-dir

2012-09-04 Thread Hemanth Yamijala (JIRA)

[ 
https://issues.apache.org/jira/browse/YARN-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448464#comment-13448464
 ] 

Hemanth Yamijala commented on YARN-82:
--

Arun, assume it is ok to add deps on configs in Common (i.e core-site), but not 
with Mapreduce/HDFS. Is that correct ?

 YARN local-dirs defaults to /tmp/nm-local-dir
 -

 Key: YARN-82
 URL: https://issues.apache.org/jira/browse/YARN-82
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.1.0-alpha
Reporter: Andy Isaacson
Assignee: Andy Isaacson
Priority: Minor

 {{yarn.nodemanager.local-dirs}} defaults to {{/tmp/nm-local-dir}}.  It should 
 be {hadoop.tmp.dir}/nm-local-dir or similar.  Among other problems, this can 
 prevent multiple test clusters from starting on the same machine.
 Thanks to Hemanth Yamijala for reporting this issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira