[ https://issues.apache.org/jira/browse/YARN-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534626#comment-14534626 ]
Hadoop QA commented on YARN-2821: --------------------------------- \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 15m 4s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 1 new or modified test files. | | {color:green}+1{color} | javac | 7m 46s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 54s | There were no new javadoc warning messages. | | {color:green}+1{color} | release audit | 0m 23s | The applied patch does not increase the total number of release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 23s | The applied patch generated 2 new checkstyle issues (total was 150, now 150). | | {color:green}+1{color} | whitespace | 0m 3s | The patch has no lines that end in whitespace. | | {color:green}+1{color} | install | 1m 37s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 0m 37s | The patch does not introduce any new Findbugs (version 2.0.3) warnings. | | {color:green}+1{color} | yarn tests | 7m 2s | Tests passed in hadoop-yarn-applications-distributedshell. | | | | 43m 25s | | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12731438/YARN-2821.003.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 241a72a | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/7806/artifact/patchprocess/diffcheckstylehadoop-yarn-applications-distributedshell.txt | | hadoop-yarn-applications-distributedshell test log | https://builds.apache.org/job/PreCommit-YARN-Build/7806/artifact/patchprocess/testrun_hadoop-yarn-applications-distributedshell.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7806/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf904.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/7806/console | This message was automatically generated. > Distributed shell app master becomes unresponsive sometimes > ----------------------------------------------------------- > > Key: YARN-2821 > URL: https://issues.apache.org/jira/browse/YARN-2821 > Project: Hadoop YARN > Issue Type: Bug > Components: applications/distributed-shell > Affects Versions: 2.5.1 > Reporter: Varun Vasudev > Assignee: Varun Vasudev > Attachments: YARN-2821.002.patch, YARN-2821.003.patch, > apache-yarn-2821.0.patch, apache-yarn-2821.1.patch > > > We've noticed that once in a while the distributed shell app master becomes > unresponsive and is eventually killed by the RM. snippet of the logs - > {noformat} > 14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: > appattempt_1415123350094_0017_000001 received 0 previous attempts' running > containers on AM registration. > 14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested > container ask: Capability[<memory:10, vCores:1>]Priority[0] > 14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested > container ask: Capability[<memory:10, vCores:1>]Priority[0] > 14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested > container ask: Capability[<memory:10, vCores:1>]Priority[0] > 14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested > container ask: Capability[<memory:10, vCores:1>]Priority[0] > 14/11/04 18:21:37 INFO distributedshell.ApplicationMaster: Requested > container ask: Capability[<memory:10, vCores:1>]Priority[0] > 14/11/04 18:21:38 INFO impl.AMRMClientImpl: Received new token for : > onprem-tez2:45454 > 14/11/04 18:21:38 INFO distributedshell.ApplicationMaster: Got response from > RM for container ask, allocatedCnt=1 > 14/11/04 18:21:38 INFO distributedshell.ApplicationMaster: Launching shell > command on a new container., > containerId=container_1415123350094_0017_01_000002, > containerNode=onprem-tez2:45454, containerNodeURI=onprem-tez2:50060, > containerResourceMemory1024, containerResourceVirtualCores1 > 14/11/04 18:21:38 INFO distributedshell.ApplicationMaster: Setting up > container launch container for > containerid=container_1415123350094_0017_01_000002 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > START_CONTAINER for Container container_1415123350094_0017_01_000002 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez2:45454 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > QUERY_CONTAINER for Container container_1415123350094_0017_01_000002 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez2:45454 > 14/11/04 18:21:39 INFO impl.AMRMClientImpl: Received new token for : > onprem-tez3:45454 > 14/11/04 18:21:39 INFO impl.AMRMClientImpl: Received new token for : > onprem-tez4:45454 > 14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Got response from > RM for container ask, allocatedCnt=3 > 14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Launching shell > command on a new container., > containerId=container_1415123350094_0017_01_000003, > containerNode=onprem-tez2:45454, containerNodeURI=onprem-tez2:50060, > containerResourceMemory1024, containerResourceVirtualCores1 > 14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Launching shell > command on a new container., > containerId=container_1415123350094_0017_01_000004, > containerNode=onprem-tez3:45454, containerNodeURI=onprem-tez3:50060, > containerResourceMemory1024, containerResourceVirtualCores1 > 14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Launching shell > command on a new container., > containerId=container_1415123350094_0017_01_000005, > containerNode=onprem-tez4:45454, containerNodeURI=onprem-tez4:50060, > containerResourceMemory1024, containerResourceVirtualCores1 > 14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Setting up > container launch container for > containerid=container_1415123350094_0017_01_000003 > 14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Setting up > container launch container for > containerid=container_1415123350094_0017_01_000005 > 14/11/04 18:21:39 INFO distributedshell.ApplicationMaster: Setting up > container launch container for > containerid=container_1415123350094_0017_01_000004 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > START_CONTAINER for Container container_1415123350094_0017_01_000005 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > START_CONTAINER for Container container_1415123350094_0017_01_000003 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez4:45454 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez2:45454 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > START_CONTAINER for Container container_1415123350094_0017_01_000004 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez3:45454 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > QUERY_CONTAINER for Container container_1415123350094_0017_01_000005 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez4:45454 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > QUERY_CONTAINER for Container container_1415123350094_0017_01_000003 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez2:45454 > 14/11/04 18:21:39 INFO impl.NMClientAsyncImpl: Processing Event EventType: > QUERY_CONTAINER for Container container_1415123350094_0017_01_000004 > 14/11/04 18:21:39 INFO impl.ContainerManagementProtocolProxy: Opening proxy : > onprem-tez3:45454 > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: Got response from > RM for container ask, completedCnt=1 > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: > appattempt_1415123350094_0017_000001 got container status for > containerID=container_1415123350094_0017_01_000002, state=COMPLETE, > exitStatus=0, diagnostics= > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: Container > completed successfully., containerId=container_1415123350094_0017_01_000002 > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: Got response from > RM for container ask, allocatedCnt=2 > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: Launching shell > command on a new container., > containerId=container_1415123350094_0017_01_000006, > containerNode=onprem-tez2:45454, containerNodeURI=onprem-tez2:50060, > containerResourceMemory1024, containerResourceVirtualCores1 > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: Launching shell > command on a new container., > containerId=container_1415123350094_0017_01_000007, > containerNode=onprem-tez3:45454, containerNodeURI=onprem-tez3:50060, > containerResourceMemory1024, containerResourceVirtualCores1 > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: Setting up > container launch container for > containerid=container_1415123350094_0017_01_000007 > 14/11/04 18:21:40 INFO distributedshell.ApplicationMaster: Setting up > container launch container for > containerid=container_1415123350094_0017_01_000006 > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)