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

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

[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&focusedCommentId=15300422#comment-15300422 ] Karthik Kambatla edited comment on YARN-4767 at 5/25/16 5:01 PM:

[jira] [Updated] (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:all-tabpanel ] Karthik Kambatla updated YARN-4767: --- Target Version/s: 2.8.0 > Network issues can cause persistent RM UI outage > --

[jira] [Commented] (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&focusedCommentId=15300422#comment-15300422 ] Karthik Kambatla commented on YARN-4767: The patch looks good to me, but for the fo

[jira] [Updated] (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:all-tabpanel ] Karthik Kambatla updated YARN-4767: --- Affects Version/s: (was: 2.9.0) 2.7.2 > Network issues can cause per

[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&focusedCommentId=15300124#comment-15300124 ] Karthik Kambatla commented on YARN-4866: bq. The parameter queue is used for recurs

[jira] [Commented] (YARN-5123) SQL based RM state store

[ https://issues.apache.org/jira/browse/YARN-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300089#comment-15300089 ] Karthik Kambatla commented on YARN-5123: Thanks for the clarification, [~lavkesh].

[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&focusedCommentId=15300076#comment-15300076 ] Karthik Kambatla commented on YARN-5077: Actually, one last nit. Sorry for not sugg

[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&focusedCommentId=15299463#comment-15299463 ] Karthik Kambatla commented on YARN-4599: Oh, and any interest in contributing to do

[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&focusedCommentId=15299461#comment-15299461 ] Karthik Kambatla commented on YARN-4599: [~sandflee] - more details on your experie

[jira] [Commented] (YARN-5139) [Umbrella] Move YARN scheduler towards global scheduler

[ https://issues.apache.org/jira/browse/YARN-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299456#comment-15299456 ] Karthik Kambatla commented on YARN-5139: I am less particular about using ClusterNo

[jira] [Assigned] (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:all-tabpanel ] Karthik Kambatla reassigned YARN-5077: -- Assignee: Karthik Kambatla (was: Yufei Gu) > Fix FSLeafQueue#getFairShare() for queues

[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&focusedCommentId=15299112#comment-15299112 ] Karthik Kambatla commented on YARN-5077: In that case, should we update the way han

[jira] [Commented] (YARN-5139) [Umbrella] Move YARN scheduler towards global scheduler

[ https://issues.apache.org/jira/browse/YARN-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299044#comment-15299044 ] Karthik Kambatla commented on YARN-5139: Oh, and can we see how we can evolved Clus

[jira] [Comment Edited] (YARN-5139) [Umbrella] Move YARN scheduler towards global scheduler

[ https://issues.apache.org/jira/browse/YARN-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299024#comment-15299024 ] Karthik Kambatla edited comment on YARN-5139 at 5/24/16 10:07 PM: ---

[jira] [Commented] (YARN-5139) [Umbrella] Move YARN scheduler towards global scheduler

[ https://issues.apache.org/jira/browse/YARN-5139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299024#comment-15299024 ] Karthik Kambatla commented on YARN-5139: [~leftnoteasy] - thanks for filing this.

[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&focusedCommentId=15298672#comment-15298672 ] Karthik Kambatla commented on YARN-4866: Patch looks close. # Shouldn't isVCoreOver

[jira] [Commented] (YARN-4878) Expose scheduling policy and max running apps over JMX for Yarn queues

[ https://issues.apache.org/jira/browse/YARN-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298613#comment-15298613 ] Karthik Kambatla commented on YARN-4878: +1, checking this in. > Expose schedulin

[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&focusedCommentId=15298598#comment-15298598 ] Karthik Kambatla commented on YARN-4464: My preference for changing defaults is of

[jira] [Updated] (YARN-4979) FSAppAttempt demand calculation considers demands at multiple locality levels different

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4979: --- Summary: FSAppAttempt demand calculation considers demands at multiple locality levels differen

[jira] [Commented] (YARN-4979) FSAppAttempt adds duplicate ResourceRequest to demand in updateDemand.

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297118#comment-15297118 ] Karthik Kambatla commented on YARN-4979: +1, checking this in. > FSAppAttempt add

[jira] [Commented] (YARN-4979) FSAppAttempt adds duplicate ResourceRequest to demand in updateDemand.

[ https://issues.apache.org/jira/browse/YARN-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297107#comment-15297107 ] Karthik Kambatla commented on YARN-4979: More importantly, the demand could be wron

[jira] [Commented] (YARN-5087) Expose API to allow AM to request for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296955#comment-15296955 ] Karthik Kambatla commented on YARN-5087: A single {{UpdateContainerRequest}} seems

[jira] [Commented] (YARN-5123) SQL based RM state store

[ https://issues.apache.org/jira/browse/YARN-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296556#comment-15296556 ] Karthik Kambatla commented on YARN-5123: I am not a SQL expert, but I don't quite u

[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&focusedCommentId=15296548#comment-15296548 ] Karthik Kambatla commented on YARN-5047: Thanks for the review, Wangda. Agree tha

[jira] [Commented] (YARN-5085) Add support for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296542#comment-15296542 ] Karthik Kambatla commented on YARN-5085: Sounds reasonable. > Add support for cha

[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&focusedCommentId=15292349#comment-15292349 ] Karthik Kambatla commented on YARN-4464: bq. The patch is changing the config for m

[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&focusedCommentId=15292113#comment-15292113 ] Karthik Kambatla commented on YARN-4464: +1. Will commit this to trunk tomorrow if

[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&focusedCommentId=15290416#comment-15290416 ] Karthik Kambatla commented on YARN-5047: Excited to see progress here. Thanks for w

[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&focusedCommentId=15289906#comment-15289906 ] Karthik Kambatla commented on YARN-4464: bq. If we change the default value to 0 Th

[jira] [Commented] (YARN-4494) Recover completed apps asynchronously

[ https://issues.apache.org/jira/browse/YARN-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289900#comment-15289900 ] Karthik Kambatla commented on YARN-4494: I am okay with asynchronous recovery so lo

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15289885#comment-15289885 ] Karthik Kambatla commented on YARN-4882: Thanks for your inputs, [~jlowe]. I would

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

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5047: --- Summary: Refactor nodeUpdate across schedulers (was: Refactor nodeUpdate() from FairScheduler,

[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&focusedCommentId=15287817#comment-15287817 ] Karthik Kambatla commented on YARN-5077: This has been a long standing inconvenienc

[jira] [Created] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

Karthik Kambatla created YARN-5106: -- Summary: Provide a builder interface for FairScheduler allocations for use in tests Key: YARN-5106 URL: https://issues.apache.org/jira/browse/YARN-5106 Project: H

[jira] [Commented] (YARN-4308) ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats

[ https://issues.apache.org/jira/browse/YARN-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287771#comment-15287771 ] Karthik Kambatla commented on YARN-4308: Given we expect to see -1 exactly once, do

[jira] [Commented] (YARN-4457) Cleanup unchecked types for EventHandler

[ https://issues.apache.org/jira/browse/YARN-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287757#comment-15287757 ] Karthik Kambatla commented on YARN-4457: Thanks for taking the time to clean these

[jira] [Commented] (YARN-4494) Recover completed apps asynchronously

[ https://issues.apache.org/jira/browse/YARN-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287681#comment-15287681 ] Karthik Kambatla commented on YARN-4494: [~sunilg] - can you elaborate on the on-de

[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&focusedCommentId=15287674#comment-15287674 ] Karthik Kambatla commented on YARN-4464: [~jianhe] - do you think it is okay to low

[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&focusedCommentId=15287660#comment-15287660 ] Karthik Kambatla commented on YARN-4866: Thanks for working on this, Yufei. Comment

[jira] [Commented] (YARN-5085) Add support for change of container ExecutionType

[ https://issues.apache.org/jira/browse/YARN-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285930#comment-15285930 ] Karthik Kambatla commented on YARN-5085: Are you proposing the AM be able to change

[jira] [Commented] (YARN-5079) [Umbrella] Native YARN framework layer for services and beyond

[ https://issues.apache.org/jira/browse/YARN-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15282987#comment-15282987 ] Karthik Kambatla commented on YARN-5079: I agree with Hitesh. The mailing list migh

[jira] [Commented] (YARN-4971) RM fails to re-bind to wildcard IP after failover in multi homed clusters

[ https://issues.apache.org/jira/browse/YARN-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281097#comment-15281097 ] Karthik Kambatla commented on YARN-4971: I must be missing something, but can't fig

[jira] [Updated] (YARN-4995) FairScheduler: Display per-queue demand on the scheduler page

[ https://issues.apache.org/jira/browse/YARN-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4995: --- Summary: FairScheduler: Display per-queue demand on the scheduler page (was: FairScheduler: Di

[jira] [Updated] (YARN-4995) FairScheduler: Display demand resource for queues on the scheduler page

[ https://issues.apache.org/jira/browse/YARN-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4995: --- Summary: FairScheduler: Display demand resource for queues on the scheduler page (was: Fair Sc

[jira] [Commented] (YARN-4995) Fair Scheduler: Display demand resource for queues on the scheduler page

[ https://issues.apache.org/jira/browse/YARN-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281038#comment-15281038 ] Karthik Kambatla commented on YARN-4995: Cool. Looks good per my previous review. C

[jira] [Commented] (YARN-5046) [Umbrella] Refactor scheduler code

[ https://issues.apache.org/jira/browse/YARN-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280842#comment-15280842 ] Karthik Kambatla commented on YARN-5046: Thanks for picking this up, [~rchiang]. Th

[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&focusedCommentId=15280807#comment-15280807 ] Karthik Kambatla commented on YARN-4599: Yes, I meant containers. My proposal was

[jira] [Commented] (YARN-4882) Change the log level to DEBUG for recovering completed applications

[ https://issues.apache.org/jira/browse/YARN-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278993#comment-15278993 ] Karthik Kambatla commented on YARN-4882: Was debugging something else in the RM and

[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&focusedCommentId=15269318#comment-15269318 ] Karthik Kambatla commented on YARN-5035: bq. I was thinking of integrating YARN-405

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

Karthik Kambatla created YARN-5035: -- Summary: FairScheduler: Adjust maxAssign dynamically when assignMultiple is turned on Key: YARN-5035 URL: https://issues.apache.org/jira/browse/YARN-5035 Project:

[jira] [Commented] (YARN-5031) Add a conf to disable container reservation

[ https://issues.apache.org/jira/browse/YARN-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268879#comment-15268879 ] Karthik Kambatla commented on YARN-5031: By container reservation, do you mean the

[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&focusedCommentId=15268875#comment-15268875 ] Karthik Kambatla commented on YARN-4464: [~magnum] - any chance you are running int

[jira] [Commented] (YARN-5002) getApplicationReport call may raise NPE

[ https://issues.apache.org/jira/browse/YARN-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267189#comment-15267189 ] Karthik Kambatla commented on YARN-5002: For ACLs, I would like to think we enforce

[jira] [Created] (YARN-5030) Revisit o.a.h.y.s.rm.scheduler.ResourceUsage

Karthik Kambatla created YARN-5030: -- Summary: Revisit o.a.h.y.s.rm.scheduler.ResourceUsage Key: YARN-5030 URL: https://issues.apache.org/jira/browse/YARN-5030 Project: Hadoop YARN Issue Type

[jira] [Commented] (YARN-4995) Fair Scheduler: Display demand resource for queues on the scheduler page

[ https://issues.apache.org/jira/browse/YARN-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267026#comment-15267026 ] Karthik Kambatla commented on YARN-4995: Actually, let us wait until we get a Jenki

[jira] [Commented] (YARN-4995) Fair Scheduler: Display demand resource for queues on the scheduler page

[ https://issues.apache.org/jira/browse/YARN-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15267025#comment-15267025 ] Karthik Kambatla commented on YARN-4995: +1, checking this in. > Fair Scheduler:

[jira] [Created] (YARN-5028) RMStateStore should trim down app state for completed applications

Karthik Kambatla created YARN-5028: -- Summary: RMStateStore should trim down app state for completed applications Key: YARN-5028 URL: https://issues.apache.org/jira/browse/YARN-5028 Project: Hadoop YA

[jira] [Commented] (YARN-5008) LeveldbRMStateStore database can grow substantially leading to long recovery times

[ https://issues.apache.org/jira/browse/YARN-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266859#comment-15266859 ] Karthik Kambatla commented on YARN-5008: By the way, this also brings up another is

[jira] [Commented] (YARN-4804) [Umbrella] Improve test run duration

[ https://issues.apache.org/jira/browse/YARN-4804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260465#comment-15260465 ] Karthik Kambatla commented on YARN-4804: We shaved off 10 minutes through YARN-4805

[jira] [Updated] (YARN-4807) MockAM#waitForState sleep duration is too long

[ https://issues.apache.org/jira/browse/YARN-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4807: --- Labels: (was: newbie) > MockAM#waitForState sleep duration is too long >

[jira] [Commented] (YARN-4807) MockAM#waitForState sleep duration is too long

[ https://issues.apache.org/jira/browse/YARN-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260452#comment-15260452 ] Karthik Kambatla commented on YARN-4807: +1, checking this in. > MockAM#waitForSt

[jira] [Commented] (YARN-4676) Automatic and Asynchronous Decommissioning Nodes Status Tracking

[ https://issues.apache.org/jira/browse/YARN-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260441#comment-15260441 ] Karthik Kambatla commented on YARN-4676: Haven't looked at the code itself, but loo

[jira] [Commented] (YARN-1297) FairScheduler: Move some logs to debug and check if debug logging is enabled

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258077#comment-15258077 ] Karthik Kambatla commented on YARN-1297: Thanks for the contribution, Yufei, Sandy

[jira] [Commented] (YARN-4795) ContainerMetrics drops records

[ https://issues.apache.org/jira/browse/YARN-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258060#comment-15258060 ] Karthik Kambatla commented on YARN-4795: +1, checking this in. > ContainerMetrics

[jira] [Commented] (YARN-4808) SchedulerNode can use a few more cosmetic changes

[ https://issues.apache.org/jira/browse/YARN-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258023#comment-15258023 ] Karthik Kambatla commented on YARN-4808: I briefly looked at YARN-4390, and comment

[jira] [Commented] (YARN-4390) Do surgical preemption based on reserved container in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15258018#comment-15258018 ] Karthik Kambatla commented on YARN-4390: Looked only at the SchedulerNode changes,

[jira] [Updated] (YARN-1297) FairScheduler: Move some logs to debug and check if debug logging is enabled

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1297: --- Summary: FairScheduler: Move some logs to debug and check if debug logging is enabled (was: Mi

[jira] [Commented] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257958#comment-15257958 ] Karthik Kambatla commented on YARN-1297: +1, checking this in. > Miscellaneous Fa

[jira] [Commented] (YARN-4090) Make Collections.sort() more efficient in FSParentQueue.java

[ https://issues.apache.org/jira/browse/YARN-4090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15257957#comment-15257957 ] Karthik Kambatla commented on YARN-4090: Sorry for the confusion here. We had some

[jira] [Assigned] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1011: -- Assignee: Karthik Kambatla > [Umbrella] Schedule containers based on utilization of curr

[jira] [Commented] (YARN-1011) [Umbrella] Schedule containers based on utilization of currently allocated containers

[ https://issues.apache.org/jira/browse/YARN-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255967#comment-15255967 ] Karthik Kambatla commented on YARN-1011: The prototype I have been working on is he

[jira] [Commented] (YARN-4308) ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats

[ https://issues.apache.org/jira/browse/YARN-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255906#comment-15255906 ] Karthik Kambatla commented on YARN-4308: I had recently reviewed ResourceCalculator

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

[ https://issues.apache.org/jira/browse/YARN-4599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4599: --- Attachment: yarn-4599-not-so-useful.patch > Set OOM control for memory cgroups > --

[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&focusedCommentId=15254348#comment-15254348 ] Karthik Kambatla commented on YARN-4599: FWIW, just posted the not useful version o

[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&focusedCommentId=15254335#comment-15254335 ] Karthik Kambatla commented on YARN-4599: Looked more into this, specifically on how

[jira] [Updated] (YARN-4971) RM fails to re-bind to wildcard IP after failover in multi homed clusters

[ https://issues.apache.org/jira/browse/YARN-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4971: --- Affects Version/s: (was: 3.0.0) 2.7.2 > RM fails to re-bind to wildc

[jira] [Updated] (YARN-4971) RM fails to re-bind to wildcard IP after failover in multi homed clusters

[ https://issues.apache.org/jira/browse/YARN-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4971: --- Target Version/s: 2.9.0 > RM fails to re-bind to wildcard IP after failover in multi homed clus

[jira] [Commented] (YARN-1297) Miscellaneous Fair Scheduler speedups

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252984#comment-15252984 ] Karthik Kambatla commented on YARN-1297: Looks like the test failures are because o

[jira] [Commented] (YARN-4981) limit the max containers to assign to one application per heartbeart

[ https://issues.apache.org/jira/browse/YARN-4981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252787#comment-15252787 ] Karthik Kambatla commented on YARN-4981: Does limiting to one application per heart

[jira] [Updated] (YARN-4784) Fairscheduler: defaultQueueSchedulingPolicy should not accept FIFO

[ https://issues.apache.org/jira/browse/YARN-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4784: --- Summary: Fairscheduler: defaultQueueSchedulingPolicy should not accept FIFO (was: fair schedul

[jira] [Updated] (YARN-4784) fair scheduler: defaultQueueSchedulingPolicy should not accept fifo as a value

[ https://issues.apache.org/jira/browse/YARN-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4784: --- Hadoop Flags: Incompatible change Release Note: Clusters cannot use FIFO policy as the defa

[jira] [Commented] (YARN-4784) fair scheduler: defaultQueueSchedulingPolicy should not accept fifo as a value

[ https://issues.apache.org/jira/browse/YARN-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251403#comment-15251403 ] Karthik Kambatla commented on YARN-4784: The patch looks reasonable to me. However,

[jira] [Commented] (YARN-4935) TestYarnClient#testSubmitIncorrectQueue fails with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251378#comment-15251378 ] Karthik Kambatla commented on YARN-4935: +1, checking this in. > TestYarnClient#t

[jira] [Commented] (YARN-3126) FairScheduler: queue's usedResource is always more than the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15251323#comment-15251323 ] Karthik Kambatla commented on YARN-3126: Commenting without looking into the relate

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4087: --- Hadoop Flags: Incompatible change Marking this incompatible to ensure this gets called out in t

[jira] [Updated] (YARN-1458) FairScheduler: Zero weight can lead to livelock

[ https://issues.apache.org/jira/browse/YARN-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1458: --- Fix Version/s: 2.6.0 > FairScheduler: Zero weight can lead to livelock > --

[jira] [Updated] (YARN-1458) FairScheduler: Zero weight can lead to livelock

[ https://issues.apache.org/jira/browse/YARN-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1458: --- Labels: (was: patch) > FairScheduler: Zero weight can lead to livelock >

[jira] [Commented] (YARN-4807) MockAM#waitForState sleep duration is too long

[ https://issues.apache.org/jira/browse/YARN-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250287#comment-15250287 ] Karthik Kambatla commented on YARN-4807: Thanks [~yufeigu] for working on this and

[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=15250145#comment-15250145 ] Karthik Kambatla commented on YARN-2883: Latest patch looks good to me. +1 The tes

[jira] [Commented] (YARN-4725) [Umbrella] Auto-­restart of containers

[ https://issues.apache.org/jira/browse/YARN-4725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244983#comment-15244983 ] Karthik Kambatla commented on YARN-4725: Haven't looked at the patch posted on YARN

[jira] [Comment Edited] (YARN-4692) [Umbrella] Simplified and first-class support for services in YARN

[ https://issues.apache.org/jira/browse/YARN-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244843#comment-15244843 ] Karthik Kambatla edited comment on YARN-4692 at 4/17/16 8:39 PM:

[jira] [Commented] (YARN-4692) [Umbrella] Simplified and first-class support for services in YARN

[ https://issues.apache.org/jira/browse/YARN-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244843#comment-15244843 ] Karthik Kambatla commented on YARN-4692: (Discussed this offline with [~vinodkv]. P

[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=15243066#comment-15243066 ] Karthik Kambatla commented on YARN-2883: The latest patch (YARN-2883.013.patch) loo

[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=15239499#comment-15239499 ] Karthik Kambatla commented on YARN-2883: Discussed this offline with [~asuresh], [~

[jira] [Commented] (YARN-4931) Preempted resources go back to the same application

[ https://issues.apache.org/jira/browse/YARN-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239235#comment-15239235 ] Karthik Kambatla commented on YARN-4931: Thanks for reporting this. The issue here

[jira] [Created] (YARN-4944) Handle lack of ResourceCalculatorPlugin gracefully

Karthik Kambatla created YARN-4944: -- Summary: Handle lack of ResourceCalculatorPlugin gracefully Key: YARN-4944 URL: https://issues.apache.org/jira/browse/YARN-4944 Project: Hadoop YARN Issu

[jira] [Comment Edited] (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=15234184#comment-15234184 ] Karthik Kambatla edited comment on YARN-2883 at 4/11/16 7:22 PM:

[jira] [Comment Edited] (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=15234184#comment-15234184 ] Karthik Kambatla edited comment on YARN-2883 at 4/11/16 7:23 PM:

[jira] [Commented] (YARN-4935) TestYarnClient#testSubmitIncorrectQueue fails with FairScheduler

[ https://issues.apache.org/jira/browse/YARN-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234365#comment-15234365 ] Karthik Kambatla commented on YARN-4935: If the test is capacity scheduler specific

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