[jira] [Updated] (YARN-4762) NMs failing on DelegatingLinuxContainerRuntime init with LCE on

[ https://issues.apache.org/jira/browse/YARN-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4762: Priority: Blocker (was: Critical) > NMs failing on DelegatingLinuxContainerRuntime init with LCE on

[jira] [Updated] (YARN-4553) Add cgroups support for docker containers

[ https://issues.apache.org/jira/browse/YARN-4553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-4553: Fix Version/s: 2.9.0 > Add cgroups support for docker containers > --

[jira] [Updated] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4761: -- Attachment: YARN-4761.02.patch Thanks for the pointer [~rohithsharma]. It's good to know. Posted patch v

[jira] [Commented] (YARN-4737) Use CSRF Filter in YARN

[ https://issues.apache.org/jira/browse/YARN-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179478#comment-15179478 ] Varun Vasudev commented on YARN-4737: - Thanks for the updated patch Jon! You don't need

[jira] [Commented] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

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

[jira] [Commented] (YARN-2883) Queuing of container requests in the NM

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

[jira] [Updated] (YARN-4762) NMs failing on DelegatingLinuxContainerRuntime init with LCE on

[ https://issues.apache.org/jira/browse/YARN-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-4762: Priority: Critical (was: Major) > NMs failing on DelegatingLinuxContainerRuntime init with L

[jira] [Commented] (YARN-4762) NMs failing on DelegatingLinuxContainerRuntime init with LCE on

[ https://issues.apache.org/jira/browse/YARN-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179196#comment-15179196 ] Sidharta Seethana commented on YARN-4762: - Changing priority to critical - NMs don'

[jira] [Commented] (YARN-4762) NMs failing on DelegatingLinuxContainerRuntime init with LCE on

[ https://issues.apache.org/jira/browse/YARN-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179194#comment-15179194 ] Sidharta Seethana commented on YARN-4762: - /cc [~vvasudev] When the new resource h

[jira] [Assigned] (YARN-4762) NMs failing on DelegatingLinuxContainerRuntime init with LCE on

[ https://issues.apache.org/jira/browse/YARN-4762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana reassigned YARN-4762: --- Assignee: Sidharta Seethana > NMs failing on DelegatingLinuxContainerRuntime init with

[jira] [Created] (YARN-4762) NMs failing on DelegatingLinuxContainerRuntime init with LCE on

Vinod Kumar Vavilapalli created YARN-4762: - Summary: NMs failing on DelegatingLinuxContainerRuntime init with LCE on Key: YARN-4762 URL: https://issues.apache.org/jira/browse/YARN-4762 Project

[jira] [Commented] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179171#comment-15179171 ] Rohith Sharma K S commented on YARN-4761: - I think we can move the test to TestAbst

[jira] [Commented] (YARN-4737) Use CSRF Filter in YARN

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

[jira] [Commented] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179127#comment-15179127 ] Sangjin Lee commented on YARN-4761: --- I'd like to discuss the unit test for this. I could

[jira] [Updated] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4761: -- Attachment: YARN-4761.01.patch Posted patch v.1. Applied the same fix to the fair scheduler. > NMs reco

[jira] [Commented] (YARN-4117) End to end unit test with mini YARN cluster for AMRMProxy Service

[ https://issues.apache.org/jira/browse/YARN-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179070#comment-15179070 ] Jian He commented on YARN-4117: --- bq. MiniYarnCluster allocates the ports for the RM during th

[jira] [Commented] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179066#comment-15179066 ] zhihai xu commented on YARN-4761: - Good Finding [~sjlee0]! the same issue could also happen

[jira] [Commented] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179045#comment-15179045 ] Sangjin Lee commented on YARN-4761: --- To see this, you add this code to {{TestResourceTra

[jira] [Created] (YARN-4761) NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler

Sangjin Lee created YARN-4761: - Summary: NMs reconnecting with changed capabilities can lead to wrong cluster resource calculations on fair scheduler Key: YARN-4761 URL: https://issues.apache.org/jira/browse/YARN-4761

[jira] [Commented] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

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

[jira] [Commented] (YARN-4749) Generalize config file handling in container-executor

[ https://issues.apache.org/jira/browse/YARN-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178835#comment-15178835 ] Hadoop QA commented on YARN-4749: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote |

[jira] [Updated] (YARN-2883) Queuing of container requests in the NM

[ https://issues.apache.org/jira/browse/YARN-2883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos updated YARN-2883: - Attachment: YARN-2883-yarn-2877.003.patch Adding some first test cases for the queu

[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178833#comment-15178833 ] Sidharta Seethana commented on YARN-4744: - Thanks, [~jlowe] ! > Too many signal to

[jira] [Assigned] (YARN-4760) proxy redirect to history server uses wrong URL

[ https://issues.apache.org/jira/browse/YARN-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger reassigned YARN-4760: - Assignee: Eric Badger > proxy redirect to history server uses wrong URL >

[jira] [Created] (YARN-4760) proxy redirect to history server uses wrong URL

Jason Lowe created YARN-4760: Summary: proxy redirect to history server uses wrong URL Key: YARN-4760 URL: https://issues.apache.org/jira/browse/YARN-4760 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178775#comment-15178775 ] Hadoop QA commented on YARN-4744: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote |

[jira] [Updated] (YARN-4758) Enable discovery of AMs by containers

[ https://issues.apache.org/jira/browse/YARN-4758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-4758: - Description: {color:red} This is already discussed on the umbrella JIRA YARN-1489. Copying some of my cond

[jira] [Updated] (YARN-4749) Generalize config file handling in container-executor

[ https://issues.apache.org/jira/browse/YARN-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-4749: Attachment: YARN-4749.002.patch Uploaded a new patch based on review feedback. > Generalize

[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178722#comment-15178722 ] Jason Lowe commented on YARN-4744: -- Thanks for updating the patch! +1, pending Jenkins.

[jira] [Commented] (YARN-4740) container complete msg may lost while AM restart in race condition

[ https://issues.apache.org/jira/browse/YARN-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178708#comment-15178708 ] sandflee commented on YARN-4740: yes, this patch ensure AM receive at least one container c

[jira] [Updated] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sidharta Seethana updated YARN-4744: Attachment: YARN-4744.002.patch Uploaded a new patch - added a new PrivilegedOperation constr

[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178661#comment-15178661 ] Jason Lowe commented on YARN-4744: -- Ah, ignore my previous comment -- I see now that we do

[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178658#comment-15178658 ] Jason Lowe commented on YARN-4744: -- Even if the Docker stuff doesn't work totally, it has

[jira] [Commented] (YARN-4740) container complete msg may lost while AM restart in race condition

[ https://issues.apache.org/jira/browse/YARN-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178657#comment-15178657 ] Jian He commented on YARN-4740: --- [~sandflee], actually, with this fix, the 2nd AM may possibl

[jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178653#comment-15178653 ] Vinod Kumar Vavilapalli commented on YARN-1489: --- bq. That and the "Old ru

[jira] [Created] (YARN-4759) Revisit signalContainer() for docker containers

Sidharta Seethana created YARN-4759: --- Summary: Revisit signalContainer() for docker containers Key: YARN-4759 URL: https://issues.apache.org/jira/browse/YARN-4759 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

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

[jira] [Created] (YARN-4758) Enable discovery of AMs by containers

Vinod Kumar Vavilapalli created YARN-4758: - Summary: Enable discovery of AMs by containers Key: YARN-4758 URL: https://issues.apache.org/jira/browse/YARN-4758 Project: Hadoop YARN Iss

[jira] [Updated] (YARN-4737) Use CSRF Filter in YARN

[ https://issues.apache.org/jira/browse/YARN-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron updated YARN-4737: - Attachment: YARN-4737.004.patch > Use CSRF Filter in YARN > --- > >

[jira] [Updated] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2888: -- Attachment: YARN-2888-yarn-2877.002.patch Updating above patch with some extra documentation and some min

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178629#comment-15178629 ] Jonathan Maron commented on YARN-4757: -- I've actually been working on a DNS approach f

[jira] [Assigned] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron reassigned YARN-4757: Assignee: Jonathan Maron > [Umbrella] Simplified discovery of services via DNS mechanisms >

[jira] [Created] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

Vinod Kumar Vavilapalli created YARN-4757: - Summary: [Umbrella] Simplified discovery of services via DNS mechanisms Key: YARN-4757 URL: https://issues.apache.org/jira/browse/YARN-4757 Project:

[jira] [Commented] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178614#comment-15178614 ] Hadoop QA commented on YARN-4756: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote |

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178599#comment-15178599 ] Eric Badger commented on YARN-4686: --- As per above comment, these test failures are not re

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

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

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Attachment: YARN-4756.002.patch Fixing patch so that it applies to trunk instead of being dependent on th

[jira] [Commented] (YARN-4737) Use CSRF Filter in YARN

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

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178448#comment-15178448 ] Kuhu Shukla commented on YARN-4311: --- Requesting [~jlowe], [~templedf] for review/comments

[jira] [Commented] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

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

[jira] [Commented] (YARN-4083) Add a discovery mechanism for the scheduler address

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178423#comment-15178423 ] Vinod Kumar Vavilapalli commented on YARN-4083: --- bq. Today many apps like Dis

[jira] [Commented] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

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

[jira] [Commented] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178409#comment-15178409 ] Eric Badger commented on YARN-4686: --- JIRA [YARN-4756] has been opened regarding the heart

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Description: The startStatusUpdater thread waits for the isStopped variable to be set to true, but it is

[jira] [Updated] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

[ https://issues.apache.org/jira/browse/YARN-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4756: -- Attachment: YARN-4756.001.patch The optimization to notify the Node Status Updater thread to stop waiting

[jira] [Created] (YARN-4756) Unnecessary wait in Node Status Updater during reboot

Eric Badger created YARN-4756: - Summary: Unnecessary wait in Node Status Updater during reboot Key: YARN-4756 URL: https://issues.apache.org/jira/browse/YARN-4756 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-2888) Corrective mechanisms for rebalancing NM container queues

[ https://issues.apache.org/jira/browse/YARN-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2888: -- Attachment: YARN-2888-yarn-2877.001.patch Uploading initial patch to solicit feedback > Corrective mecha

[jira] [Updated] (YARN-4686) MiniYARNCluster.start() returns before cluster is completely started

[ https://issues.apache.org/jira/browse/YARN-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Badger updated YARN-4686: -- Attachment: YARN-4686.003.patch Fixing a deadlock issue related to the Node Status Updater thread and the

[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178179#comment-15178179 ] Sidharta Seethana commented on YARN-4744: - Thanks, [~jlowe]. I would prefer to leav

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178165#comment-15178165 ] Varun Saxena commented on YARN-4712: Yeah even I think we should make minimal changes h

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178143#comment-15178143 ] Sunil G commented on YARN-4712: --- Hi [~Naganarasimha Garla] and [~varun_saxena] I think chang

[jira] [Commented] (YARN-4749) Generalize config file handling in container-executor

[ https://issues.apache.org/jira/browse/YARN-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178107#comment-15178107 ] Sidharta Seethana commented on YARN-4749: - Thanks, [~vvasudev]. These issues existe

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178065#comment-15178065 ] Sunil G commented on YARN-4712: --- [~varun_saxena] I was also planning to handle this pblm fro

[jira] [Commented] (YARN-4749) Generalize config file handling in container-executor

[ https://issues.apache.org/jira/browse/YARN-4749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178053#comment-15178053 ] Varun Vasudev commented on YARN-4749: - Thanks for the patch [~sidharta-s]. It looks mos

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178055#comment-15178055 ] Varun Saxena commented on YARN-4712: [~Naganarasimha], UNAVAILABLE related issue exists

[jira] [Updated] (YARN-4311) Removing nodes from include and exclude lists will not remove them from decommissioned nodes list

[ https://issues.apache.org/jira/browse/YARN-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kuhu Shukla updated YARN-4311: -- Attachment: YARN-4311-v11.patch Re-attaching the v11 patch with no changes to trigger another pre-commit

[jira] [Commented] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

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

[jira] [Updated] (YARN-4712) CPU Usage Metric is not captured properly in YARN-2928

[ https://issues.apache.org/jira/browse/YARN-4712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-4712: Attachment: YARN-4712-YARN-2928.v1.003.patch Hi [~djp] & [~varun_saxena], Please find the lat

[jira] [Updated] (YARN-4737) Use CSRF Filter in YARN

[ https://issues.apache.org/jira/browse/YARN-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Maron updated YARN-4737: - Attachment: YARN-4737.003.patch > Use CSRF Filter in YARN > --- > >

[jira] [Commented] (YARN-4744) Too many signal to container failure in case of LCE

[ https://issues.apache.org/jira/browse/YARN-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177872#comment-15177872 ] Jason Lowe commented on YARN-4744: -- Thanks for the patch! bq. In addition, logging in Pri

[jira] [Commented] (YARN-4700) ATS storage has one extra record each time the RM got restarted

[ https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177826#comment-15177826 ] Varun Saxena commented on YARN-4700: Thanks [~Naganarasimha] for the latest patch. +1,

[jira] [Updated] (YARN-4602) Scalable and Simple Message Service for YARN application

[ https://issues.apache.org/jira/browse/YARN-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4602: - Summary: Scalable and Simple Message Service for YARN application (was: Message/notification service betwe

[jira] [Commented] (YARN-4737) Use CSRF Filter in YARN

[ https://issues.apache.org/jira/browse/YARN-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177543#comment-15177543 ] Varun Vasudev commented on YARN-4737: - Thanks for the updated patch Jon. Some more fixe

[jira] [Commented] (YARN-3863) Support complex filters in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177526#comment-15177526 ] Varun Saxena commented on YARN-3863: Furthermore, in ATSv1 we had something called seco

[jira] [Commented] (YARN-3863) Support complex filters in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177521#comment-15177521 ] Varun Saxena commented on YARN-3863: Moreover, info also has associated info as well.

[jira] [Commented] (YARN-3863) Support complex filters in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177509#comment-15177509 ] Varun Saxena commented on YARN-3863: Thanks [~sjlee0] for the review. bq. One high lev

[jira] [Commented] (YARN-4754) Too many connection opened to TimelineServer while publishing entities

[ https://issues.apache.org/jira/browse/YARN-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177506#comment-15177506 ] Rohith Sharma K S commented on YARN-4754: - bq. I still see 2 places where we are no

[jira] [Commented] (YARN-4754) Too many connection opened to TimelineServer while publishing entities

[ https://issues.apache.org/jira/browse/YARN-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177478#comment-15177478 ] Rohith Sharma K S commented on YARN-4754: - As I see ATS logs, there were no excepti