[jira] [Updated] (YARN-4066) Large number of queues choke fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4066: --- Assignee: Johan Gustavsson > Large number of queues choke fair scheduler >

[jira] [Updated] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4180: --- Affects Version/s: 2.7.1 Target Version/s: 2.7.2 Priority: Critical (was: Maj

[jira] [Updated] (YARN-3920) FairScheduler: Limit node reservations to large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3920: --- Summary: FairScheduler: Limit node reservations to large containers (was: FairScheduler contai

[jira] [Updated] (YARN-4156) TestAMRestart#testAMBlacklistPreventsRestartOnSameNode assumes CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-4156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4156: --- Summary: TestAMRestart#testAMBlacklistPreventsRestartOnSameNode assumes CapacityScheduler (was

[jira] [Updated] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4180: --- Attachment: YARN-4180.002.patch Re-uploading the same patch to see if Jenkins kicks in. By th

[jira] [Commented] (YARN-4204) ConcurrentModificationException in FairSchedulerQueueInfo

[ https://issues.apache.org/jira/browse/YARN-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907547#comment-14907547 ] Karthik Kambatla commented on YARN-4204: +1 > ConcurrentModificationException in F

[jira] [Resolved] (YARN-2062) Too many InvalidStateTransitionExceptions from NodeState.NEW on RM failover

[ https://issues.apache.org/jira/browse/YARN-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-2062. Resolution: Invalid > Too many InvalidStateTransitionExceptions from NodeState.NEW on RM fail

[jira] [Commented] (YARN-4066) Large number of queues choke fair scheduler

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

[jira] [Updated] (YARN-4247) Deadlock in FSAppAttempt and RMAppAttemptImpl causes RM to stop processing events

[ https://issues.apache.org/jira/browse/YARN-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4247: --- Priority: Blocker (was: Major) > Deadlock in FSAppAttempt and RMAppAttemptImpl causes RM to st

[jira] [Commented] (YARN-4243) Add retry on establishing Zookeeper conenction in EmbeddedElectorService#serviceInit

[ https://issues.apache.org/jira/browse/YARN-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950960#comment-14950960 ] Karthik Kambatla commented on YARN-4243: I would like to review the patch before co

[jira] [Assigned] (YARN-2353) FairScheduler: Update demand asynchronously instead of in the Update Thread

[ https://issues.apache.org/jira/browse/YARN-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-2353: -- Assignee: Neelesh Srinivas Salian (was: Karthik Kambatla) [~neelesh77] - thanks for off

[jira] [Commented] (YARN-1550) NPE in FairSchedulerAppsBlock#render

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952141#comment-14952141 ] Karthik Kambatla commented on YARN-1550: Just verified the fix was committed to tru

[jira] [Commented] (YARN-4243) Add retry on establishing Zookeeper conenction in EmbeddedElectorService#serviceInit

[ https://issues.apache.org/jira/browse/YARN-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958972#comment-14958972 ] Karthik Kambatla commented on YARN-4243: Looking. > Add retry on establishing Zoo

[jira] [Commented] (YARN-4243) Add retry on establishing Zookeeper conenction in EmbeddedElectorService#serviceInit

[ https://issues.apache.org/jira/browse/YARN-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958994#comment-14958994 ] Karthik Kambatla commented on YARN-4243: Looks like we are addressing two issues he

[jira] [Commented] (YARN-4243) Add retry on establishing Zookeeper conenction in EmbeddedElectorService#serviceInit

[ https://issues.apache.org/jira/browse/YARN-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14958998#comment-14958998 ] Karthik Kambatla commented on YARN-4243: Oh, and Rohith's comment about this patch

[jira] [Commented] (YARN-4270) Limit application resource reservation on nodes for non-node/rack specific requests

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

[jira] [Commented] (YARN-4270) Limit application resource reservation on nodes for non-node/rack specific requests

[ https://issues.apache.org/jira/browse/YARN-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963474#comment-14963474 ] Karthik Kambatla commented on YARN-4270: Added comment too soon. Couple of comments

[jira] [Commented] (YARN-4270) Limit application resource reservation on nodes for non-node/rack specific requests

[ https://issues.apache.org/jira/browse/YARN-4270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964290#comment-14964290 ] Karthik Kambatla commented on YARN-4270: +1 > Limit application resource reservati

[jira] [Commented] (YARN-4243) Add retry on establishing Zookeeper conenction in EmbeddedElectorService#serviceInit

[ https://issues.apache.org/jira/browse/YARN-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968343#comment-14968343 ] Karthik Kambatla commented on YARN-4243: Thanks for the update, Xuan. Sorry for the

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues with 'Fair' policy should compute shares of all resources for its children during a recompute

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14971152#comment-14971152 ] Karthik Kambatla commented on YARN-4212: Patch looks fairly straight-forward. Comme

[jira] [Updated] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

[ https://issues.apache.org/jira/browse/YARN-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4310: --- Summary: FairScheduler: Log skipping reservation messages at DEBUG level (was: Reduce log leve

[jira] [Commented] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

[ https://issues.apache.org/jira/browse/YARN-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979195#comment-14979195 ] Karthik Kambatla commented on YARN-4310: Can we add a guard to check debug logging

[jira] [Commented] (YARN-4310) FairScheduler: Log skipping reservation messages at DEBUG level

[ https://issues.apache.org/jira/browse/YARN-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979334#comment-14979334 ] Karthik Kambatla commented on YARN-4310: +1, pending Jenkins. > FairScheduler: Lo

[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=14979382#comment-14979382 ] Karthik Kambatla commented on YARN-4308: Don't recall all the details, but that was

[jira] [Commented] (YARN-4309) Add debug information to application logs when a container fails

[ https://issues.apache.org/jira/browse/YARN-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979396#comment-14979396 ] Karthik Kambatla commented on YARN-4309: Generally, in favor of collecting debug in

[jira] [Commented] (YARN-4314) Adding container wait time as a metric at queue level and application level.

[ https://issues.apache.org/jira/browse/YARN-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981613#comment-14981613 ] Karthik Kambatla commented on YARN-4314: I was thinking of filing a JIRA for the sa

[jira] [Updated] (YARN-3112) AM restart and keep containers from previous attempts, then new container launch failed

[ https://issues.apache.org/jira/browse/YARN-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3112: --- Description: This error is very similar to YARN-1795, YARN-1839, but i have check the solution

[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14989664#comment-14989664 ] Karthik Kambatla commented on YARN-3980: Thanks Inigo. Looks generally good. Commen

[jira] [Commented] (YARN-4314) Adding container wait time as a metric at queue level and application level.

[ https://issues.apache.org/jira/browse/YARN-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990346#comment-14990346 ] Karthik Kambatla commented on YARN-4314: bq. I feel adding timestamp to each resour

[jira] [Commented] (YARN-4032) Corrupted state from a previous version can still cause RM to fail with NPE due to same reasons as YARN-2834

[ https://issues.apache.org/jira/browse/YARN-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990399#comment-14990399 ] Karthik Kambatla commented on YARN-4032: [~jianhe]'s suggestion makes sense to me.

[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004686#comment-15004686 ] Karthik Kambatla commented on YARN-3980: I believe we are waiting for the test to b

[jira] [Resolved] (YARN-3501) problem in running yarn scheduler load simulator

[ https://issues.apache.org/jira/browse/YARN-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-3501. Resolution: Incomplete Closing this JIRA for lack of information. > problem in running yarn

[jira] [Commented] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009876#comment-15009876 ] Karthik Kambatla commented on YARN-4367: /cc [~ywskycn] > SLS webapp doesn't load

[jira] [Created] (YARN-4367) SLS webapp doesn't load

Karthik Kambatla created YARN-4367: -- Summary: SLS webapp doesn't load Key: YARN-4367 URL: https://issues.apache.org/jira/browse/YARN-4367 Project: Hadoop YARN Issue Type: Bug Compo

[jira] [Updated] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4367: --- Attachment: YARN-4367-branch-2.1.patch Looks like the issue is because the html template files

[jira] [Commented] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009967#comment-15009967 ] Karthik Kambatla commented on YARN-4367: This isn't an issue on trunk. Trunk has th

[jira] [Updated] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4367: --- Attachment: YARN-4367-branch-2.2.patch It might make more sense to have all the changes in slsr

[jira] [Updated] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4367: --- Attachment: YARN-4367-branch-2.patch Uploading same patch with a different name. > SLS webapp

[jira] [Commented] (YARN-4367) SLS webapp doesn't load

[ https://issues.apache.org/jira/browse/YARN-4367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010290#comment-15010290 ] Karthik Kambatla commented on YARN-4367: Classpath fix that is hard to write a test

[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020766#comment-15020766 ] Karthik Kambatla commented on YARN-3980: Reviewing the latest patch here. > Plumb

[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020785#comment-15020785 ] Karthik Kambatla commented on YARN-3980: Neat test using the MiniYarnCluster. Com

[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021189#comment-15021189 ] Karthik Kambatla commented on YARN-3980: Jenkins could be running on a (virtual) ma

[jira] [Comment Edited] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021189#comment-15021189 ] Karthik Kambatla edited comment on YARN-3980 at 11/22/15 9:11 PM: ---

[jira] [Commented] (YARN-3980) Plumb resource-utilization info in node heartbeat through to the scheduler

[ https://issues.apache.org/jira/browse/YARN-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022715#comment-15022715 ] Karthik Kambatla commented on YARN-3980: +1. Will commit this later today. > Plum

[jira] [Resolved] (YARN-4407) Support Resource oversubscription in YARN scheduler

[ https://issues.apache.org/jira/browse/YARN-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-4407. Resolution: Duplicate > Support Resource oversubscription in YARN scheduler > ---

[jira] [Commented] (YARN-2975) FSLeafQueue app lists are accessed without required locks

[ https://issues.apache.org/jira/browse/YARN-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048436#comment-15048436 ] Karthik Kambatla commented on YARN-2975: Makes sense. [~sjlee0] - want to do the ho

[jira] [Commented] (YARN-4438) Implement RM leader election with curator

[ https://issues.apache.org/jira/browse/YARN-4438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050391#comment-15050391 ] Karthik Kambatla commented on YARN-4438: Would very much like for us to use Curator

[jira] [Commented] (YARN-1011) [Umbrella] RM should dynamically 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=15055206#comment-15055206 ] Karthik Kambatla commented on YARN-1011: I have been thinking of this for a while n

[jira] [Updated] (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 updated YARN-1011: --- Summary: [Umbrella] Schedule containers based on utilization of currently allocated containers

[jira] [Commented] (YARN-2618) Avoid over-allocation of disk resources

[ https://issues.apache.org/jira/browse/YARN-2618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527792#comment-14527792 ] Karthik Kambatla commented on YARN-2618: [~vinodkv] - we were thinking of working o

[jira] [Commented] (YARN-1050) Document the Fair Scheduler REST API

[ https://issues.apache.org/jira/browse/YARN-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530912#comment-14530912 ] Karthik Kambatla commented on YARN-1050: Sorry for not looking at this sooner. Our

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

[ https://issues.apache.org/jira/browse/YARN-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14530960#comment-14530960 ] Karthik Kambatla commented on YARN-2619: I really would have liked to review or at

[jira] [Commented] (YARN-3423) RM HA setup, "Cluster" tab links populated with AM hostname instead of RM

[ https://issues.apache.org/jira/browse/YARN-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531147#comment-14531147 ] Karthik Kambatla commented on YARN-3423: [~adhoot] - you were looking at this recen

[jira] [Commented] (YARN-2194) Add Cgroup support for RedHat 7

[ https://issues.apache.org/jira/browse/YARN-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1450#comment-1450 ] Karthik Kambatla commented on YARN-2194: RHEL7 recommends using systemd, but doesn'

[jira] [Updated] (YARN-3489) RMServerUtils.validateResourceRequests should only obtain queue info once

[ https://issues.apache.org/jira/browse/YARN-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3489: --- Labels: (was: BB2015-05-RFC) > RMServerUtils.validateResourceRequests should only obtain queu

[jira] [Commented] (YARN-3489) RMServerUtils.validateResourceRequests should only obtain queue info once

[ https://issues.apache.org/jira/browse/YARN-3489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535014#comment-14535014 ] Karthik Kambatla commented on YARN-3489: The patch doesn't apply anymore. > RMSer

[jira] [Updated] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1612: --- Labels: (was: BB2015-05-TBR) > FairScheduler: Enable delay scheduling by default > --

[jira] [Commented] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535027#comment-14535027 ] Karthik Kambatla commented on YARN-1612: In the latest patch, I only see changes th

[jira] [Updated] (YARN-3259) FairScheduler: Update to fairShare could be triggered early on node events instead of waiting for update interval

[ https://issues.apache.org/jira/browse/YARN-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3259: --- Labels: (was: BB2015-05-TBR) > FairScheduler: Update to fairShare could be triggered early on

[jira] [Commented] (YARN-3259) FairScheduler: Update to fairShare could be triggered early on node events instead of waiting for update interval

[ https://issues.apache.org/jira/browse/YARN-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535067#comment-14535067 ] Karthik Kambatla commented on YARN-3259: The patch doesn't compile because we are a

[jira] [Updated] (YARN-1501) Fair Scheduler will NPE if it hits IOException on queue assignment

[ https://issues.apache.org/jira/browse/YARN-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1501: --- Labels: newbie (was: BB2015-05-TBR newbie) > Fair Scheduler will NPE if it hits IOException on

[jira] [Updated] (YARN-2098) App priority support in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2098: --- Labels: (was: BB2015-05-TBR) > App priority support in Fair Scheduler > -

[jira] [Commented] (YARN-2684) FairScheduler should fast-fail if queue is removed during app recovery

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535194#comment-14535194 ] Karthik Kambatla commented on YARN-2684: Sorry for the delay in following up here.

[jira] [Updated] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2684: --- Summary: FairScheduler: When failing an application due to changes in queue config or placement

[jira] [Updated] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2684: --- Labels: (was: BB2015-05-TBR) > FairScheduler: When failing an application due to changes in q

[jira] [Commented] (YARN-1050) Document the Fair Scheduler REST API

[ https://issues.apache.org/jira/browse/YARN-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535241#comment-14535241 ] Karthik Kambatla commented on YARN-1050: Of course. Thanks for the help, [~rvs]. I

[jira] [Commented] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535291#comment-14535291 ] Karthik Kambatla commented on YARN-1612: [~airbots] - sorry, my bad. Missed this lo

[jira] [Updated] (YARN-1612) FairScheduler: Enable delay scheduling by default

[ https://issues.apache.org/jira/browse/YARN-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1612: --- Hadoop Flags: Incompatible change > FairScheduler: Enable delay scheduling by default > ---

[jira] [Commented] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535306#comment-14535306 ] Karthik Kambatla commented on YARN-2684: It would definitely be nice to have the sa

[jira] [Created] (YARN-3607) Allow users to choose between failing the daemons vs failing the apps/containers

Karthik Kambatla created YARN-3607: -- Summary: Allow users to choose between failing the daemons vs failing the apps/containers Key: YARN-3607 URL: https://issues.apache.org/jira/browse/YARN-3607 Proj

[jira] [Commented] (YARN-3607) Allow users to choose between failing the daemons vs failing the apps/containers

[ https://issues.apache.org/jira/browse/YARN-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535463#comment-14535463 ] Karthik Kambatla commented on YARN-3607: If people think it is reasonable to add a

[jira] [Commented] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535483#comment-14535483 ] Karthik Kambatla commented on YARN-2684: [~rohithsharma] - agree. As I said earlier

[jira] [Updated] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2684: --- Component/s: (was: resourcemanager) > FairScheduler: When failing an application due to cha

[jira] [Updated] (YARN-2684) FairScheduler: When failing an application due to changes in queue config or placement policy, indicate the cause.

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2684: --- Labels: (was: BB2015-05-RFC) > FairScheduler: When failing an application due to changes in q

[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=14535506#comment-14535506 ] Karthik Kambatla commented on YARN-1297: +1, pending Jenkins. > Miscellaneous Fai

[jira] [Updated] (YARN-2768) optimize FSAppAttempt.updateDemand by avoid clone of Resource which takes 85% of computing time of update thread

[ https://issues.apache.org/jira/browse/YARN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2768: --- Labels: (was: BB2015-05-RFC) > optimize FSAppAttempt.updateDemand by avoid clone of Resource

[jira] [Commented] (YARN-2768) optimize FSAppAttempt.updateDemand by avoid clone of Resource which takes 85% of computing time of update thread

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

[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=14535842#comment-14535842 ] Karthik Kambatla commented on YARN-1297: The test failures may be because of how th

[jira] [Created] (YARN-3610) FairScheduler: Add steady-fair-shares to the REST API documentation

Karthik Kambatla created YARN-3610: -- Summary: FairScheduler: Add steady-fair-shares to the REST API documentation Key: YARN-3610 URL: https://issues.apache.org/jira/browse/YARN-3610 Project: Hadoop Y

[jira] [Commented] (YARN-1050) Document the Fair Scheduler REST API

[ https://issues.apache.org/jira/browse/YARN-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535853#comment-14535853 ] Karthik Kambatla commented on YARN-1050: Thanks Roman for updating the patch, and R

[jira] [Commented] (YARN-3608) Apps submitted to MiniYarnCluster always stay in ACCEPTED state.

[ https://issues.apache.org/jira/browse/YARN-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535875#comment-14535875 ] Karthik Kambatla commented on YARN-3608: Not sure if it was a MiniYarnCluster bug,

[jira] [Commented] (YARN-3608) Apps submitted to MiniYarnCluster always stay in ACCEPTED state.

[ https://issues.apache.org/jira/browse/YARN-3608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535877#comment-14535877 ] Karthik Kambatla commented on YARN-3608: May be, something to do with the dispatche

[jira] [Updated] (YARN-3271) FairScheduler: Move tests related to max-runnable-apps from TestFairScheduler to TestAppRunnability

[ https://issues.apache.org/jira/browse/YARN-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3271: --- Labels: (was: BB2015-05-RFC) > FairScheduler: Move tests related to max-runnable-apps from Te

[jira] [Commented] (YARN-1050) Document the Fair Scheduler REST API

[ https://issues.apache.org/jira/browse/YARN-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535886#comment-14535886 ] Karthik Kambatla commented on YARN-1050: +1. Committed this to trunk and branch-2.

[jira] [Updated] (YARN-1050) Document the Fair Scheduler REST API

[ https://issues.apache.org/jira/browse/YARN-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1050: --- Labels: (was: BB2015-05-TBR) > Document the Fair Scheduler REST API > ---

[jira] [Commented] (YARN-3271) FairScheduler: Move tests related to max-runnable-apps from TestFairScheduler to TestAppRunnability

[ https://issues.apache.org/jira/browse/YARN-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535907#comment-14535907 ] Karthik Kambatla commented on YARN-3271: +1 > FairScheduler: Move tests related to

[jira] [Commented] (YARN-1287) Consolidate MockClocks

[ https://issues.apache.org/jira/browse/YARN-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535937#comment-14535937 ] Karthik Kambatla commented on YARN-1287: +1, pending Jenkins. > Consolidate MockCl

[jira] [Commented] (YARN-1287) Consolidate MockClocks

[ https://issues.apache.org/jira/browse/YARN-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536903#comment-14536903 ] Karthik Kambatla commented on YARN-1287: The test failure looks unrelated. +1, ch

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

[ https://issues.apache.org/jira/browse/YARN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1297: --- Assignee: Arun Suresh (was: Sandy Ryza) > Miscellaneous Fair Scheduler speedups >

[jira] [Updated] (YARN-3395) FairScheduler: Trim whitespaces when using username for queuename

[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3395: --- Summary: FairScheduler: Trim whitespaces when using username for queuename (was: [Fair Schedul

[jira] [Commented] (YARN-3395) FairScheduler: Trim whitespaces when using username for queuename

[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536934#comment-14536934 ] Karthik Kambatla commented on YARN-3395: +1. Checking this in . > FairScheduler:

[jira] [Commented] (YARN-3395) FairScheduler: Trim whitespaces when using username for queuename

[ https://issues.apache.org/jira/browse/YARN-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536941#comment-14536941 ] Karthik Kambatla commented on YARN-3395: Thanks Zhihai for reporting and fixing thi

[jira] [Updated] (YARN-2306) leak of reservation metrics (fair scheduler)

[ https://issues.apache.org/jira/browse/YARN-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2306: --- Labels: (was: BB2015-05-TBR) > leak of reservation metrics (fair scheduler) > ---

[jira] [Updated] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3547: --- Labels: (was: BB2015-05-TBR) > FairScheduler: Apps that have no resource demand should not pa

[jira] [Commented] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536964#comment-14536964 ] Karthik Kambatla commented on YARN-3547: In FSAppAttempt, pending resources can be

[jira] [Commented] (YARN-3259) FairScheduler: Update to fairShare could be triggered early on node events instead of waiting for update interval

[ https://issues.apache.org/jira/browse/YARN-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14536973#comment-14536973 ] Karthik Kambatla commented on YARN-3259: Thanks for updating the patch, Anubhav. F

[jira] [Created] (YARN-3613) TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods

Karthik Kambatla created YARN-3613: -- Summary: TestContainerManagerSecurity should init and start Yarn cluster in setup instead of individual methods Key: YARN-3613 URL: https://issues.apache.org/jira/browse/YARN-

[jira] [Assigned] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-3619: -- Assignee: Karthik Kambatla > ContainerMetrics unregisters during getMetrics and leads to

[jira] [Created] (YARN-3621) FairScheduler doesn't count AM vcores towards max-share

Karthik Kambatla created YARN-3621: -- Summary: FairScheduler doesn't count AM vcores towards max-share Key: YARN-3621 URL: https://issues.apache.org/jira/browse/YARN-3621 Project: Hadoop YARN

[jira] [Assigned] (YARN-3619) ContainerMetrics unregisters during getMetrics and leads to ConcurrentModificationException

[ https://issues.apache.org/jira/browse/YARN-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-3619: -- Assignee: zhihai xu (was: Karthik Kambatla) Zhihai pinged me offline mentioning he know

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