[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15385192#comment-15385192 ] Karthik Kambatla commented on YARN-4464: I know there is no right answer here. We should have

[jira] [Commented] (YARN-4888) Changes in RM AppSchedulingInfo for identifying resource-requests explicitly

[ https://issues.apache.org/jira/browse/YARN-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15381073#comment-15381073 ] Karthik Kambatla commented on YARN-4888: I like the idea of SchedulerKey. It also opens it upto a

[jira] [Updated] (YARN-5181) ClusterNodeTracker: add method to get list of nodes matching a specific resourceName

[ https://issues.apache.org/jira/browse/YARN-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5181: --- Attachment: yarn-5181-3.patch Patch to fix javac, javadoc and checkstyle warnings. >

[jira] [Commented] (YARN-5388) MAPREDUCE-6719 requires changes to DockerContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379927#comment-15379927 ] Karthik Kambatla commented on YARN-5388: Related-but-different question: [~sidharta-s], [~vinodkv]

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379922#comment-15379922 ] Karthik Kambatla commented on YARN-5047: There is one pending comment that needs addressing. I can

[jira] [Commented] (YARN-5380) NMTimelinePublisher should use getMemorySize instead of getMemory

[ https://issues.apache.org/jira/browse/YARN-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378791#comment-15378791 ] Karthik Kambatla commented on YARN-5380: I am experiencing technically difficulties checking this

[jira] [Commented] (YARN-5380) NMTimelinePublisher should use getMemorySize instead of getMemory

[ https://issues.apache.org/jira/browse/YARN-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378668#comment-15378668 ] Karthik Kambatla commented on YARN-5380: +1. Checking this in. > NMTimelinePublisher should use

[jira] [Updated] (YARN-5181) ClusterNodeTracker: add method to get list of nodes matching a specific resourceName

[ https://issues.apache.org/jira/browse/YARN-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5181: --- Attachment: yarn-5181-2.patch Thanks for the review, [~asuresh]. Updated patch incorporates

[jira] [Commented] (YARN-5182) MockNodes.newNodes creates one more node per rack than requested

[ https://issues.apache.org/jira/browse/YARN-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378614#comment-15378614 ] Karthik Kambatla commented on YARN-5182: Didn't realize this got in. Thanks [~varun_saxena] for

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378279#comment-15378279 ] Karthik Kambatla commented on YARN-5047: Sorry for missing this in my previous review.

[jira] [Created] (YARN-5380) NMTimelinePublisher should use getMemorySize instead of getMemory

Karthik Kambatla created YARN-5380: -- Summary: NMTimelinePublisher should use getMemorySize instead of getMemory Key: YARN-5380 URL: https://issues.apache.org/jira/browse/YARN-5380 Project: Hadoop

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378230#comment-15378230 ] Karthik Kambatla commented on YARN-5270: Just got around to looking at the patch. Looks good.

[jira] [Commented] (YARN-1994) Expose YARN/MR endpoints on multiple interfaces

[ https://issues.apache.org/jira/browse/YARN-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15377882#comment-15377882 ] Karthik Kambatla commented on YARN-1994: [~arpitagarwal] - what are your thoughts on setting the

[jira] [Resolved] (YARN-5371) FairScheduer ContinuousScheduling thread throws Exception

[ https://issues.apache.org/jira/browse/YARN-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-5371. Resolution: Duplicate > FairScheduer ContinuousScheduling thread throws Exception >

[jira] [Updated] (YARN-5371) FairScheduer ContinuousScheduling thread throws Exception

[ https://issues.apache.org/jira/browse/YARN-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5371: --- Priority: Critical (was: Major) > FairScheduer ContinuousScheduling thread throws Exception >

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375809#comment-15375809 ] Karthik Kambatla commented on YARN-4212: I am perfectly open to working on YARN-5264 first. Happy

[jira] [Commented] (YARN-5304) Ship single node HBase config option with single startup command

[ https://issues.apache.org/jira/browse/YARN-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375807#comment-15375807 ] Karthik Kambatla commented on YARN-5304: I spoke to [~esteban] about this. In his opinion, the

[jira] [Commented] (YARN-5343) TestContinuousScheduling#testSortedNodes fail intermittently

[ https://issues.apache.org/jira/browse/YARN-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375800#comment-15375800 ] Karthik Kambatla commented on YARN-5343: I remember [~yufeigu] was looking into this. [~yufeigu] -

[jira] [Commented] (YARN-4876) [Phase 1] Decoupled Init / Destroy of Containers from Start / Stop

[ https://issues.apache.org/jira/browse/YARN-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15375276#comment-15375276 ] Karthik Kambatla commented on YARN-4876: I understand there were more discussions on the design and

[jira] [Commented] (YARN-5215) Scheduling containers based on external load in the servers

[ https://issues.apache.org/jira/browse/YARN-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365506#comment-15365506 ] Karthik Kambatla commented on YARN-5215: YARN-1011 and I assume YARN-5202 primarily target using

[jira] [Commented] (YARN-5215) Scheduling containers based on external load in the servers

[ https://issues.apache.org/jira/browse/YARN-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364765#comment-15364765 ] Karthik Kambatla commented on YARN-5215: Spoke to Inigo offline at the summit. My primary concern

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15363498#comment-15363498 ] Karthik Kambatla commented on YARN-4212: Took a quick look at the patch. One high-level question:

[jira] [Updated] (YARN-5308) FairScheduler: Move continuous scheduling related tests to TestContinuousScheduling

[ https://issues.apache.org/jira/browse/YARN-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5308: --- Summary: FairScheduler: Move continuous scheduling related tests to TestContinuousScheduling

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15360269#comment-15360269 ] Karthik Kambatla commented on YARN-5270: Will take a closer look at the patch early next week. Is

[jira] [Created] (YARN-5308) FairScheduler: Move continuous scheduling related threads to TestContinuousScheduling

Karthik Kambatla created YARN-5308: -- Summary: FairScheduler: Move continuous scheduling related threads to TestContinuousScheduling Key: YARN-5308 URL: https://issues.apache.org/jira/browse/YARN-5308

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359850#comment-15359850 ] Karthik Kambatla commented on YARN-5047: [~rchiang] - the latest patch looks good. Is the CS test

[jira] [Commented] (YARN-4568) Fix message when NodeManager runs into errors initializing the recovery directory

[ https://issues.apache.org/jira/browse/YARN-4568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15359769#comment-15359769 ] Karthik Kambatla commented on YARN-4568: +1 > Fix message when NodeManager runs into errors

[jira] [Updated] (YARN-5293) Disable preemption per queue per partition

[ https://issues.apache.org/jira/browse/YARN-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5293: --- Component/s: capacityscheduler > Disable preemption per queue per partition >

[jira] [Commented] (YARN-5281) Explore supporting a simpler back-end implementation for ATS v2

[ https://issues.apache.org/jira/browse/YARN-5281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15343694#comment-15343694 ] Karthik Kambatla commented on YARN-5281: Thanks for filing this, [~jrottinghuis]. Copying contents

[jira] [Commented] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337589#comment-15337589 ] Karthik Kambatla commented on YARN-5270: YARN-5077 has been fixed to use the right version of

[jira] [Commented] (YARN-4844) Add getMemorySize/getVirtualCoresSize to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337574#comment-15337574 ] Karthik Kambatla commented on YARN-4844: Let me follow up on YARN-5270. > Add

[jira] [Updated] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with zero fairshare

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5077: --- Summary: Fix FSLeafQueue#getFairShare() for queues with zero fairshare (was: Fix

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337554#comment-15337554 ] Karthik Kambatla commented on YARN-5077: +1. Checking this in. > Fix FSLeafQueue#getFairShare()

[jira] [Updated] (YARN-5270) Solve miscellaneous issues caused by YARN-4844

[ https://issues.apache.org/jira/browse/YARN-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5270: --- Priority: Blocker (was: Major) > Solve miscellaneous issues caused by YARN-4844 >

[jira] [Commented] (YARN-5082) Limit ContainerId increase in fair scheduler if the num of node app reserved reached the limit

[ https://issues.apache.org/jira/browse/YARN-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15337547#comment-15337547 ] Karthik Kambatla commented on YARN-5082: +1. Checking this in. > Limit ContainerId increase in

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335226#comment-15335226 ] Karthik Kambatla commented on YARN-5077: The javac warning appears to be due to the changes

[jira] [Commented] (YARN-4844) Add getMemorySize/getVirtualCoresSize to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335221#comment-15335221 ] Karthik Kambatla commented on YARN-4844: Also, noticed that some of the helper methods in Resources

[jira] [Commented] (YARN-4844) Add getMemorySize/getVirtualCoresSize to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335220#comment-15335220 ] Karthik Kambatla commented on YARN-4844: Also, do you think we can get this in 2.9 instead so we

[jira] [Commented] (YARN-4844) Add getMemorySize/getVirtualCoresSize to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335197#comment-15335197 ] Karthik Kambatla commented on YARN-4844: Sorry for coming in late. Stumbled on this by way of

[jira] [Commented] (YARN-5264) Use FSQueue to store queue-specific information

[ https://issues.apache.org/jira/browse/YARN-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334188#comment-15334188 ] Karthik Kambatla commented on YARN-5264: This should make the code much cleaner. Once we are done

[jira] [Commented] (YARN-5215) Scheduling containers based on external load in the servers

[ https://issues.apache.org/jira/browse/YARN-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330719#comment-15330719 ] Karthik Kambatla commented on YARN-5215: We happen to have a similar low-latency framework running

[jira] [Commented] (YARN-5215) Scheduling containers based on external load in the servers

[ https://issues.apache.org/jira/browse/YARN-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330588#comment-15330588 ] Karthik Kambatla commented on YARN-5215: I am generally supportive of this. Few questions to

[jira] [Commented] (YARN-5241) FairScheduler fails to release container it is just allocated

[ https://issues.apache.org/jira/browse/YARN-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330540#comment-15330540 ] Karthik Kambatla commented on YARN-5241: Thanks for updating the patch, [~chenfolin]. I understand

[jira] [Commented] (YARN-5241) FairScheduler fails to release container it is just allocated

[ https://issues.apache.org/jira/browse/YARN-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15330542#comment-15330542 ] Karthik Kambatla commented on YARN-5241: Oh, and it would be good to add a unit test. >

[jira] [Updated] (YARN-5241) FairScheduler fails to release container it is just allocated

[ https://issues.apache.org/jira/browse/YARN-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5241: --- Summary: FairScheduler fails to release container it is just allocated (was: FairScheduler

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326645#comment-15326645 ] Karthik Kambatla commented on YARN-5124: Done. Pushed to branch-2. Thanks [~jianhe] for pointing

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326644#comment-15326644 ] Karthik Kambatla commented on YARN-5124: +1 to the addendum. Just compiled and ran

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326629#comment-15326629 ] Karthik Kambatla commented on YARN-5077: Interesting approach on the last patch. Few comments: #

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15326497#comment-15326497 ] Karthik Kambatla commented on YARN-5124: Looks good to me. +1. > Modify AMRMClient to set the

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325747#comment-15325747 ] Karthik Kambatla commented on YARN-5124: Almost there. One nit - AMRMClientAsyncImpl change is

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325276#comment-15325276 ] Karthik Kambatla commented on YARN-5124: Comments on the latest patch: # AMRMClient: Javdoc for the

[jira] [Updated] (YARN-5234) ResourceManager REST API missing descriptions for what's returned when using Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-5234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5234: --- Component/s: resourcemanager fairscheduler > ResourceManager REST API missing

[jira] [Assigned] (YARN-5230) Document FairScheduler's allowPreemptionFrom flag

[ https://issues.apache.org/jira/browse/YARN-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-5230: -- Assignee: Karthik Kambatla > Document FairScheduler's allowPreemptionFrom flag >

[jira] [Updated] (YARN-5230) allowPreemptionFrom flag not mentioned in HadoopFair Scheduler documents

[ https://issues.apache.org/jira/browse/YARN-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5230: --- Component/s: fairscheduler > allowPreemptionFrom flag not mentioned in HadoopFair Scheduler

[jira] [Updated] (YARN-5230) allowPreemptionFrom flag not mentioned in HadoopFair Scheduler documents

[ https://issues.apache.org/jira/browse/YARN-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5230: --- Summary: allowPreemptionFrom flag not mentioned in HadoopFair Scheduler documents (was:

[jira] [Updated] (YARN-5230) Document FairScheduler's allowPreemptionFrom flag

[ https://issues.apache.org/jira/browse/YARN-5230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5230: --- Summary: Document FairScheduler's allowPreemptionFrom flag (was: allowPreemptionFrom flag not

[jira] [Commented] (YARN-5124) Modify AMRMClient to set the ExecutionType in the ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15316114#comment-15316114 ] Karthik Kambatla commented on YARN-5124: [~asuresh] - excuse the delay in getting around to this.

[jira] [Commented] (YARN-5180) Add ensureExecutionType boolean flag in ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311852#comment-15311852 ] Karthik Kambatla commented on YARN-5180: +1. I am not particular, but I too like enforce over

[jira] [Commented] (YARN-5180) Add ensureExecutionType boolean flag in ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311377#comment-15311377 ] Karthik Kambatla commented on YARN-5180: bq. do we want the newInstance() of the

[jira] [Commented] (YARN-5180) Add ensureExecutionType boolean flag in ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311278#comment-15311278 ] Karthik Kambatla commented on YARN-5180: bq. considering we might introduce more types later on,

[jira] [Commented] (YARN-5180) Add ensureExecutionType boolean flag in ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311202#comment-15311202 ] Karthik Kambatla commented on YARN-5180: Can we get #2 of my previous comment fixed. And, by

[jira] [Updated] (YARN-5046) [Umbrella] De-duplicate scheduler code

[ https://issues.apache.org/jira/browse/YARN-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5046: --- Summary: [Umbrella] De-duplicate scheduler code (was: [Umbrella] Refactor scheduler code) >

[jira] [Commented] (YARN-5188) FairScheduler performance bug

[ https://issues.apache.org/jira/browse/YARN-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15309241#comment-15309241 ] Karthik Kambatla commented on YARN-5188: [~chenfolin] - thanks for reporting and working on this.

[jira] [Commented] (YARN-5180) Add ensureExecutionType boolean flag in ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308759#comment-15308759 ] Karthik Kambatla commented on YARN-5180: Thanks for working on this, Arun. Comments: # Would

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15308238#comment-15308238 ] Karthik Kambatla commented on YARN-5077: My bad again. I should probably take some time off.

[jira] [Created] (YARN-5184) Fix up incompatible changes introduced in YARN-2882

Karthik Kambatla created YARN-5184: -- Summary: Fix up incompatible changes introduced in YARN-2882 Key: YARN-5184 URL: https://issues.apache.org/jira/browse/YARN-5184 Project: Hadoop YARN

[jira] [Commented] (YARN-5182) MockNodes.newNodes creates one more node per rack than requested

[ https://issues.apache.org/jira/browse/YARN-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307389#comment-15307389 ] Karthik Kambatla commented on YARN-5182: Test test failures are known test failures. >

[jira] [Commented] (YARN-5182) MockNodes.newNodes creates one more node per rack than requested

[ https://issues.apache.org/jira/browse/YARN-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15307282#comment-15307282 ] Karthik Kambatla commented on YARN-5182: The patch on YARN-5181 tests the correctness of this. >

[jira] [Updated] (YARN-5181) ClusterNodeTracker: add method to get list of nodes matching a specific resourceName

[ https://issues.apache.org/jira/browse/YARN-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5181: --- Attachment: yarn-5181-1.patch Straight-forward patch that caches the node names in

[jira] [Updated] (YARN-5182) MockNodes.newNodes creates one more node per rack than requested

[ https://issues.apache.org/jira/browse/YARN-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5182: --- Attachment: yarn-5182-1.patch > MockNodes.newNodes creates one more node per rack than

[jira] [Created] (YARN-5182) MockNodes.newNodes creates one more node per rack than requested

Karthik Kambatla created YARN-5182: -- Summary: MockNodes.newNodes creates one more node per rack than requested Key: YARN-5182 URL: https://issues.apache.org/jira/browse/YARN-5182 Project: Hadoop

[jira] [Created] (YARN-5181) ClusterNodeTracker: add method to get list of nodes matching a specific resourceName

Karthik Kambatla created YARN-5181: -- Summary: ClusterNodeTracker: add method to get list of nodes matching a specific resourceName Key: YARN-5181 URL: https://issues.apache.org/jira/browse/YARN-5181

[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306987#comment-15306987 ] Karthik Kambatla commented on YARN-4464: [~Naganarasimha Garla], [~jianhe] - we should converge on

[jira] [Commented] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306981#comment-15306981 ] Karthik Kambatla commented on YARN-5047: Thanks for the update, Ray. Almost there. Comments: # The

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15306962#comment-15306962 ] Karthik Kambatla commented on YARN-5077: The maxShare corresponds to maxResources. It is not

[jira] [Commented] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15305430#comment-15305430 ] Karthik Kambatla commented on YARN-5132: Checking this in. > Exclude generated protobuf sources

[jira] [Commented] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303533#comment-15303533 ] Karthik Kambatla commented on YARN-5132: +1. Will check this in tomorrow (Fri) morning. >

[jira] [Commented] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303206#comment-15303206 ] Karthik Kambatla commented on YARN-5035: Pulled this into branch-2.8 as well. > FairScheduler:

[jira] [Updated] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5035: --- Fix Version/s: (was: 2.9.0) 2.8.0 > FairScheduler: Adjust maxAssign

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302540#comment-15302540 ] Karthik Kambatla commented on YARN-5077: Updating the way we calculate maxAMResource seems like a

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301649#comment-15301649 ] Karthik Kambatla commented on YARN-5077: Actually, thinking more about this, I am beginning to

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301628#comment-15301628 ] Karthik Kambatla commented on YARN-5077: And, another thing came to mind. Sorry about this. The

[jira] [Updated] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5035: --- Attachment: yarn-5035-3.patch Updated patch to use fitsIn. Note that fitsIn checks <= and not

[jira] [Commented] (YARN-4866) FairScheduler: AMs can consume all vcores leading to a livelock when using FAIR policy

[ https://issues.apache.org/jira/browse/YARN-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301521#comment-15301521 ] Karthik Kambatla commented on YARN-4866: +1. Checking this in. > FairScheduler: AMs can consume

[jira] [Commented] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301516#comment-15301516 ] Karthik Kambatla commented on YARN-5035: The unit test failures are unrelated. [~templedf] - are

[jira] [Commented] (YARN-4271) Make the NodeManager's health checker service pluggable

[ https://issues.apache.org/jira/browse/YARN-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301492#comment-15301492 ] Karthik Kambatla commented on YARN-4271: As I see things, YARN-5137 and this JIRA are slightly

[jira] [Updated] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5035: --- Hadoop Flags: Incompatible change Release Note: Introducing a new configuration

[jira] [Updated] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5035: --- Attachment: yarn-5035-2.patch Updated patch that improves the test and the docs. >

[jira] [Comment Edited] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301173#comment-15301173 ] Karthik Kambatla edited comment on YARN-5132 at 5/26/16 12:06 AM: -- I see

[jira] [Commented] (YARN-5132) Exclude generated protobuf sources from YARN Javadoc build

[ https://issues.apache.org/jira/browse/YARN-5132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301173#comment-15301173 ] Karthik Kambatla commented on YARN-5132: I see several reasons to get this in: # As Subru, Chris

[jira] [Commented] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301158#comment-15301158 ] Karthik Kambatla commented on YARN-5035: bq. Looks to me like you can never assign the last

[jira] [Updated] (YARN-5035) FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on

[ https://issues.apache.org/jira/browse/YARN-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5035: --- Attachment: yarn-5035-1.patch Patch that implements dynamic max assign. > FairScheduler:

[jira] [Commented] (YARN-4599) Set OOM control for memory cgroups

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300607#comment-15300607 ] Karthik Kambatla commented on YARN-4599: bq. yes, I'd like to update our patch in one or two weeks.

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues is not allowed to be 'Fair' policy if its children have the "drf" policy

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300587#comment-15300587 ] Karthik Kambatla commented on YARN-4212: Thanks for working on this, Yufei. The scheduling policy

[jira] [Commented] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300512#comment-15300512 ] Karthik Kambatla commented on YARN-3344: +1, checking this in. > procfs stat file is not in the

[jira] [Updated] (YARN-3344) Fix warning - procfs stat file is not in the expected format

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3344: --- Summary: Fix warning - procfs stat file is not in the expected format (was: Fix warning

[jira] [Updated] (YARN-3344) Fix warning "procfs stat file is not in the expected format"

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3344: --- Summary: Fix warning "procfs stat file is not in the expected format" (was: procfs stat file

[jira] [Updated] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3344: --- Assignee: Ravindra Kumar Naik (was: Akira AJISAKA) > procfs stat file is not in the expected

[jira] [Commented] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300466#comment-15300466 ] Karthik Kambatla commented on YARN-5104: I wonder if the other failure is an environment issue. >

[jira] [Comment Edited] (YARN-4767) Network issues can cause persistent RM UI outage

[ https://issues.apache.org/jira/browse/YARN-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15300422#comment-15300422 ] Karthik Kambatla edited comment on YARN-4767 at 5/25/16 5:01 PM: - The patch

<    2   3   4   5   6   7   8   9   10   11   >