[jira] [Commented] (YARN-6897) Refactoring RMWebServices by moving some util methods to RMWebAppUtil

[ https://issues.apache.org/jira/browse/YARN-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118772#comment-16118772 ] Giovanni Matteo Fumarola commented on YARN-6897: Attached Branch2-v2 that fixed the javadoc

[jira] [Updated] (YARN-6897) Refactoring RMWebServices by moving some util methods to RMWebAppUtil

[ https://issues.apache.org/jira/browse/YARN-6897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-6897: --- Attachment: YARN-6897-branch-2.v2.patch > Refactoring RMWebServices by moving

[jira] [Commented] (YARN-6757) Refactor the usage of yarn.nodemanager.linux-container-executor.cgroups.mount-path

[ https://issues.apache.org/jira/browse/YARN-6757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118767#comment-16118767 ] Miklos Szegedi commented on YARN-6757: -- Yes please. > Refactor the usage of >

[jira] [Commented] (YARN-6515) Fix warnings from Spotbugs in hadoop-yarn-server-nodemanager

[ https://issues.apache.org/jira/browse/YARN-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118688#comment-16118688 ] Miklos Szegedi commented on YARN-6515: -- Thanks [~Naganarasimha], I created YARN-6968 for the Docker

[jira] [Created] (YARN-6968) Hard coded reference to an absolute pathname in org.apache.hadoop.yarn.server.nodemanager.containermanager.linux.runtime.DockerLinuxContainerRuntime.launchContainer(Contai

Miklos Szegedi created YARN-6968: Summary: Hard coded reference to an absolute pathname in org.apache.hadoop.yarn.server.nodemanager.containermanager.linux.runtime.DockerLinuxContainerRuntime.launchContainer(ContainerRuntimeContext)

[jira] [Updated] (YARN-6668) Use cgroup to get container resource utilization

[ https://issues.apache.org/jira/browse/YARN-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Miklos Szegedi updated YARN-6668: - Attachment: YARN-6668.005.patch Attaching the same patch again with my previous checkstyle fixes.

[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.004.patch Also noticed that the handling of {{FairSchedulerPolicy}} was

[jira] [Commented] (YARN-6668) Use cgroup to get container resource utilization

[ https://issues.apache.org/jira/browse/YARN-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118666#comment-16118666 ] Haibo Chen commented on YARN-6668: -- I see. Let's leave them then. > Use cgroup to get container resource

[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed

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

[jira] [Commented] (YARN-6668) Use cgroup to get container resource utilization

[ https://issues.apache.org/jira/browse/YARN-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118660#comment-16118660 ] Miklos Szegedi commented on YARN-6668: -- They are dead code but generate compiler warnings, that is why

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118650#comment-16118650 ] Miklos Szegedi commented on YARN-6930: -- Thank you [~shaneku...@gmail.com]. Yes, let's address the user

[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.003.patch Fixed related unit test failure. > Fair scheduler misuses

[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.002.patch In answering [~miklos.szeg...@cloudera.com]'s question, I

[jira] [Commented] (YARN-6953) Clean up ResourceUtils.setMinimumAllocationForMandatoryResources() and setMaximumAllocationForMandatoryResources()

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

[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=16118587#comment-16118587 ] Daniel Templeton commented on YARN-6964: Previously the code was:{code}Resource desiredShare =

[jira] [Assigned] (YARN-6885) AllocationFileLoaderService.loadQueue() should use a switch statement in the main tag parsing loop instead of the if/else-if/...

[ https://issues.apache.org/jira/browse/YARN-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Templeton reassigned YARN-6885: -- Assignee: Yu-Tang Lin > AllocationFileLoaderService.loadQueue() should use a switch

[jira] [Updated] (YARN-6953) Clean up ResourceUtils.setMinimumAllocationForMandatoryResources() and setMaximumAllocationForMandatoryResources()

[ https://issues.apache.org/jira/browse/YARN-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R updated YARN-6953: --- Attachment: YARN-6953-YARN-3926.004.patch > Clean up

[jira] [Commented] (YARN-6953) Clean up ResourceUtils.setMinimumAllocationForMandatoryResources() and setMaximumAllocationForMandatoryResources()

[ https://issues.apache.org/jira/browse/YARN-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118541#comment-16118541 ] Manikandan R commented on YARN-6953: Fixed whitespace issues. > Clean up

[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed

[ https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118533#comment-16118533 ] Manikandan R commented on YARN-65: -- Fixed whitespace issues. > Reduce RM app memory footprint once app has

[jira] [Updated] (YARN-65) Reduce RM app memory footprint once app has completed

[ https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R updated YARN-65: - Attachment: YARN-65.007.patch > Reduce RM app memory footprint once app has completed >

[jira] [Commented] (YARN-5534) Allow whitelisted volume mounts

[ https://issues.apache.org/jira/browse/YARN-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118526#comment-16118526 ] Eric Badger commented on YARN-5534: --- I emailed [~miklos.szeg...@cloudera.com] about this offline, but I'd

[jira] [Commented] (YARN-6361) FairScheduler: FSLeafQueue.fetchAppsWithDemand CPU usage is high with big queues

[ https://issues.apache.org/jira/browse/YARN-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118524#comment-16118524 ] YunFan Zhou commented on YARN-6361: --- [~yufeigu] [~Naganarasimha] Hi, Yufei, Naganarasimha. I've found

[jira] [Commented] (YARN-6967) Limit application attempt's diagnostic message size thoroughly

[ https://issues.apache.org/jira/browse/YARN-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118522#comment-16118522 ] Daniel Templeton commented on YARN-6967: Thanks for catching that, [~chengbing.liu]. In the

[jira] [Commented] (YARN-6668) Use cgroup to get container resource utilization

[ https://issues.apache.org/jira/browse/YARN-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118388#comment-16118388 ] Haibo Chen commented on YARN-6668: -- Sorry for being nit-picky. Can you fix the checkstyle issues? Also, I

[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed

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

[jira] [Commented] (YARN-6953) Clean up ResourceUtils.setMinimumAllocationForMandatoryResources() and setMaximumAllocationForMandatoryResources()

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

[jira] [Commented] (YARN-6967) Limit application attempt's diagnostic message size thoroughly

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

[jira] [Commented] (YARN-6953) Clean up ResourceUtils.setMinimumAllocationForMandatoryResources() and setMaximumAllocationForMandatoryResources()

[ https://issues.apache.org/jira/browse/YARN-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118304#comment-16118304 ] Manikandan R commented on YARN-6953: Fixed checkstyle issues. Attached patch for review. > Clean up

[jira] [Updated] (YARN-6953) Clean up ResourceUtils.setMinimumAllocationForMandatoryResources() and setMaximumAllocationForMandatoryResources()

[ https://issues.apache.org/jira/browse/YARN-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R updated YARN-6953: --- Attachment: YARN-6953-YARN-3926.003.patch > Clean up

[jira] [Commented] (YARN-65) Reduce RM app memory footprint once app has completed

[ https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118302#comment-16118302 ] Manikandan R commented on YARN-65: -- Fixed whitespace & checkstyle issues. Junit failures are not related to

[jira] [Updated] (YARN-65) Reduce RM app memory footprint once app has completed

[ https://issues.apache.org/jira/browse/YARN-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R updated YARN-65: - Attachment: YARN-65.006.patch > Reduce RM app memory footprint once app has completed >

[jira] [Commented] (YARN-6930) Admins should be able to explicitly enable specific LinuxContainerRuntime in the NodeManager

[ https://issues.apache.org/jira/browse/YARN-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118300#comment-16118300 ] Shane Kumpf commented on YARN-6930: --- Thanks for the comments, [~miklos.szeg...@cloudera.com]. I will get

[jira] [Assigned] (YARN-6965) Duplicate instantiation in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-6965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka reassigned YARN-6965: --- Assignee: Masahiro Tanaka Labels: newbie (was: ) Thanks [~masatana] for reporting

[jira] [Commented] (YARN-6873) Moving logging APIs over to slf4j in hadoop-yarn-server-applicationhistoryservice

[ https://issues.apache.org/jira/browse/YARN-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118286#comment-16118286 ] Yeliang Cang commented on YARN-6873: Thanks [~ajisakaa] for committing this, and thanks for [~vincent

[jira] [Commented] (YARN-6515) Fix warnings from Spotbugs in hadoop-yarn-server-nodemanager

[ https://issues.apache.org/jira/browse/YARN-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118280#comment-16118280 ] Shane Kumpf commented on YARN-6515: --- Thanks [~Naganarasimha] for the updated patch. With regard to the

[jira] [Updated] (YARN-6967) Limit application attempt's diagnostic message size thoroughly

[ https://issues.apache.org/jira/browse/YARN-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chengbing Liu updated YARN-6967: Attachment: YARN-6967.01.patch Attached the patch. > Limit application attempt's diagnostic message

[jira] [Created] (YARN-6967) Limit application attempt's diagnostic message size thoroughly

Chengbing Liu created YARN-6967: --- Summary: Limit application attempt's diagnostic message size thoroughly Key: YARN-6967 URL: https://issues.apache.org/jira/browse/YARN-6967 Project: Hadoop YARN

[jira] [Commented] (YARN-6958) Moving logging APIs over to slf4j in hadoop-yarn-server-timelineservice

[ https://issues.apache.org/jira/browse/YARN-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118206#comment-16118206 ] Akira Ajisaka commented on YARN-6958: - bq. LOG is unused in TimelineStorageUtils.java. Should we remove

[jira] [Commented] (YARN-6966) NodeManager metrics may return wrong negative values when NM restart

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

[jira] [Commented] (YARN-6515) Fix warnings from Spotbugs in hadoop-yarn-server-nodemanager

[ https://issues.apache.org/jira/browse/YARN-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118201#comment-16118201 ] Akira Ajisaka commented on YARN-6515: - Thanks [~Naganarasimha] for the comment and the patch. +1. >

[jira] [Commented] (YARN-6961) Remove commons-logging dependency from hadoop-yarn-server-applicationhistoryservice module

[ https://issues.apache.org/jira/browse/YARN-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118191#comment-16118191 ] Yeliang Cang commented on YARN-6961: Thank you for the review, [~ajisakaa]! > Remove commons-logging

[jira] [Commented] (YARN-6961) Remove commons-logging dependency from hadoop-yarn-server-applicationhistoryservice module

[ https://issues.apache.org/jira/browse/YARN-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118158#comment-16118158 ] Akira Ajisaka commented on YARN-6961: - +1, checking this in. > Remove commons-logging dependency from

[jira] [Updated] (YARN-6966) NodeManager metrics may return wrong negative values when NM restart

[ https://issues.apache.org/jira/browse/YARN-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Wang updated YARN-6966: Attachment: YARN-6966.001.patch > NodeManager metrics may return wrong negative values when NM restart >

[jira] [Commented] (YARN-6873) Moving logging APIs over to slf4j in hadoop-yarn-server-applicationhistoryservice

[ https://issues.apache.org/jira/browse/YARN-6873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118149#comment-16118149 ] Akira Ajisaka commented on YARN-6873: - +1, checking this in. > Moving logging APIs over to slf4j in >

[jira] [Commented] (YARN-6960) definition of active queue allows idle long-running apps to distort fair shares

[ https://issues.apache.org/jira/browse/YARN-6960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118146#comment-16118146 ] Steven Rand commented on YARN-6960: --- Yep, that concern is definitely valid. I wrote a patch that

[jira] [Updated] (YARN-6966) NodeManager metrics may return wrong negative values when NM restart

[ https://issues.apache.org/jira/browse/YARN-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Wang updated YARN-6966: Summary: NodeManager metrics may return wrong negative values when NM restart (was: NodeManager metrics may

[jira] [Created] (YARN-6966) NodeManager metrics may returning wrong negative values when after restart

Yang Wang created YARN-6966: --- Summary: NodeManager metrics may returning wrong negative values when after restart Key: YARN-6966 URL: https://issues.apache.org/jira/browse/YARN-6966 Project: Hadoop YARN

[jira] [Commented] (YARN-6959) RM may allocate wrong AM Container for new attempt

[ https://issues.apache.org/jira/browse/YARN-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118030#comment-16118030 ] Yuqi Wang commented on YARN-6959: - [~templedf] [~jianhe] Please help to review this. > RM may allocate

[jira] [Commented] (YARN-6959) RM may allocate wrong AM Container for new attempt

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

[jira] [Commented] (YARN-6959) RM may allocate wrong AM Container for new attempt

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

[jira] [Updated] (YARN-6959) RM may allocate wrong AM Container for new attempt

[ https://issues.apache.org/jira/browse/YARN-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuqi Wang updated YARN-6959: Attachment: YARN-6959.005.patch UT fail is not due to the patch. Re-trigger Jenkins since the UT is not

<    1   2