[jira] [Commented] (YARN-6695) Race condition in RM for publishing container events vs appFinished events causes NPE

[ https://issues.apache.org/jira/browse/YARN-6695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867599#comment-16867599 ] K G Bakthavachalam commented on YARN-6695: -- [~Prabhu Joseph] can u provide brief info how to

[jira] [Commented] (YARN-9448) Fix Opportunistic Scheduling for node local allocations.

[ https://issues.apache.org/jira/browse/YARN-9448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16867516#comment-16867516 ] K G Bakthavachalam commented on YARN-9448: -- [~abmodi] can u give brief information how to

[jira] [Commented] (YARN-9435) Add Opportunistic Scheduler metrics in ResourceManager.

[ https://issues.apache.org/jira/browse/YARN-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839076#comment-16839076 ] K G Bakthavachalam commented on YARN-9435: -- [~abmodi] destroy is not handled in RM side ,so when

[jira] [Updated] (YARN-9435) Add Opportunistic Scheduler metrics in ResourceManager.

[ https://issues.apache.org/jira/browse/YARN-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] K G Bakthavachalam updated YARN-9435: - Description: # Right now there are no metrics available for Opportunistic Scheduler at

[jira] [Commented] (YARN-9039) App ACLs are not validated when serving logs from LogWebService

[ https://issues.apache.org/jira/browse/YARN-9039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770947#comment-16770947 ] K G Bakthavachalam commented on YARN-9039: -- [~suma.shivaprasad] any updates on this jira > App

[jira] [Updated] (YARN-5566) Client-side NM graceful decom is not triggered when jobs finish

[ https://issues.apache.org/jira/browse/YARN-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] K G Bakthavachalam updated YARN-5566: - Description: I was testing the client-side NM graceful decommission and noticed that it

[jira] [Updated] (YARN-5566) Client-side NM graceful decom is not triggered when jobs finish

[ https://issues.apache.org/jira/browse/YARN-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] K G Bakthavachalam updated YARN-5566: - Description: I was testing the client-side NM graceful decommission and noticed that it

[jira] [Updated] (YARN-5566) Client-side NM graceful decom is not triggered when jobs finish

[ https://issues.apache.org/jira/browse/YARN-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] K G Bakthavachalam updated YARN-5566: - Description: I was testing the client-side NM graceful decommission and noticed that it

[jira] [Updated] (YARN-8491) UT failure in TestServiceCLI#testEnableFastLaunch when umask is set to 077

[ https://issues.apache.org/jira/browse/YARN-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bakthavachalam updated YARN-8491: - Attachment: YARN-8491.001.patch > UT failure in TestServiceCLI#testEnableFastLaunch when umask is

[jira] [Created] (YARN-8491) UT failure in TestServiceCLI#testEnableFastLaunch when umask is set to 077

bakthavachalam created YARN-8491: Summary: UT failure in TestServiceCLI#testEnableFastLaunch when umask is set to 077 Key: YARN-8491 URL: https://issues.apache.org/jira/browse/YARN-8491 Project:

[jira] [Assigned] (YARN-8491) UT failure in TestServiceCLI#testEnableFastLaunch when umask is set to 077

[ https://issues.apache.org/jira/browse/YARN-8491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bakthavachalam reassigned YARN-8491: Assignee: bakthavachalam > UT failure in TestServiceCLI#testEnableFastLaunch when umask is

[jira] [Updated] (YARN-8424) mapreduce job is getting submitted with negative priority as it is not handled to run with default priority(i.e: 0)

[ https://issues.apache.org/jira/browse/YARN-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bakthavachalam updated YARN-8424: - Attachment: (was: apppatch.patch) > mapreduce job is getting submitted with negative priority

[jira] [Updated] (YARN-8424) mapreduce job is getting submitted with negative priority as it is not handled to run with default priority(i.e: 0)

[ https://issues.apache.org/jira/browse/YARN-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bakthavachalam updated YARN-8424: - Attachment: apppatch.patch > mapreduce job is getting submitted with negative priority as it is