[jira] [Commented] (YARN-8155) Improve the logging in NMTimelinePublisher and TimelineCollectorWebService

[ https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512030#comment-16512030 ] Rohith Sharma K S commented on YARN-8155: - Committing shortly.. > Improve the lo

[jira] [Assigned] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reassigned YARN-8423: Assignee: Sunil Govindan (was: Wangda Tan) > GPU does not get released even though the application

[jira] [Commented] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512022#comment-16512022 ] Wangda Tan commented on YARN-8423: -- A possible simple fix to workaround the issue is to m

[jira] [Updated] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8423: - Target Version/s: 3.1.1 > GPU does not get released even though the application gets killed. > ---

[jira] [Updated] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-8423: - Attachment: kill-container-nm.log > GPU does not get released even though the application gets killed. > -

[jira] [Commented] (YARN-8423) GPU does not get released even though the application gets killed.

[ https://issues.apache.org/jira/browse/YARN-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512019#comment-16512019 ] Wangda Tan commented on YARN-8423: -- Thanks [~ssath...@hortonworks.com] for filing the iss

[jira] [Commented] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512014#comment-16512014 ] Gour Saha commented on YARN-8425: - If you are not reporting a bug or improvement, sending

[jira] [Reopened] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapas Sen reopened YARN-8425: - > Yarn container getting killed due to running beyond physical memory limits > ---

[jira] [Commented] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512010#comment-16512010 ] Tapas Sen commented on YARN-8425: -   So this is a prod cluster, what is the impact on the

[jira] [Commented] (YARN-8412) Move ResourceRequest.clone logic everywhere into a proper API

[ https://issues.apache.org/jira/browse/YARN-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511988#comment-16511988 ] genericqa commented on YARN-8412: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Updated] (YARN-8401) Yarnui2 not working with out internet connection

[ https://issues.apache.org/jira/browse/YARN-8401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-8401: --- Target Version/s: 3.1.1 > Yarnui2 not working with out internet connection > -

[jira] [Updated] (YARN-8418) App local logs could leaked if log aggregation fails to initialize for the app

[ https://issues.apache.org/jira/browse/YARN-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-8418: --- Target Version/s: 3.1.1 > App local logs could leaked if log aggregation fails to initialize f

[jira] [Commented] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[ https://issues.apache.org/jira/browse/YARN-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511962#comment-16511962 ] genericqa commented on YARN-8421: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-6972) Adding RM ClusterId in AppInfo

[ https://issues.apache.org/jira/browse/YARN-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511959#comment-16511959 ] genericqa commented on YARN-6972: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-6972) Adding RM ClusterId in AppInfo

[ https://issues.apache.org/jira/browse/YARN-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511940#comment-16511940 ] Yiran Wu commented on YARN-6972: Can we show the SubClusterId information in the 'yarn app

[jira] [Commented] (YARN-8270) Adding JMX Metrics for Timeline Collector and Reader

[ https://issues.apache.org/jira/browse/YARN-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511938#comment-16511938 ] Haibo Chen commented on YARN-8270: -- Thanks [~Sushil-K-S] for updating the patch! The unit

[jira] [Commented] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511937#comment-16511937 ] genericqa commented on YARN-7556: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511909#comment-16511909 ] Sunil Govindan commented on YARN-8258: -- configs.env is a static file. This is loaded

[jira] [Commented] (YARN-7708) [GPG] Load based policy generator

[ https://issues.apache.org/jira/browse/YARN-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511918#comment-16511918 ] genericqa commented on YARN-7708: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Updated] (YARN-8421) when moving app, activeUsers is increased, even though app does not have outstanding request

[ https://issues.apache.org/jira/browse/YARN-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-8421: --- Attachment: YARN-8421.002.patch > when moving app, activeUsers is increased, even though app does not

[jira] [Updated] (YARN-8412) Move ResourceRequest.clone logic everywhere into a proper API

[ https://issues.apache.org/jira/browse/YARN-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-8412: --- Attachment: YARN-8412.v2.patch > Move ResourceRequest.clone logic everywhere into a proper API > -

[jira] [Commented] (YARN-8414) Nodemanager crashes soon if ATSv2 HBase is either down or absent

[ https://issues.apache.org/jira/browse/YARN-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511867#comment-16511867 ] Eric Yang commented on YARN-8414: - The root cause for node manager to crash is contributed

[jira] [Commented] (YARN-6964) Fair scheduler misuses Resources operations

[ https://issues.apache.org/jira/browse/YARN-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511848#comment-16511848 ] genericqa commented on YARN-6964: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8412) Move ResourceRequest.clone logic everywhere into a proper API

[ https://issues.apache.org/jira/browse/YARN-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511841#comment-16511841 ] genericqa commented on YARN-8412: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511833#comment-16511833 ] Eric Yang commented on YARN-8258: - [~sunilg] I am getting this error with patch 008 withou

[jira] [Commented] (YARN-6995) Improve use of ResourceNotFoundException in resource types code

[ https://issues.apache.org/jira/browse/YARN-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511837#comment-16511837 ] genericqa commented on YARN-6995: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8259) Revisit liveliness checks for Docker containers

[ https://issues.apache.org/jira/browse/YARN-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511814#comment-16511814 ] Hudson commented on YARN-8259: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #144

[jira] [Updated] (YARN-8283) [Umbrella] MaWo - A Master Worker framework on top of YARN Services

[ https://issues.apache.org/jira/browse/YARN-8283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora updated YARN-8283: - Attachment: [Design Doc] [YARN-8283] MaWo - A Master Worker framework on top of YARN Services.pdf > [Umbr

[jira] [Commented] (YARN-8411) Enable stopped system services to be started during RM start

[ https://issues.apache.org/jira/browse/YARN-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511799#comment-16511799 ] Hudson commented on YARN-8411: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #144

[jira] [Commented] (YARN-8283) [Umbrella] MaWo - A Master Worker framework on top of YARN Services

[ https://issues.apache.org/jira/browse/YARN-8283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511791#comment-16511791 ] Yesha Vora commented on YARN-8283: -- Design doc is attached.  > [Umbrella] MaWo - A Maste

[jira] [Commented] (YARN-6995) Improve use of ResourceNotFoundException in resource types code

[ https://issues.apache.org/jira/browse/YARN-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511754#comment-16511754 ] Daniel Templeton commented on YARN-6995: I rebased to latest trunk. [~sunilg], I

[jira] [Updated] (YARN-6995) Improve use of ResourceNotFoundException in resource types code

[ https://issues.apache.org/jira/browse/YARN-6995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-6995: --- Attachment: YARN-6995.005.patch > Improve use of ResourceNotFoundException in resource types c

[jira] [Resolved] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gour Saha resolved YARN-8425. - Resolution: Not A Bug > Yarn container getting killed due to running beyond physical memory limits > -

[jira] [Commented] (YARN-8414) Nodemanager crashes soon if ATSv2 HBase is either down or absent

[ https://issues.apache.org/jira/browse/YARN-8414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511737#comment-16511737 ] Eric Yang commented on YARN-8414: - When hbase.client.pause is configured, there does not a

[jira] [Updated] (YARN-6964) Fair scheduler misuses Resources operations

[ https://issues.apache.org/jira/browse/YARN-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-6964: --- Attachment: YARN-6964.012.patch > Fair scheduler misuses Resources operations > --

[jira] [Commented] (YARN-6964) Fair scheduler misuses Resources operations

[ https://issues.apache.org/jira/browse/YARN-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511728#comment-16511728 ] Daniel Templeton commented on YARN-6964: I made an arbitrary choice to set demand

[jira] [Commented] (YARN-7708) [GPG] Load based policy generator

[ https://issues.apache.org/jira/browse/YARN-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511705#comment-16511705 ] Young Chen commented on YARN-7708: -- Thanks [~botong] for the comments. I've fixed all of

[jira] [Updated] (YARN-7708) [GPG] Load based policy generator

[ https://issues.apache.org/jira/browse/YARN-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Young Chen updated YARN-7708: - Attachment: YARN-7708-YARN-7402.03.patch > [GPG] Load based policy generator > ---

[jira] [Updated] (YARN-8412) Move ResourceRequest.clone logic everywhere into a proper API

[ https://issues.apache.org/jira/browse/YARN-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-8412: --- Attachment: YARN-8412.v2.patch > Move ResourceRequest.clone logic everywhere into a proper API > -

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511694#comment-16511694 ] Eric Payne commented on YARN-8379: -- [~Zian Chen], I attached the confs I used to create m

[jira] [Commented] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511692#comment-16511692 ] Daniel Templeton commented on YARN-7556: New patch addresses [~wilfreds] docs conc

[jira] [Updated] (YARN-7556) Fair scheduler configuration should allow resource types in the minResources and maxResources properties

[ https://issues.apache.org/jira/browse/YARN-7556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton updated YARN-7556: --- Attachment: YARN-7556.007.patch > Fair scheduler configuration should allow resource types in

[jira] [Commented] (YARN-8412) Move ResourceRequest.clone logic everywhere into a proper API

[ https://issues.apache.org/jira/browse/YARN-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511685#comment-16511685 ] genericqa commented on YARN-8412: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Updated] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Payne updated YARN-8379: - Attachment: ericpayne.confs.tgz > Add an option to allow Capacity Scheduler preemption to balance satisfie

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511522#comment-16511522 ] Zian Chen commented on YARN-8379: - Thank you [~eepayne] for your suggestions. I'm totally

[jira] [Commented] (YARN-8410) Registry DNS lookup fails to return for CNAMEs

[ https://issues.apache.org/jira/browse/YARN-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511505#comment-16511505 ] Eric Yang commented on YARN-8410: - [~shaneku...@gmail.com] The reordering of cname records

[jira] [Commented] (YARN-8394) Improve data locality documentation for Capacity Scheduler

[ https://issues.apache.org/jira/browse/YARN-8394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511503#comment-16511503 ] Yufei Gu commented on YARN-8394: Hi [~cheersyang], Let me clarify a little bit. The code

[jira] [Updated] (YARN-8412) Move ResourceRequest.clone logic everywhere into a proper API

[ https://issues.apache.org/jira/browse/YARN-8412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-8412: --- Attachment: YARN-8412.v2.patch > Move ResourceRequest.clone logic everywhere into a proper API > -

[jira] [Commented] (YARN-8410) Registry DNS lookup fails to return for CNAMEs

[ https://issues.apache.org/jira/browse/YARN-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511494#comment-16511494 ] Eric Yang commented on YARN-8410: - {quote} I'll note that it does look like we've got foll

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511469#comment-16511469 ] Eric Payne commented on YARN-8379: -- [~Zian Chen], thank you for the work on this issue an

[jira] [Commented] (YARN-8259) Revisit liveliness checks for Docker containers

[ https://issues.apache.org/jira/browse/YARN-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511444#comment-16511444 ] genericqa commented on YARN-8259: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511380#comment-16511380 ] Sunil Govindan commented on YARN-8258: -- Find bugs warnings are on trunk and shaded cl

[jira] [Updated] (YARN-8259) Revisit liveliness checks for Docker containers

[ https://issues.apache.org/jira/browse/YARN-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-8259: -- Attachment: YARN-8259.002.patch > Revisit liveliness checks for Docker containers >

[jira] [Commented] (YARN-8405) RM zk-state-store.parent-path ACLs has been changed since HADOOP-14773

[ https://issues.apache.org/jira/browse/YARN-8405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511350#comment-16511350 ] Íñigo Goiri commented on YARN-8405: --- Thanks [~rohithsharma] for the cherry-pick! > RM z

[jira] [Commented] (YARN-7190) Ensure only NM classpath in 2.x gets TSv2 related hbase jars, not the user classpath

[ https://issues.apache.org/jira/browse/YARN-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511347#comment-16511347 ] Sean Busbey commented on YARN-7190: --- I thought this issue was going to be included in th

[jira] [Commented] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511241#comment-16511241 ] Gour Saha commented on YARN-8425: - If _yarn.nodemanager.pmem-check-enabled_ in your cluste

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511201#comment-16511201 ] genericqa commented on YARN-8258: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8410) Registry DNS lookup fails to return for CNAMEs

[ https://issues.apache.org/jira/browse/YARN-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511208#comment-16511208 ] genericqa commented on YARN-8410: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8411) Enable stopped system services to be started during RM start

[ https://issues.apache.org/jira/browse/YARN-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511170#comment-16511170 ] Billie Rinaldi commented on YARN-8411: -- Thanks for taking a look, [~rohithsharma]! Ye

[jira] [Updated] (YARN-8410) Registry DNS lookup fails to return for CNAMEs

[ https://issues.apache.org/jira/browse/YARN-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Kumpf updated YARN-8410: -- Attachment: YARN-8410.003.patch > Registry DNS lookup fails to return for CNAMEs > -

[jira] [Commented] (YARN-8410) Registry DNS lookup fails to return for CNAMEs

[ https://issues.apache.org/jira/browse/YARN-8410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511152#comment-16511152 ] Shane Kumpf commented on YARN-8410: --- Thanks for the review and feedback [~eyang]! That b

[jira] [Commented] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511007#comment-16511007 ] Sunil Govindan commented on YARN-8258: -- HADOOP-15518 and YARN-8108 are majorly fixing

[jira] [Updated] (YARN-8258) YARN webappcontext for UI2 should inherit all filters from default context

[ https://issues.apache.org/jira/browse/YARN-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8258: - Attachment: YARN-8258.008.patch > YARN webappcontext for UI2 should inherit all filters from defau

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510996#comment-16510996 ] genericqa commented on YARN-8379: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote ||

[jira] [Commented] (YARN-8404) Timeline event publish need to be async to avoid Dispatcher thread leak in case ATS is down

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510949#comment-16510949 ] Hudson commented on YARN-8404: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #144

[jira] [Updated] (YARN-8404) Timeline event publish need to be async to avoid Dispatcher thread leak in case ATS is down

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil Govindan updated YARN-8404: - Summary: Timeline event publish need to be async to avoid Dispatcher thread leak in case ATS is do

[jira] [Updated] (YARN-8418) App local logs could leaked if log aggregation fails to initialize for the app

[ https://issues.apache.org/jira/browse/YARN-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-8418: --- Affects Version/s: 2.8.0 3.0.0-alpha1 > App local logs could leaked if

[jira] [Updated] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zian Chen updated YARN-8379: Attachment: YARN-8379.003.patch > Add an option to allow Capacity Scheduler preemption to balance satisfied

[jira] [Commented] (YARN-8379) Add an option to allow Capacity Scheduler preemption to balance satisfied queues

[ https://issues.apache.org/jira/browse/YARN-8379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510896#comment-16510896 ] Zian Chen commented on YARN-8379: - Update patch 003 for stage 2. Add configured timeout fo

[jira] [Updated] (YARN-8425) Yarn container getting killed due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapas Sen updated YARN-8425: Summary: Yarn container getting killed due to running beyond physical memory limits (was: Yarn container ge

[jira] [Updated] (YARN-8425) Yarn container getting due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapas Sen updated YARN-8425: Attachment: yarn_configuration_3.PNG yarn_configuration_2.PNG yarn_configurat

[jira] [Updated] (YARN-8425) Yarn container getting due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapas Sen updated YARN-8425: Description: Hi, Getting these error.   2018-06-12 17:59:07,193 INFO [AsyncDispatcher event handler] org

[jira] [Updated] (YARN-8425) Yarn container getting due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapas Sen updated YARN-8425: Description: Hi, Getting these error.   2018-06-12 17:59:07,193 INFO [AsyncDispatcher event handler] org

[jira] [Updated] (YARN-8425) Yarn container getting due to running beyond physical memory limits

[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tapas Sen updated YARN-8425: Description: Hi, Getting these error.   2018-06-12 17:59:07,193 INFO [AsyncDispatcher event handler] or

[jira] [Created] (YARN-8425) Yarn container getting due to running beyond physical memory limits

Tapas Sen created YARN-8425: --- Summary: Yarn container getting due to running beyond physical memory limits Key: YARN-8425 URL: https://issues.apache.org/jira/browse/YARN-8425 Project: Hadoop YARN

[jira] [Commented] (YARN-8404) RM Event dispatcher is blocked if ATS1/1.5 server is not running.

[ https://issues.apache.org/jira/browse/YARN-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510845#comment-16510845 ] Sunil Govindan commented on YARN-8404: -- Committing shortly. > RM Event dispatcher is

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16510810#comment-16510810 ] Bibin A Chundatt commented on YARN-8424: Thank you [~baktha] raising the issue. M

[jira] [Moved] (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 ] Bibin A Chundatt moved HADOOP-15534 to YARN-8424: - Affects Version/s: (was: 2.8.3) 2.8.3