[jira] [Updated] (YARN-6970) Add PoolInitializationException as retriable exception in FederationFacade

[ https://issues.apache.org/jira/browse/YARN-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-6970: - Component/s: federation > Add PoolInitializationException as retriable exception in

[jira] [Commented] (YARN-6956) preemption may only consider resource requests for one node

[ https://issues.apache.org/jira/browse/YARN-6956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119135#comment-16119135 ] Steven Rand commented on YARN-6956: --- Hi [~kasha], thanks for the suggestions. I would definitely like to

[jira] [Updated] (YARN-6820) Restrict read access to timelineservice v2 data

[ https://issues.apache.org/jira/browse/YARN-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-6820: - Attachment: YARN-6820-YARN-5355.003.patch Attaching patch 003 that addresses the review suggestions. -

[jira] [Commented] (YARN-6970) Add PoolInitializationException as retriable exception in FederationFacade

[ https://issues.apache.org/jira/browse/YARN-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119039#comment-16119039 ] Giovanni Matteo Fumarola commented on YARN-6970: {{SQLException}} in

[jira] [Created] (YARN-6974) Make CuratorBasedElectorService the default

Robert Kanter created YARN-6974: --- Summary: Make CuratorBasedElectorService the default Key: YARN-6974 URL: https://issues.apache.org/jira/browse/YARN-6974 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-6974) Make CuratorBasedElectorService the default

[ https://issues.apache.org/jira/browse/YARN-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-6974: --- Priority: Critical (was: Major) > Make CuratorBasedElectorService the default >

[jira] [Assigned] (YARN-6466) Provide shaded framework jar for containers

[ https://issues.apache.org/jira/browse/YARN-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen reassigned YARN-6466: Assignee: Haibo Chen > Provide shaded framework jar for containers >

[jira] [Commented] (YARN-6133) [ATSv2 Security] Renew delegation token for app automatically if an app collector is active

[ https://issues.apache.org/jira/browse/YARN-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119168#comment-16119168 ] Jian He commented on YARN-6133: --- lgtm overall, minor comments: - log the new expiration time also ? in case

[jira] [Commented] (YARN-6789) new api to get all supported resources from RM

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

[jira] [Commented] (YARN-6974) Make CuratorBasedElectorService the default

[ https://issues.apache.org/jira/browse/YARN-6974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119054#comment-16119054 ] Robert Kanter commented on YARN-6974: - [~jianhe], have you tried out the

[jira] [Commented] (YARN-6054) TimelineServer fails to start when some LevelDb state files are missing.

[ https://issues.apache.org/jira/browse/YARN-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119128#comment-16119128 ] Junping Du commented on YARN-6054: -- We actually hit this problem recently. Bump up to Critical as the

[jira] [Updated] (YARN-6054) TimelineServer fails to start when some LevelDb state files are missing.

[ https://issues.apache.org/jira/browse/YARN-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-6054: - Priority: Critical (was: Major) > TimelineServer fails to start when some LevelDb state files are

[jira] [Commented] (YARN-6820) Restrict read access to timelineservice v2 data

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

[jira] [Commented] (YARN-6892) Improve API implementation in Resources and DominantResourceCalculator in align to ResourceInformation

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

[jira] [Commented] (YARN-6820) Restrict read access to timelineservice v2 data

[ https://issues.apache.org/jira/browse/YARN-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119232#comment-16119232 ] Rohith Sharma K S commented on YARN-6820: - thanks for the patch! quick nit on the patch. #

[jira] [Commented] (YARN-6550) Capture launch_container.sh logs

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

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119165#comment-16119165 ] Vrushali C commented on YARN-6323: -- Any thoughts on this [~rohithsharma] [~varun_saxena] [~haibo.chen] >

[jira] [Commented] (YARN-6892) Improve API implementation in Resources and DominantResourceCalculator in align to ResourceInformation

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

[jira] [Updated] (YARN-6054) TimelineServer fails to start when some LevelDb state files are missing.

[ https://issues.apache.org/jira/browse/YARN-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-6054: --- Target Version/s: 2.9.0, 2.8.2 (was: 2.9.0) > TimelineServer fails to start when some LevelDb state

[jira] [Updated] (YARN-6054) TimelineServer fails to start when some LevelDb state files are missing.

[ https://issues.apache.org/jira/browse/YARN-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-6054: --- Fix Version/s: 2.8.2 > TimelineServer fails to start when some LevelDb state files are missing. >

[jira] [Commented] (YARN-6054) TimelineServer fails to start when some LevelDb state files are missing.

[ https://issues.apache.org/jira/browse/YARN-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119164#comment-16119164 ] Ravi Prakash commented on YARN-6054: Sure Junping! I took the liberty of cherry-picking the change into

[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

[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] [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-6852) [YARN-6223] Native code changes to support isolate GPU devices by using CGroups

[ https://issues.apache.org/jira/browse/YARN-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119277#comment-16119277 ] Miklos Szegedi commented on YARN-6852: -- +1 (non-binding) Thanks for the latest patch [~wangda]. >

[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.yarn_rm.log.zip RM log for this bug. > RM may allocate wrong AM Container for new

[jira] [Comment Edited] (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=16119337#comment-16119337 ] Yuqi Wang edited comment on YARN-6959 at 8/9/17 2:46 AM: - Attach RM log for this

[jira] [Commented] (YARN-6971) Clean up different ways to create resources

[ https://issues.apache.org/jira/browse/YARN-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119442#comment-16119442 ] Sunil G commented on YARN-6971: --- Post YARN-6775, we use SimpleResource for Resource.newInstance(). So for all

[jira] [Updated] (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:all-tabpanel ] Yeliang Cang updated YARN-6958: --- Attachment: YARN-6958.002.patch > Moving logging APIs over to slf4j in

[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=16119334#comment-16119334 ] Yuqi Wang commented on YARN-6959: - [~jianhe] Reproduce the race condition during below segment pipeline of

[jira] [Commented] (YARN-3254) HealthReport should include disk full information

[ https://issues.apache.org/jira/browse/YARN-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119415#comment-16119415 ] Sunil G commented on YARN-3254: --- Thanks [~suma.shivaprasad] Latest patch seems fine to me. I will commit the

[jira] [Updated] (YARN-3254) HealthReport should include disk full information

[ https://issues.apache.org/jira/browse/YARN-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3254: -- Fix Version/s: (was: 3.0.0-beta1) > HealthReport should include disk full information >

[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=16119291#comment-16119291 ] Chengbing Liu commented on YARN-6967: - Hi [~templedf], I don't think the message will be any longer. In

[jira] [Commented] (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:comment-tabpanel=16119322#comment-16119322 ] Yu-Tang Lin commented on YARN-6885: --- I noticed that reloadAllocations had the similar code, both will be

[jira] [Comment Edited] (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=16119337#comment-16119337 ] Yuqi Wang edited comment on YARN-6959 at 8/9/17 2:47 AM: - Attach RM log for this

[jira] [Comment Edited] (YARN-6896) Federation: routing REST invocations transparently to multiple RMs

[ https://issues.apache.org/jira/browse/YARN-6896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119263#comment-16119263 ] Carlo Curino edited comment on YARN-6896 at 8/9/17 12:57 AM: - Thaks

[jira] [Commented] (YARN-6896) Federation: routing REST invocations transparently to multiple RMs

[ https://issues.apache.org/jira/browse/YARN-6896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119263#comment-16119263 ] Carlo Curino commented on YARN-6896: Thaks [~giovanni.fumarola] for the contribution. Yetus seems

[jira] [Commented] (YARN-6033) Add support for sections in container-executor configuration file

[ https://issues.apache.org/jira/browse/YARN-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16119438#comment-16119438 ] Sunil G commented on YARN-6033: --- I am fine with latest patch. Thanks. > Add support for sections in

[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=16119366#comment-16119366 ] Yuqi Wang commented on YARN-6959: - Anyway, as YARN-5197, executing a double check to avoid potential race

[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=16119441#comment-16119441 ] Yeliang Cang commented on YARN-6958: Submit patch002 to remove LOG in TimelineStorageUtils.java. >

[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-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] [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-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] [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] [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] [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-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] [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-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-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-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] [Updated] (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:all-tabpanel ] Daniel Templeton updated YARN-6757: --- Affects Version/s: 2.8.1 > Refactor the usage of >

[jira] [Commented] (YARN-5695) New ResourceCalculator implementation that operates on vector of resources, but respect sum of ratios

[ https://issues.apache.org/jira/browse/YARN-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118795#comment-16118795 ] Tanuj Nayak commented on YARN-5695: --- Hello I would like to throw out an idea for implementing the ratio

[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=16118801#comment-16118801 ] Eric Badger commented on YARN-6930: --- Hey [~shaneku...@gmail.com], thanks for the patch! I have a few

[jira] [Updated] (YARN-6033) Add support for sections in container-executor configuration file

[ https://issues.apache.org/jira/browse/YARN-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-6033: - Attachment: YARN-6033.013.patch Thanks [~miklos.szeg...@cloudera.com], I attached ver.013 patch. For the

[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=16118804#comment-16118804 ] Hadoop QA commented on YARN-6964: - | (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=16118809#comment-16118809 ] Hadoop QA commented on YARN-6964: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6789) new api to get all supported resources from RM

[ https://issues.apache.org/jira/browse/YARN-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118819#comment-16118819 ] Wangda Tan commented on YARN-6789: -- Thanks [~sunilg], One comments regarding to ResourceTypeInfo: There's

[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.005.patch Fixed whitespace issue. > Fair scheduler misuses Resources

[jira] [Commented] (YARN-6879) TestLeafQueue.testDRFUserLimits() has commented out code

[ https://issues.apache.org/jira/browse/YARN-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118825#comment-16118825 ] Daniel Templeton commented on YARN-6879: LGTM +1 > TestLeafQueue.testDRFUserLimits() has commented

[jira] [Commented] (YARN-6926) FSSchedulerNode reservation conflict

[ https://issues.apache.org/jira/browse/YARN-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118831#comment-16118831 ] Yufei Gu commented on YARN-6926: Looking more deeply, this isn't a issue since method

[jira] [Resolved] (YARN-6926) FSSchedulerNode reservation conflict

[ https://issues.apache.org/jira/browse/YARN-6926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu resolved YARN-6926. Resolution: Invalid > FSSchedulerNode reservation conflict > > >

[jira] [Commented] (YARN-6033) Add support for sections in container-executor configuration file

[ https://issues.apache.org/jira/browse/YARN-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118834#comment-16118834 ] Miklos Szegedi commented on YARN-6033: -- +1 (non-binding). Thank you for the fixes, [~wangda]. Note:

[jira] [Commented] (YARN-6875) New aggregated log file format for YARN log aggregation.

[ https://issues.apache.org/jira/browse/YARN-6875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118840#comment-16118840 ] Wangda Tan commented on YARN-6875: -- [~jlowe], make sense, it looks like we have to come back to solution

[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.006.patch > Use cgroup to get container resource utilization >

[jira] [Created] (YARN-6969) Remove method getMinShareMemoryFraction and getPendingContainers in class FairSchedulerQueueInfo

Yufei Gu created YARN-6969: -- Summary: Remove method getMinShareMemoryFraction and getPendingContainers in class FairSchedulerQueueInfo Key: YARN-6969 URL: https://issues.apache.org/jira/browse/YARN-6969

[jira] [Updated] (YARN-6969) Remove method getMinShareMemoryFraction and getPendingContainers in class FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6969: --- Labels: newbie++ (was: ) > Remove method getMinShareMemoryFraction and getPendingContainers in class >

[jira] [Updated] (YARN-6969) Remove method getMinShareMemoryFraction and getPendingContainers in class FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-6969: --- Issue Type: Task (was: Bug) > Remove method getMinShareMemoryFraction and getPendingContainers in class >

[jira] [Updated] (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:all-tabpanel ] Daniel Templeton updated YARN-6757: --- Fix Version/s: 2.9.0 > Refactor the usage of >

[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=16118781#comment-16118781 ] Daniel Templeton commented on YARN-6757: Also committed to branch-2. > Refactor the usage of >

[jira] [Updated] (YARN-6879) TestLeafQueue.testDRFUserLimits() has commented out code

[ https://issues.apache.org/jira/browse/YARN-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Wang updated YARN-6879: -- Attachment: YARN-6879.001.patch > TestLeafQueue.testDRFUserLimits() has commented out code >

[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=16118836#comment-16118836 ] Jian He commented on YARN-6959: --- [~yqwang], thanks for the patch. one question is I'm wondering under what

[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=16118837#comment-16118837 ] Hadoop QA commented on YARN-6668: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6033) Add support for sections in container-executor configuration file

[ https://issues.apache.org/jira/browse/YARN-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16118843#comment-16118843 ] Wangda Tan commented on YARN-6033: -- [~sunilg]/[~vvasudev], could one of you help bless the latest patch.

[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] [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] [Commented] (YARN-6033) Add support for sections in container-executor configuration file

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

[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=16118864#comment-16118864 ] Hadoop QA commented on YARN-6668: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[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] [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-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] [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-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-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-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-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-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=16118590#comment-16118590 ] Hadoop QA commented on YARN-6953: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[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] [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] [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] [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-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] [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

  1   2   >