[jira] [Commented] (YARN-2001) Persist NMs info for RM restart

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990091#comment-13990091 ] Karthik Kambatla commented on YARN-2001: I am not quite sure if this is a good

[jira] [Commented] (YARN-2017) Merge common code in schedulers

[ https://issues.apache.org/jira/browse/YARN-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990100#comment-13990100 ] Karthik Kambatla commented on YARN-2017: Instead of removing these too, can we make

[jira] [Commented] (YARN-2017) Merge common code in schedulers

[ https://issues.apache.org/jira/browse/YARN-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990104#comment-13990104 ] Karthik Kambatla commented on YARN-2017: s/too/two/ Merge common code in

[jira] [Commented] (YARN-2001) Persist NMs info for RM restart

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990241#comment-13990241 ] Karthik Kambatla commented on YARN-2001: bq. we may run into condition like the

[jira] [Commented] (YARN-1987) Wrapper for leveldb DBIterator to aid in handling database exceptions

[ https://issues.apache.org/jira/browse/YARN-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990879#comment-13990879 ] Karthik Kambatla commented on YARN-1987: +1. Committing this shortly. Wrapper for

[jira] [Commented] (YARN-1987) Wrapper for leveldb DBIterator to aid in handling database exceptions

[ https://issues.apache.org/jira/browse/YARN-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990921#comment-13990921 ] Karthik Kambatla commented on YARN-1987: (having trouble with my account - not

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13991133#comment-13991133 ] Karthik Kambatla commented on YARN-2010: [~rohithsharma] - I don't see an updated

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13991141#comment-13991141 ] Karthik Kambatla commented on YARN-2001: I haven't looked closely enough, but

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13991133#comment-13991133 ] Karthik Kambatla commented on YARN-2010: [~rohithsharma] - I don't see an updated

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13991138#comment-13991138 ] Karthik Kambatla commented on YARN-2001: bq. In a simple case that an application

[jira] [Commented] (YARN-1987) Wrapper for leveldb DBIterator to aid in handling database exceptions

[ https://issues.apache.org/jira/browse/YARN-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994443#comment-13994443 ] Karthik Kambatla commented on YARN-1987: Just got my access back. The email outage

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994837#comment-13994837 ] Karthik Kambatla commented on YARN-1474: # Correct me if I am wrong, but changes to

[jira] [Updated] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2010: --- Attachment: yarn-2010-2.patch New patch with following changes - # Noticed that

[jira] [Commented] (YARN-556) RM Restart phase 2 - Work preserving restart

[ https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995165#comment-13995165 ] Karthik Kambatla commented on YARN-556: --- Oh. Forgot to mention that. [~adhoot] offered

[jira] [Created] (YARN-2036) Document yarn.resourcemanager.hostname in ClusterSetup

Karthik Kambatla created YARN-2036: -- Summary: Document yarn.resourcemanager.hostname in ClusterSetup Key: YARN-2036 URL: https://issues.apache.org/jira/browse/YARN-2036 Project: Hadoop YARN

[jira] [Resolved] (YARN-2039) Better reporting of finished containers to AMs

[ https://issues.apache.org/jira/browse/YARN-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla resolved YARN-2039. Resolution: Duplicate Thanks for pointing that out, Bikas. Resolving as duplicate. Better

[jira] [Commented] (YARN-2033) Investigate merging generic-history into the Timeline Store

[ https://issues.apache.org/jira/browse/YARN-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995438#comment-13995438 ] Karthik Kambatla commented on YARN-2033: Thanks Vinod. Would like to hear your

[jira] [Assigned] (YARN-1913) With Fair Scheduler, cluster can logjam when all resources are consumed by AMs

[ https://issues.apache.org/jira/browse/YARN-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1913: -- Assignee: Karthik Kambatla With Fair Scheduler, cluster can logjam when all resources

[jira] [Commented] (YARN-1969) Fair Scheduler: Add policy for Earliest Deadline First

[ https://issues.apache.org/jira/browse/YARN-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995153#comment-13995153 ] Karthik Kambatla commented on YARN-1969: Just stating the obvious: we need to add a

[jira] [Commented] (YARN-2001) Threshold for RM to accept requests from AM after failover

[ https://issues.apache.org/jira/browse/YARN-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995243#comment-13995243 ] Karthik Kambatla commented on YARN-2001: I think the epoch idea might work very

[jira] [Commented] (YARN-1372) Ensure all completed containers are reported to the AMs across RM restart

[ https://issues.apache.org/jira/browse/YARN-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995247#comment-13995247 ] Karthik Kambatla commented on YARN-1372: Based on offline discussion with Anubhav,

[jira] [Commented] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995743#comment-13995743 ] Karthik Kambatla commented on YARN-1861: bq. Also, we need to make sure that when

[jira] [Commented] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995781#comment-13995781 ] Karthik Kambatla commented on YARN-1861: bq. That is what I was thinking, but I am

[jira] [Commented] (YARN-1969) Fair Scheduler: Add policy for Earliest Deadline First

[ https://issues.apache.org/jira/browse/YARN-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996101#comment-13996101 ] Karthik Kambatla commented on YARN-1969: I am a little confused. Is the original

[jira] [Commented] (YARN-556) RM Restart phase 2 - Work preserving restart

[ https://issues.apache.org/jira/browse/YARN-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993895#comment-13993895 ] Karthik Kambatla commented on YARN-556: --- For the scheduler-related work itself, the

[jira] [Updated] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Attachment: yarn-2054-1.patch Straight-forward patch that brings the cumulative to 10

[jira] [Commented] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997159#comment-13997159 ] Karthik Kambatla commented on YARN-2054: On a cluster with RM HA and buggy RM, this

[jira] [Updated] (YARN-1550) the page http:/ip:50030/cluster/scheduler has 500 error in fairScheduler

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1550: --- Description: three Steps : 1、debug at RMAppManager#submitApplication after code if

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

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1550: --- Summary: NPE in FairSchedulerAppsBlock#render (was: the page

[jira] [Created] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

Karthik Kambatla created YARN-2054: -- Summary: Poor defaults for YARN ZK configs for retries and retry-inteval Key: YARN-2054 URL: https://issues.apache.org/jira/browse/YARN-2054 Project: Hadoop YARN

[jira] [Commented] (YARN-2016) Yarn getApplicationRequest start time range is not honored

[ https://issues.apache.org/jira/browse/YARN-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996780#comment-13996780 ] Karthik Kambatla commented on YARN-2016: Sorry for missing those merge-backs. A

[jira] [Commented] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13994014#comment-13994014 ] Karthik Kambatla commented on YARN-1861: I am obviously a +1 because I wrote the

[jira] [Created] (YARN-2061) Revisit logging levels in ZKRMStateStore

Karthik Kambatla created YARN-2061: -- Summary: Revisit logging levels in ZKRMStateStore Key: YARN-2061 URL: https://issues.apache.org/jira/browse/YARN-2061 Project: Hadoop YARN Issue Type:

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

Karthik Kambatla created YARN-2062: -- Summary: Too many InvalidStateTransitionExceptions from NodeState.NEW on RM failover Key: YARN-2062 URL: https://issues.apache.org/jira/browse/YARN-2062 Project:

[jira] [Commented] (YARN-2061) Revisit logging levels in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998251#comment-13998251 ] Karthik Kambatla commented on YARN-2061: # After loading state corresponding to one

[jira] [Commented] (YARN-2040) Recover information about finished containers

[ https://issues.apache.org/jira/browse/YARN-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993959#comment-13993959 ] Karthik Kambatla commented on YARN-2040: [~jlowe] - please close this as duplicate

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

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13997742#comment-13997742 ] Karthik Kambatla commented on YARN-1550: The patch doesn't apply anymore.

[jira] [Commented] (YARN-1489) [Umbrella] Work-preserving ApplicationMaster restart

[ https://issues.apache.org/jira/browse/YARN-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993962#comment-13993962 ] Karthik Kambatla commented on YARN-1489: Created a couple of sub-tasks based on an

[jira] [Commented] (YARN-2036) Document yarn.resourcemanager.hostname in ClusterSetup

[ https://issues.apache.org/jira/browse/YARN-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993888#comment-13993888 ] Karthik Kambatla commented on YARN-2036: Looks good to me. +1, pending Jenkins.

[jira] [Created] (YARN-2058) .gitignore should ignore .orig and .rej files

Karthik Kambatla created YARN-2058: -- Summary: .gitignore should ignore .orig and .rej files Key: YARN-2058 URL: https://issues.apache.org/jira/browse/YARN-2058 Project: Hadoop YARN Issue

[jira] [Created] (YARN-2037) Add restart support for Unmanaged AMs

Karthik Kambatla created YARN-2037: -- Summary: Add restart support for Unmanaged AMs Key: YARN-2037 URL: https://issues.apache.org/jira/browse/YARN-2037 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2061) Revisit logging levels in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998254#comment-13998254 ] Karthik Kambatla commented on YARN-2061: I guess that is the only major case.

[jira] [Updated] (YARN-2039) Better reporting of finished containers to AMs

[ https://issues.apache.org/jira/browse/YARN-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2039: --- Issue Type: Sub-task (was: Bug) Parent: YARN-128 Better reporting of finished

[jira] [Created] (YARN-2039) Better reporting of finished containers to AMs

Karthik Kambatla created YARN-2039: -- Summary: Better reporting of finished containers to AMs Key: YARN-2039 URL: https://issues.apache.org/jira/browse/YARN-2039 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13993978#comment-13993978 ] Karthik Kambatla commented on YARN-1861: Thanks a bunch for writing the test for

[jira] [Created] (YARN-2040) Recover information about finished containers

Karthik Kambatla created YARN-2040: -- Summary: Recover information about finished containers Key: YARN-2040 URL: https://issues.apache.org/jira/browse/YARN-2040 Project: Hadoop YARN Issue

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=13998269#comment-13998269 ] Karthik Kambatla commented on YARN-2062: I propose having a dummy invalid

[jira] [Commented] (YARN-2061) Revisit logging levels in ZKRMStateStore

[ https://issues.apache.org/jira/browse/YARN-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13998524#comment-13998524 ] Karthik Kambatla commented on YARN-2061: We assume that the Log level is at least

[jira] [Commented] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999771#comment-13999771 ] Karthik Kambatla commented on YARN-2054: bq. If we want these configs to match up

[jira] [Created] (YARN-2068) FairScheduler uses the same ResourceCalculator for all policies

Karthik Kambatla created YARN-2068: -- Summary: FairScheduler uses the same ResourceCalculator for all policies Key: YARN-2068 URL: https://issues.apache.org/jira/browse/YARN-2068 Project: Hadoop YARN

[jira] [Created] (YARN-2067) FairScheduler update/continuous-scheduling threads should start only when after the scheduler is started

Karthik Kambatla created YARN-2067: -- Summary: FairScheduler update/continuous-scheduling threads should start only when after the scheduler is started Key: YARN-2067 URL:

[jira] [Updated] (YARN-1996) Provide alternative policies for UNHEALTHY nodes.

[ https://issues.apache.org/jira/browse/YARN-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1996: --- Description: Currently, UNHEALTHY nodes can significantly prolong execution of large

[jira] [Updated] (YARN-1969) Fair Scheduler: Add policy for Earliest Endtime First

[ https://issues.apache.org/jira/browse/YARN-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1969: --- Summary: Fair Scheduler: Add policy for Earliest Endtime First (was: Fair Scheduler: Add

[jira] [Updated] (YARN-1969) Fair Scheduler: Add policy for Earliest Endtime First

[ https://issues.apache.org/jira/browse/YARN-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1969: --- Description: What we are observing is that some big jobs with many allocated containers are

[jira] [Updated] (YARN-1861) Both RM stuck in standby mode when automatic failover is enabled

[ https://issues.apache.org/jira/browse/YARN-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1861: --- Attachment: yarn-1861-6.patch Updated new patch (yarn-1861-6.patch) to fix the nits. Also,

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000528#comment-14000528 ] Karthik Kambatla commented on YARN-1474: Looks like it did run, but couldn't apply

[jira] [Updated] (YARN-2041) Hard to co-locate MR2 and Spark jobs on the same cluster in YARN

[ https://issues.apache.org/jira/browse/YARN-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2041: --- Fix Version/s: (was: 2.4.0) (was: 2.3.0) Hard to co-locate MR2

[jira] [Commented] (YARN-2041) Hard to co-locate MR2 and Spark jobs on the same cluster in YARN

[ https://issues.apache.org/jira/browse/YARN-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000602#comment-14000602 ] Karthik Kambatla commented on YARN-2041: Also, the Fix Version is to track what

[jira] [Commented] (YARN-2041) Hard to co-locate MR2 and Spark jobs on the same cluster in YARN

[ https://issues.apache.org/jira/browse/YARN-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14000601#comment-14000601 ] Karthik Kambatla commented on YARN-2041: yarn.nodemanager.resource.memory-mb should

[jira] [Created] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

Karthik Kambatla created YARN-2073: -- Summary: FairScheduler starts preempting resources even with free resources on the cluster Key: YARN-2073 URL: https://issues.apache.org/jira/browse/YARN-2073

[jira] [Comment Edited] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002284#comment-14002284 ] Karthik Kambatla edited comment on YARN-1474 at 5/19/14 8:08 PM:

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002432#comment-14002432 ] Karthik Kambatla commented on YARN-1366: With the responseMap, I think the best

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002455#comment-14002455 ] Karthik Kambatla commented on YARN-1366: Sorry, missed the point in your previous

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002615#comment-14002615 ] Karthik Kambatla commented on YARN-1474: Let me take a closer look. Make

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002707#comment-14002707 ] Karthik Kambatla commented on YARN-1474: Thanks [~ozawa] for your patience with the

[jira] [Comment Edited] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14002707#comment-14002707 ] Karthik Kambatla edited comment on YARN-1474 at 5/20/14 2:01 AM:

[jira] [Updated] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

[ https://issues.apache.org/jira/browse/YARN-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2073: --- Attachment: yarn-2073-1.patch Added a unit test - the test fails without the fix. Also, moved

[jira] [Commented] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

[ https://issues.apache.org/jira/browse/YARN-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004181#comment-14004181 ] Karthik Kambatla commented on YARN-2073: bq. we may also need to move the previous

[jira] [Updated] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

[ https://issues.apache.org/jira/browse/YARN-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2073: --- Attachment: yarn-2073-2.patch Thanks Wei. Updated patch to address the nits. FairScheduler

[jira] [Commented] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

[ https://issues.apache.org/jira/browse/YARN-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14004315#comment-14004315 ] Karthik Kambatla commented on YARN-2073: Sandy - you make very good points. In

[jira] [Commented] (YARN-2089) FairScheduler: QueuePlacementPolicy and QueuePlacementRule are missing audience annotations

[ https://issues.apache.org/jira/browse/YARN-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005211#comment-14005211 ] Karthik Kambatla commented on YARN-2089: Looks good to me as well. +1. Checking

[jira] [Commented] (YARN-2089) FairScheduler: QueuePlacementPolicy and QueuePlacementRule are missing audience annotations

[ https://issues.apache.org/jira/browse/YARN-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14005214#comment-14005214 ] Karthik Kambatla commented on YARN-2089: (actually, let us wait for Jenkins even

[jira] [Updated] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Attachment: yarn-2054-2.patch A patch that sets the retry interval based on the session

[jira] [Updated] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

[ https://issues.apache.org/jira/browse/YARN-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2073: --- Attachment: yarn-2073-4.patch Thanks for the review, Sandy. Updated the patch to reflect your

[jira] [Updated] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2096: --- Summary: Race in TestRMRestart#testQueueMetricsOnRMRestart (was: testQueueMetricsOnRMRestart

[jira] [Commented] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007338#comment-14007338 ] Karthik Kambatla commented on YARN-2096: Looks good to me. +1. Race in

[jira] [Comment Edited] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007338#comment-14007338 ] Karthik Kambatla edited comment on YARN-2096 at 5/23/14 4:41 PM:

[jira] [Commented] (YARN-2105) Three TestFairScheduler tests fail in trunk

[ https://issues.apache.org/jira/browse/YARN-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010013#comment-14010013 ] Karthik Kambatla commented on YARN-2105: Looks good to me. I ll wait for Sandy also

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010728#comment-14010728 ] Karthik Kambatla commented on YARN-1474: Thanks Tsuyoshi. We are very close to

[jira] [Updated] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Attachment: yarn-2054-3.patch Patch with unit test. Poor defaults for YARN ZK configs for

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010854#comment-14010854 ] Karthik Kambatla commented on YARN-2010: bq. In non-workpreserving restart, since

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011331#comment-14011331 ] Karthik Kambatla commented on YARN-1474: I think that is the step in the right

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011362#comment-14011362 ] Karthik Kambatla commented on YARN-2010: I see. Thanks for the input. Let me check

[jira] [Updated] (YARN-2054) Poor defaults for YARN ZK configs for retries and retry-inteval

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Attachment: yarn-2054-4.patch Sorry for the bulky patch - forgot to rebase against trunk

[jira] [Updated] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2010: --- Attachment: yarn-2010-3.patch New patch that gets rid of the config and addresses the issue

[jira] [Updated] (YARN-2054) Better defaults for YARN ZK configs for retries and retry-inteval when HA is enabled

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2054: --- Summary: Better defaults for YARN ZK configs for retries and retry-inteval when HA is enabled

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013777#comment-14013777 ] Karthik Kambatla commented on YARN-2010: Let me clarify a couple of things. It is

[jira] [Commented] (YARN-2054) Better defaults for YARN ZK configs for retries and retry-inteval when HA is enabled

[ https://issues.apache.org/jira/browse/YARN-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013788#comment-14013788 ] Karthik Kambatla commented on YARN-2054: Saw this late - thanks for the review,

[jira] [Updated] (YARN-1877) Document yarn.resourcemanager.zk-auth and its scope

[ https://issues.apache.org/jira/browse/YARN-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1877: --- Summary: Document yarn.resourcemanager.zk-auth and its scope (was: ZK store: Add

[jira] [Commented] (YARN-1877) ZK store: Add yarn.resourcemanager.zk-state-store.root-node.auth for root node auth

[ https://issues.apache.org/jira/browse/YARN-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013793#comment-14013793 ] Karthik Kambatla commented on YARN-1877: Thanks for investigating this, Robert.

[jira] [Assigned] (YARN-1877) Document yarn.resourcemanager.zk-auth and its scope

[ https://issues.apache.org/jira/browse/YARN-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1877: -- Assignee: Robert Kanter (was: Karthik Kambatla) Document yarn.resourcemanager.zk-auth

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14014772#comment-14014772 ] Karthik Kambatla commented on YARN-1474: Latest patch looks good to me. +1. Given

[jira] [Updated] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-1474: --- Hadoop Flags: Reviewed Make schedulers services

[jira] [Commented] (YARN-1474) Make schedulers services

[ https://issues.apache.org/jira/browse/YARN-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14014809#comment-14014809 ] Karthik Kambatla commented on YARN-1474: I just committed this to trunk, but had

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

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla reassigned YARN-1550: -- Assignee: Anubhav Dhoot Looks good to me. +1. Committing this shortly. NPE in

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

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015439#comment-14015439 ] Karthik Kambatla commented on YARN-1550: Actually, I run into the following NPE

[jira] [Commented] (YARN-2010) RM can't transition to active if it can't recover an app attempt

[ https://issues.apache.org/jira/browse/YARN-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015653#comment-14015653 ] Karthik Kambatla commented on YARN-2010: Sorry, the commit messages are for the

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

[ https://issues.apache.org/jira/browse/YARN-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015844#comment-14015844 ] Karthik Kambatla commented on YARN-1550: Thanks Anubhav. +1. Committing this

[jira] [Commented] (YARN-1590) _HOST doesn't expand properly for RM, NM, ProxyServer and JHS

[ https://issues.apache.org/jira/browse/YARN-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015862#comment-14015862 ] Karthik Kambatla commented on YARN-1590: Just ran into this. If I am not mistaken,

[jira] [Commented] (YARN-2119) Fix the DEFAULT_PROXY_ADDRESS used for getBindAddress to fix 1590

[ https://issues.apache.org/jira/browse/YARN-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015866#comment-14015866 ] Karthik Kambatla commented on YARN-2119: Looks good to me. +1. I ll commit this

<    5   6   7   8   9   10   11   12   13   14   >