[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154282#comment-17154282 ] Bilwa S T commented on YARN-10341: -- Thanks [~brahmareddy] > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Fix For: 3.4.0, 3.3.1 > > Attachments: YARN-10341.001.patch, YARN-10341.002.patch, > YARN-10341.003.patch, YARN-10341.004.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154281#comment-17154281 ] Hudson commented on YARN-10341: --- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18421 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/18421/]) YARN-10341. Yarn Service Container Completed event doesn't get (brahma: rev dfe60392c91be21f574c1659af22f5c381b2675a) * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/test/java/org/apache/hadoop/yarn/service/TestServiceAM.java * (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core/src/main/java/org/apache/hadoop/yarn/service/ServiceScheduler.java > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Fix For: 3.4.0, 3.3.1 > > Attachments: YARN-10341.001.patch, YARN-10341.002.patch, > YARN-10341.003.patch, YARN-10341.004.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154250#comment-17154250 ] Brahma Reddy Battula commented on YARN-10341: - [~BilwaST] thanks bilwa for addressing the checkstyle, going to commit shortly. > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch, YARN-10341.002.patch, > YARN-10341.003.patch, YARN-10341.004.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154242#comment-17154242 ] Bilwa S T commented on YARN-10341: -- Fixed Checkstyle issues > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch, YARN-10341.002.patch, > YARN-10341.003.patch, YARN-10341.004.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154235#comment-17154235 ] Hadoop QA commented on YARN-10341: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m 19s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m 0s{color} | {color:green} No case conflicting files found. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 22m 3s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 27s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 21s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 30s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 16m 23s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s{color} | {color:green} trunk passed {color} | | {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 0m 55s{color} | {color:blue} Used deprecated FindBugs config; considering switching to SpotBugs. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 53s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 29s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 22s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 22s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 14s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 26s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 15m 44s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 15s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 57s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 19m 27s{color} | {color:green} hadoop-yarn-services-core in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 28s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 81m 8s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/PreCommit-YARN-Build/26262/artifact/out/Dockerfile | | JIRA Issue | YARN-10341 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/13007346/YARN-10341.004.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 760c568266eb 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | personality/hadoop.sh | | git revision | trunk / 10d218934c9 | | Default Java | Private Build-1.8.0_252-8u252-b09-1~18.04-b09 | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/26262/testReport/ | | Max. process+thread count | 777 (vs. ulimit of 5500) | | modules | C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core U:
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153700#comment-17153700 ] Hadoop QA commented on YARN-10341: -- | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m 19s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m 0s{color} | {color:green} No case conflicting files found. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 24m 38s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 28s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 22s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 36s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 16m 42s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s{color} | {color:green} trunk passed {color} | | {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 0m 57s{color} | {color:blue} Used deprecated FindBugs config; considering switching to SpotBugs. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 54s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 28s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 23s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 23s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 15s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core: The patch generated 2 new + 15 unchanged - 0 fixed = 17 total (was 15) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 24s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 15m 28s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 16s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 58s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 19m 37s{color} | {color:green} hadoop-yarn-services-core in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 31s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 84m 7s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/PreCommit-YARN-Build/26257/artifact/out/Dockerfile | | JIRA Issue | YARN-10341 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/13007305/YARN-10341.003.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux eb15ff0a25e6 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | personality/hadoop.sh | | git revision | trunk / 3a4d05b8504 | | Default Java | Private Build-1.8.0_252-8u252-b09-1~18.04-b09 | | checkstyle |
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153590#comment-17153590 ] Hadoop QA commented on YARN-10341: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m 21s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m 0s{color} | {color:green} No case conflicting files found. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 0s{color} | {color:green} The patch appears to include 1 new or modified test files. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 22m 14s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 28s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 21s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 31s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 16m 18s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s{color} | {color:green} trunk passed {color} | | {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 0m 55s{color} | {color:blue} Used deprecated FindBugs config; considering switching to SpotBugs. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 52s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 28s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 23s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 23s{color} | {color:green} the patch passed {color} | | {color:orange}-0{color} | {color:orange} checkstyle {color} | {color:orange} 0m 15s{color} | {color:orange} hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-services/hadoop-yarn-services-core: The patch generated 4 new + 15 unchanged - 0 fixed = 19 total (was 15) {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 24s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 15m 25s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 16s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 58s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:red}-1{color} | {color:red} unit {color} | {color:red} 19m 25s{color} | {color:red} hadoop-yarn-services-core in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 29s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 81m 1s{color} | {color:black} {color} | \\ \\ || Reason || Tests || | Failed junit tests | hadoop.yarn.service.TestServiceAM | \\ \\ || Subsystem || Report/Notes || | Docker | ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/PreCommit-YARN-Build/26256/artifact/out/Dockerfile | | JIRA Issue | YARN-10341 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/13007298/YARN-10341.002.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 13923a5cf4ff 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | personality/hadoop.sh | | git revision | trunk / 3a4d05b8504 | | Default Java | Private Build-1.8.0_252-8u252-b09-1~18.04-b09 | | checkstyle |
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153525#comment-17153525 ] Bilwa S T commented on YARN-10341: -- Thanks [~brahmareddy] [~billie] for reviewing. I have added testcase in patch .002 > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch, YARN-10341.002.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152870#comment-17152870 ] Billie Rinaldi commented on YARN-10341: --- I agree, continue looks better here. > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152749#comment-17152749 ] Brahma Reddy Battula commented on YARN-10341: - [~BilwaST] thanks for reporting. Looks to be hidden bug here..Patch lgtm.. Try to add one UT for this. > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152338#comment-17152338 ] Eric Yang commented on YARN-10341: -- cc [~billie] [~jianhe] > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152325#comment-17152325 ] Hadoop QA commented on YARN-10341: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 2m 35s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m 0s{color} | {color:green} No case conflicting files found. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s{color} | {color:red} The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 26m 50s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 33s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 27s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 34s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 19m 0s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 25s{color} | {color:green} trunk passed {color} | | {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 1m 7s{color} | {color:blue} Used deprecated FindBugs config; considering switching to SpotBugs. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 4s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 38s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 29s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 29s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 17s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 30s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 18m 15s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 18s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 12s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 20m 17s{color} | {color:green} hadoop-yarn-services-core in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 28s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 94m 34s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/PreCommit-YARN-Build/26253/artifact/out/Dockerfile | | JIRA Issue | YARN-10341 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/13007176/YARN-10341.001.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux 9f5b79b49796 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | personality/hadoop.sh | | git revision | trunk / 834372f4040 | | Default Java | Private Build-1.8.0_252-8u252-b09-1~18.04-b09 | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/26253/testReport/ | | Max. process+thread count | 778 (vs. ulimit of 5500) | | modules
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152271#comment-17152271 ] Bilwa S T commented on YARN-10341: -- Okay i will take care from next time . Thanks [~eyang] > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152267#comment-17152267 ] Eric Yang commented on YARN-10341: -- [~BilwaST] I see that you'd changed the code from break to continue. This change looks better. Please use a new version of the patch instead of replacing existing patch 001, this will help the recommit build to report correctly for the new patch. Thanks > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152246#comment-17152246 ] Hadoop QA commented on YARN-10341: -- | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m 24s{color} | {color:blue} Docker mode activated. {color} | || || || || {color:brown} Prechecks {color} || | {color:green}+1{color} | {color:green} dupname {color} | {color:green} 0m 0s{color} | {color:green} No case conflicting files found. {color} | | {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} | | {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s{color} | {color:red} The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color} | || || || || {color:brown} trunk Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 23m 56s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 32s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 22s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 35s{color} | {color:green} trunk passed {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 17m 29s{color} | {color:green} branch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s{color} | {color:green} trunk passed {color} | | {color:blue}0{color} | {color:blue} spotbugs {color} | {color:blue} 1m 5s{color} | {color:blue} Used deprecated FindBugs config; considering switching to SpotBugs. {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 6s{color} | {color:green} trunk passed {color} | || || || || {color:brown} Patch Compile Tests {color} || | {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 33s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 30s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 30s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 17s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} mvnsite {color} | {color:green} 0m 28s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} | | {color:green}+1{color} | {color:green} shadedclient {color} | {color:green} 15m 51s{color} | {color:green} patch has no errors when building and testing our client artifacts. {color} | | {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 16s{color} | {color:green} the patch passed {color} | | {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 2s{color} | {color:green} the patch passed {color} | || || || || {color:brown} Other Tests {color} || | {color:green}+1{color} | {color:green} unit {color} | {color:green} 19m 43s{color} | {color:green} hadoop-yarn-services-core in the patch passed. {color} | | {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 33s{color} | {color:green} The patch does not generate ASF License warnings. {color} | | {color:black}{color} | {color:black} {color} | {color:black} 85m 22s{color} | {color:black} {color} | \\ \\ || Subsystem || Report/Notes || | Docker | ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/PreCommit-YARN-Build/26252/artifact/out/Dockerfile | | JIRA Issue | YARN-10341 | | JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/13007162/YARN-10341.001.patch | | Optional Tests | dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle | | uname | Linux b6a1c9c50022 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux | | Build tool | maven | | Personality | personality/hadoop.sh | | git revision | trunk / 834372f4040 | | Default Java | Private Build-1.8.0_252-8u252-b09-1~18.04-b09 | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/26252/testReport/ | | Max. process+thread count | 777 (vs. ulimit of 5500) | | modules
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152241#comment-17152241 ] Eric Yang commented on YARN-10341: -- [~BilwaST] Sorry, I am confused by this ticket and the proposed patch fix to the described problem. The containers "restart_policy" controls if the container should be restarted on the event of failure/killed. If it was not set, it will always restart. If it was set to "NEVER", it will not restart. The completion events are secondary information to assist to restart the containers or not. Using return or break in onContainerCompleted method, don't make any difference. Maybe I am missing something, could you give more information on how this patch address the observed issue? > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed
[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152182#comment-17152182 ] Bilwa S T commented on YARN-10341: -- cc [~eyang] > Yarn Service Container Completed event doesn't get processed > - > > Key: YARN-10341 > URL: https://issues.apache.org/jira/browse/YARN-10341 > Project: Hadoop YARN > Issue Type: Bug >Reporter: Bilwa S T >Assignee: Bilwa S T >Priority: Critical > Attachments: YARN-10341.001.patch > > > If there 10 workers running and if containers get killed , after a while we > see that there are just 9 workers runnning. This is due to CONTAINER > COMPLETED Event is not processed on AM side. > Issue is in below code: > {code:java} > public void onContainersCompleted(List statuses) { > for (ContainerStatus status : statuses) { > ContainerId containerId = status.getContainerId(); > ComponentInstance instance = > liveInstances.get(status.getContainerId()); > if (instance == null) { > LOG.warn( > "Container {} Completed. No component instance exists. > exitStatus={}. diagnostics={} ", > containerId, status.getExitStatus(), status.getDiagnostics()); > return; > } > ComponentEvent event = > new ComponentEvent(instance.getCompName(), CONTAINER_COMPLETED) > .setStatus(status).setInstance(instance) > .setContainerId(containerId); > dispatcher.getEventHandler().handle(event); > } > {code} > If component instance doesnt exist for a container, it doesnt iterate over > other containers as its returning from method -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org