[ 
https://issues.apache.org/jira/browse/YARN-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986162#comment-14986162
 ] 

MENG DING commented on YARN-1510:
---------------------------------

The mvninstall error and failed tests should not be related to this ticket.

It seems that Hadoop QA now uses a different test framework? Not sure why 
mvninstall failed, it runs ok in my environment, see below. Maybe the 
mvninstall test should be placed in the last instead of the first?
{code}
Total Elapsed time:  47m  0s



+1 overall

 __________
< Success! >
 ----------
 \     /\  ___  /\
  \   // \/   \/ \\
     ((    O O    ))
      \\ /     \ //
       \/  | |  \/
        |  | |  |
        |  | |  |
        |   o   |
        | |   | |
        |m|   |m|


| Vote |           Subsystem |  Runtime   | Comment
============================================================================
|   0  |          pre-patch  |  20m 34s   | Pre-patch trunk compilation is
|      |                     |            | healthy.
|  +1  |            @author  |  0m 0s     | The patch does not contain any
|      |                     |            | @author tags.
|  +1  |     tests included  |  0m 0s     | The patch appears to include 2 new
|      |                     |            | or modified test files.
|  +1  |              javac  |  9m 39s    | There were no new javac warning
|      |                     |            | messages.
|  +1  |            javadoc  |  10m 43s   | There were no new javadoc warning
|      |                     |            | messages.
|  +1  |      release audit  |  0m 32s    | The applied patch does not increase
|      |                     |            | the total number of release audit
|      |                     |            | warnings.
|  +1  |         checkstyle  |  1m 5s     | There were no new checkstyle
|      |                     |            | issues.
|  +1  |         whitespace  |  0m 5s     | The patch has no lines that end in
|      |                     |            | whitespace.
|  +1  |            install  |  1m 54s    | mvn install still works.
|  +1  |    eclipse:eclipse  |  0m 43s    | The patch built with
|      |                     |            | eclipse:eclipse.
|  +1  |           findbugs  |  1m 43s    | The patch does not introduce any
|      |                     |            | new Findbugs (version 3.0.0)
|      |                     |            | warnings.
|      |                     |  47m 0s    |
{code}

In addition, the {{TestDistributedShell}} timeout may have the same root cause 
of YARN-4320, as the ApplicationMaster reports the following error in my test 
environment:
{code}
2015-11-02 21:57:38,066 INFO  [main] impl.TimelineClientImpl 
(TimelineClientImpl.java:serviceInit(299)) - Timeline service address: 
http://mdinglin02:0/ws/v1/timeline/
2015-11-02 21:57:38,099 INFO  [main] impl.TimelineClientImpl 
(TimelineClientImpl.java:logException(213)) - Exception caught by 
TimelineClientConnectionRetry, will try 30 more time(s).
...
...
java.lang.RuntimeException: Failed to connect to timeline server. Connection 
retries limit exceeded. The posted timeline event may be missing
        at 
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$TimelineClientConnectionRetry.retryOn(TimelineClientImpl.java:206)
        at 
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$TimelineJerseyRetryFilter.handle(TimelineClientImpl.java:245)
        at com.sun.jersey.api.client.Client.handle(Client.java:648)
        at com.sun.jersey.api.client.WebResource.handle(WebResource.java:670)
        at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74)
        at 
com.sun.jersey.api.client.WebResource$Builder.post(WebResource.java:563)
        at 
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.doPostingObject(TimelineClientImpl.java:477)
        at 
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$1.run(TimelineClientImpl.java:326)
        at 
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl$1.run(TimelineClientImpl.java:323)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:415)
        at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1669)
        at 
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.doPosting(TimelineClientImpl.java:323)
        at 
org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.putEntities(TimelineClientImpl.java:308)
        at 
org.apache.hadoop.yarn.applications.distributedshell.ApplicationMaster.publishApplicationAttemptEvent(ApplicationMaster.java:1184)
        at 
org.apache.hadoop.yarn.applications.distributedshell.ApplicationMaster.run(ApplicationMaster.java:571)
        at 
org.apache.hadoop.yarn.applications.distributedshell.ApplicationMaster.main(ApplicationMaster.java:302)
{code}

> Make NMClient support change container resources
> ------------------------------------------------
>
>                 Key: YARN-1510
>                 URL: https://issues.apache.org/jira/browse/YARN-1510
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>            Reporter: Wangda Tan (No longer used)
>            Assignee: MENG DING
>         Attachments: YARN-1510-YARN-1197.1.patch, 
> YARN-1510-YARN-1197.2.patch, YARN-1510.3.patch, YARN-1510.4.patch, 
> YARN-1510.5.patch, YARN-1510.6.patch, YARN-1510.7.patch
>
>
> As described in YARN-1197, YARN-1449, we need add API in NMClient to support
> 1) sending request of increase/decrease container resource limits
> 2) get succeeded/failed changed containers response from NM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to