[jira] [Commented] (YARN-4831) Recovered containers will be killed after NM stateful restart

[ https://issues.apache.org/jira/browse/YARN-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197895#comment-15197895 ] Siqi Li commented on YARN-4831: --- When NM does a stateful restart, the ContainerManagerImpl will try to

[jira] [Updated] (YARN-4831) Recovered containers will be killed after NM stateful restart

[ https://issues.apache.org/jira/browse/YARN-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4831: -- Attachment: YARN-4831.v1.patch > Recovered containers will be killed after NM stateful restart >

[jira] [Created] (YARN-4831) Recovered containers will be killed after NM stateful restart

Siqi Li created YARN-4831: - Summary: Recovered containers will be killed after NM stateful restart Key: YARN-4831 URL: https://issues.apache.org/jira/browse/YARN-4831 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-4831) Recovered containers will be killed after NM stateful restart

[ https://issues.apache.org/jira/browse/YARN-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4831: -- Description: {code} 2016-03-04 19:43:48,130 INFO

[jira] [Assigned] (YARN-4831) Recovered containers will be killed after NM stateful restart

[ https://issues.apache.org/jira/browse/YARN-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned YARN-4831: - Assignee: Siqi Li > Recovered containers will be killed after NM stateful restart >

[jira] [Updated] (YARN-2913) Fair scheduler should have ability to set MaxResourceDefault for each queue

[ https://issues.apache.org/jira/browse/YARN-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2913: -- Attachment: YARN-2913.v4.patch > Fair scheduler should have ability to set MaxResourceDefault for each queue >

[jira] [Updated] (YARN-2913) Fair scheduler should have ability to set MaxResourceDefault for each queue

[ https://issues.apache.org/jira/browse/YARN-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2913: -- Attachment: YARN-2913.v5.patch > Fair scheduler should have ability to set MaxResourceDefault for each queue >

[jira] [Updated] (YARN-2913) Fair scheduler should have ability to set MaxResourceDefault for each queue

[ https://issues.apache.org/jira/browse/YARN-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2913: -- Attachment: YARN-2913.v3.patch > Fair scheduler should have ability to set MaxResourceDefault for each queue >

[jira] [Updated] (YARN-2913) Fair scheduler should have ability to set MaxResourceDefault for each queue

[ https://issues.apache.org/jira/browse/YARN-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2913: -- Attachment: YARN-2913.v2.patch > Fair scheduler should have ability to set MaxResourceDefault for each queue >

[jira] [Commented] (YARN-2913) Fair scheduler should have ability to set MaxResourceDefault for each queue

[ https://issues.apache.org/jira/browse/YARN-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14965716#comment-14965716 ] Siqi Li commented on YARN-2913: --- Hi [~mingma], Can you take a look at this patch? > Fair scheduler should

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14933639#comment-14933639 ] Siqi Li commented on YARN-3944: --- Agreed, I will close this one > Connection refused to nodemanagers are

[jira] [Created] (YARN-4033) In FairScheduler, parent queues should also display queue status

Siqi Li created YARN-4033: - Summary: In FairScheduler, parent queues should also display queue status Key: YARN-4033 URL: https://issues.apache.org/jira/browse/YARN-4033 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-4033) In FairScheduler, parent queues should also display queue status

[ https://issues.apache.org/jira/browse/YARN-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4033: -- Attachment: Screen Shot 2015-08-07 at 2.04.04 PM.png In FairScheduler, parent queues should also display queue

[jira] [Updated] (YARN-4033) In FairScheduler, parent queues should also display queue status

[ https://issues.apache.org/jira/browse/YARN-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4033: -- Attachment: YARN-4033.v1.patch In FairScheduler, parent queues should also display queue status

[jira] [Updated] (YARN-4033) In FairScheduler, parent queues should also display queue status

[ https://issues.apache.org/jira/browse/YARN-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4033: -- Attachment: patch In FairScheduler, parent queues should also display queue status

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14662122#comment-14662122 ] Siqi Li commented on YARN-3176: --- If we don't allow a queue inherit properties from its

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14662391#comment-14662391 ] Siqi Li commented on YARN-3176: --- From FairSchedulerPage, it looks like the UI has already

[jira] [Updated] (YARN-4033) In FairScheduler, parent queues should also display queue status

[ https://issues.apache.org/jira/browse/YARN-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4033: -- Attachment: (was: screenshot-1.png) In FairScheduler, parent queues should also display queue status

[jira] [Updated] (YARN-4033) In FairScheduler, parent queues should also display queue status

[ https://issues.apache.org/jira/browse/YARN-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4033: -- Attachment: (was: patch) In FairScheduler, parent queues should also display queue status

[jira] [Updated] (YARN-4033) In FairScheduler, parent queues should also display queue status

[ https://issues.apache.org/jira/browse/YARN-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-4033: -- Attachment: screenshot-1.png In FairScheduler, parent queues should also display queue status

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660787#comment-14660787 ] Siqi Li commented on YARN-3176: --- One example could be queueMaxAppsDefault is set to 50, and

[jira] [Commented] (YARN-2414) RM web UI: app page will crash if app is failed before any attempt has been created

[ https://issues.apache.org/jira/browse/YARN-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660689#comment-14660689 ] Siqi Li commented on YARN-2414: --- The latest patch can be applied to 2.6.0 branch cleanly RM

[jira] [Commented] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

[ https://issues.apache.org/jira/browse/YARN-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660704#comment-14660704 ] Siqi Li commented on YARN-3641: --- The latest patch can be applied to 2.6.0 branch cleanly

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660895#comment-14660895 ] Siqi Li commented on YARN-3176: --- Considering an other example, grandparent - parent - child

[jira] [Commented] (YARN-3526) ApplicationMaster tracking URL is incorrectly redirected on a QJM cluster

[ https://issues.apache.org/jira/browse/YARN-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660686#comment-14660686 ] Siqi Li commented on YARN-3526: --- The latest patch can be applied to 2.6.0 branch cleanly

[jira] [Commented] (YARN-2997) NM keeps sending already-sent completed containers to RM until containers are removed from context

[ https://issues.apache.org/jira/browse/YARN-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660692#comment-14660692 ] Siqi Li commented on YARN-2997: --- The latest patch can be applied to 2.6.0 branch cleanly NM

[jira] [Commented] (YARN-3094) reset timer for liveness monitors after RM recovery

[ https://issues.apache.org/jira/browse/YARN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660694#comment-14660694 ] Siqi Li commented on YARN-3094: --- The latest patch can be applied to 2.6.0 branch cleanly

[jira] [Commented] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

[ https://issues.apache.org/jira/browse/YARN-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660701#comment-14660701 ] Siqi Li commented on YARN-3485: --- The latest patch can be applied to 2.6.0 branch cleanly

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661251#comment-14661251 ] Siqi Li commented on YARN-3176: --- That makes sense. If you feel like this change is

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660948#comment-14660948 ] Siqi Li commented on YARN-3176: --- for that, we can maybe introduce something like a default as

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14660651#comment-14660651 ] Siqi Li commented on YARN-3176: --- [~ashwinshankar77], I don't think the sample alloc is a good

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Attachment: YARN-3960.v1.patch FairScheduler, Assign default child queue to applications that specifies only

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Attachment: YARN-3960.v1.patch FairScheduler, Assign default child queue to applications that specifies only

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Attachment: (was: YARN-3960.v1.patch) FairScheduler, Assign default child queue to applications that

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Attachment: YARN-3960.v1.patch FairScheduler, Assign default child queue to applications that specifies only

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Attachment: (was: YARN-3960.v1.patch) FairScheduler, Assign default child queue to applications that

[jira] [Created] (YARN-3960) Assign default child queue to applications that specifies only parent queue name

Siqi Li created YARN-3960: - Summary: Assign default child queue to applications that specifies only parent queue name Key: YARN-3960 URL: https://issues.apache.org/jira/browse/YARN-3960 Project: Hadoop YARN

[jira] [Assigned] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned YARN-3960: - Assignee: Siqi Li FairScheduler, Assign default child queue to applications that specifies only parent

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Description: For a tier queue in fair scheduler, if you submits a job without specifying the exact child queue.

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Summary: FairScheduler, Assign default child queue to applications that specifies only parent queue name (was:

[jira] [Updated] (YARN-3960) FairScheduler, Assign default child queue to applications that specifies only parent queue name

[ https://issues.apache.org/jira/browse/YARN-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3960: -- Component/s: fairscheduler FairScheduler, Assign default child queue to applications that specifies only

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Priority: Critical (was: Blocker) Connection refused to nodemanagers are retried at multiple levels

[jira] [Assigned] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned YARN-3944: - Assignee: Siqi Li Connection refused to nodemanagers are retried at multiple levels

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Attachment: YARN-3944.v1.patch Connection refused to nodemanagers are retried at multiple levels

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Affects Version/s: 2.6.0 Connection refused to nodemanagers are retried at multiple levels

[jira] [Created] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

Siqi Li created YARN-3944: - Summary: Connection refused to nodemanagers are retried at multiple levels Key: YARN-3944 URL: https://issues.apache.org/jira/browse/YARN-3944 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3944: -- Description: This is related to YARN-3238. When NM is down, ipc client will get ConnectException. Caused by:

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634286#comment-14634286 ] Siqi Li commented on YARN-3944: --- [~zxu], this is not a duplicate of YARN-3238(i.e.

[jira] [Commented] (YARN-3944) Connection refused to nodemanagers are retried at multiple levels

[ https://issues.apache.org/jira/browse/YARN-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14634513#comment-14634513 ] Siqi Li commented on YARN-3944: --- [~zxu] Thanks for your quick response, I think the reason we

[jira] [Commented] (YARN-3891) Apps are starved for resource due to default FairSharePolicy in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616287#comment-14616287 ] Siqi Li commented on YARN-3891: --- Yes, I think this is related to MAPREDUCE-6302. So if

[jira] [Resolved] (YARN-3891) Apps are starved for resource due to default FairSharePolicy in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-3891. --- Resolution: Duplicate Assignee: Siqi Li Apps are starved for resource due to default FairSharePolicy in

[jira] [Created] (YARN-3891) Apps are starved for resource due to default fair share scheduling policy in Fair Scheduler

Siqi Li created YARN-3891: - Summary: Apps are starved for resource due to default fair share scheduling policy in Fair Scheduler Key: YARN-3891 URL: https://issues.apache.org/jira/browse/YARN-3891 Project:

[jira] [Updated] (YARN-3891) Apps are starved for resource due to default fair share scheduling policy in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3891: -- Description: Based on FairSharePolicy, FSLeafQueue Apps are starved for resource due to default fair share

[jira] [Updated] (YARN-3891) Apps are starved for resource due to default FairSharePolicy in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3891: -- Summary: Apps are starved for resource due to default FairSharePolicy in Fair Scheduler (was: Apps are starved

[jira] [Updated] (YARN-3891) Apps are starved for resource due to default FairSharePolicy in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3891: -- Description: Based on FairSharePolicy, FSLeafQueue will try to schedule an app that has the lowest resource

[jira] [Commented] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14596257#comment-14596257 ] Siqi Li commented on YARN-3176: --- Hi [~djp], can you take a look at patch v2. The checkstyle

[jira] [Updated] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp and maxResource from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3176: -- Summary: In Fair Scheduler, child queue should inherit maxApp and maxResource from its parent (was: In Fair

[jira] [Updated] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3176: -- Attachment: YARN-3176.v2.patch In Fair Scheduler, child queue should inherit maxApp from its parent

[jira] [Updated] (YARN-3176) In Fair Scheduler, child queue should inherit maxApp from its parent

[ https://issues.apache.org/jira/browse/YARN-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3176: -- Summary: In Fair Scheduler, child queue should inherit maxApp from its parent (was: In Fair Scheduler, child

[jira] [Commented] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556442#comment-14556442 ] Siqi Li commented on YARN-1391: --- [~djp] Looks like, the trunk has already have this patch.

[jira] [Resolved] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-1391. --- Resolution: Duplicate Lost node list should be identify by NodeId

[jira] [Reopened] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reopened YARN-1391: --- Lost node list should be identify by NodeId --- Key:

[jira] [Resolved] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-1391. --- Resolution: Fixed Lost node list should be identify by NodeId ---

[jira] [Commented] (YARN-1391) Lost node list should be identify by NodeId

[ https://issues.apache.org/jira/browse/YARN-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14556447#comment-14556447 ] Siqi Li commented on YARN-1391: --- here is the duplicate jira YARN-3266 Lost node list should

[jira] [Commented] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550734#comment-14550734 ] Siqi Li commented on YARN-1945: --- Hi [~xgong], I just rebased the patch, and checkstyle and

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v4.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Commented] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14551351#comment-14551351 ] Siqi Li commented on YARN-2876: --- Hi [~leftnoteasy], I have uploaded patch v4 that added a

[jira] [Commented] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14550728#comment-14550728 ] Siqi Li commented on YARN-1735: --- Hi [~jianhe], I just rebased the patch, and checkstyle,

[jira] [Commented] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548239#comment-14548239 ] Siqi Li commented on YARN-3468: --- Agreed. setting yarn.nodemanager.delete.debug-delay-sec to

[jira] [Resolved] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li resolved YARN-3468. --- Resolution: Won't Fix NM should not blindly rename usercache/filecache/nmPrivate on restart

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v2.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: YARN-1945.v6.patch Adding description for each pool in Fair Scheduler Page from

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v2.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Updated] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Attachment: YARN-1735.v2.patch For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: (was: YARN-2876.v2.patch) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource

[jira] [Commented] (YARN-1896) For FairScheduler expose MinimumQueueResource of each queue in QueueMetrics

[ https://issues.apache.org/jira/browse/YARN-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14548265#comment-14548265 ] Siqi Li commented on YARN-1896: --- As I said in the description, it would be good to have

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v2.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: (was: YARN-2876.v2.patch) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: YARN-1945.v6.patch Adding description for each pool in Fair Scheduler Page from

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: (was: YARN-1945.v6.patch) Adding description for each pool in Fair Scheduler Page from

[jira] [Updated] (YARN-2876) In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for subqueues

[ https://issues.apache.org/jira/browse/YARN-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-2876: -- Attachment: YARN-2876.v3.patch In Fair Scheduler, JMX and Scheduler UI display wrong maxResource info for

[jira] [Updated] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Attachment: YARN-1735.v3.patch For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[jira] [Updated] (YARN-1735) For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[ https://issues.apache.org/jira/browse/YARN-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1735: -- Attachment: YARN-1735.v4.patch For FairScheduler AvailableMB in QueueMetrics is the same as AllocateMB

[jira] [Updated] (YARN-1945) Adding description for each pool in Fair Scheduler Page from fair-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-1945: -- Attachment: YARN-1945.v7.patch Adding description for each pool in Fair Scheduler Page from

[jira] [Assigned] (YARN-3532) nodemanager version in RM nodes page didn't update when NMs rejoin

[ https://issues.apache.org/jira/browse/YARN-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li reassigned YARN-3532: - Assignee: Siqi Li nodemanager version in RM nodes page didn't update when NMs rejoin

[jira] [Created] (YARN-3532) nodemanager version in RM nodes page didn't update when NMs rejoin

Siqi Li created YARN-3532: - Summary: nodemanager version in RM nodes page didn't update when NMs rejoin Key: YARN-3532 URL: https://issues.apache.org/jira/browse/YARN-3532 Project: Hadoop YARN

[jira] [Updated] (YARN-3532) nodemanager version in RM nodes page didn't update when NMs rejoin

[ https://issues.apache.org/jira/browse/YARN-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3532: -- Attachment: YARN-3532.v1.patch nodemanager version in RM nodes page didn't update when NMs rejoin

[jira] [Updated] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3468: -- Attachment: YARN-3468.v2.patch NM should not blindly rename usercache/filecache/nmPrivate on restart

[jira] [Commented] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14504151#comment-14504151 ] Siqi Li commented on YARN-3468: --- Got it. I will modify the patch as you suggested NM should

[jira] [Commented] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14487979#comment-14487979 ] Siqi Li commented on YARN-3468: --- Can anyone have some comments on this jira? NM should not

[jira] [Created] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

Siqi Li created YARN-3468: - Summary: NM should not blindly rename usercache/filecache/nmPrivate on restart Key: YARN-3468 URL: https://issues.apache.org/jira/browse/YARN-3468 Project: Hadoop YARN

[jira] [Commented] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14486285#comment-14486285 ] Siqi Li commented on YARN-3468: --- The renaming is causing a enormous number of _DEL_timestamp

[jira] [Updated] (YARN-3468) NM should not blindly rename usercache/filecache/nmPrivate on restart

[ https://issues.apache.org/jira/browse/YARN-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3468: -- Attachment: YARN-3468.v1.patch NM should not blindly rename usercache/filecache/nmPrivate on restart

[jira] [Commented] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14343840#comment-14343840 ] Siqi Li commented on YARN-3231: --- Hi [~kasha], I have added two test cases for reducing

[jira] [Updated] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3231: -- Attachment: YARN-3231.v3.patch FairScheduler changing queueMaxRunningApps on the fly will cause all pending

[jira] [Commented] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14339214#comment-14339214 ] Siqi Li commented on YARN-3231: --- Hi [~ka...@cloudera.com], thanks for your feedback. I have

[jira] [Updated] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3231: -- Attachment: YARN-3231.v4.patch FairScheduler changing queueMaxRunningApps on the fly will cause all pending

[jira] [Updated] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3231: -- Attachment: YARN-3231.v2.patch FairScheduler changing queueMaxRunningApps on the fly will cause all pending

[jira] [Updated] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3231: -- Attachment: (was: YARN-3231.v2.patch) FairScheduler changing queueMaxRunningApps on the fly will cause all

[jira] [Commented] (YARN-3231) FairScheduler changing queueMaxRunningApps on the fly will cause all pending job stuck

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335770#comment-14335770 ] Siqi Li commented on YARN-3231: --- find bugs and test failures seems not to be related to this

  1   2   3   4   >