[jira] [Updated] (YARN-6664) Backport YARN-5988 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-6664: Attachment: YARN-5988-branch-2.7.0001.patch > Backport YARN-5988 to branch-2.8, branch-2.7 >

[jira] [Updated] (YARN-6664) Backport YARN-5988 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-6664: Attachment: YARN-5988-branch-2.8.0001.patch > Backport YARN-5988 to branch-2.8, branch-2.7 >

[jira] [Commented] (YARN-5892) Capacity Scheduler: Support user-specific minimum user limit percent

[ https://issues.apache.org/jira/browse/YARN-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032499#comment-16032499 ] Sunil G commented on YARN-5892: --- Latest patch seems fine for me. [~leftnoteasy], could you also please take a

[jira] [Commented] (YARN-6663) Backport YARN-5333 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032493#comment-16032493 ] Sunil G commented on YARN-6663: --- Committed to branch-2.7. I will wait for jenkins issue to commit branch-2.8

[jira] [Commented] (YARN-6320) FairScheduler:Identifying apps to assign in updateThread

[ https://issues.apache.org/jira/browse/YARN-6320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032452#comment-16032452 ] daemon commented on YARN-6320: -- I think I have solved the problem and in my test environment the scheduler can

[jira] [Commented] (YARN-1471) The SLS simulator is not running the preemption policy for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032448#comment-16032448 ] Konstantin Shvachko commented on YARN-1471: --- Hey guys. Let's target full SLS feature for the next

[jira] [Commented] (YARN-6663) Backport YARN-5333 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032411#comment-16032411 ] Akira Ajisaka commented on YARN-6663: - It seems oracle-java7-install is failing.

[jira] [Commented] (YARN-5953) Create CLI for changing YARN configurations

[ https://issues.apache.org/jira/browse/YARN-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032387#comment-16032387 ] Jonathan Hung commented on YARN-5953: - Attached 001 patch for changing scheduler configurations via

[jira] [Updated] (YARN-5953) Create CLI for changing YARN configurations

[ https://issues.apache.org/jira/browse/YARN-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Hung updated YARN-5953: Attachment: YARN-5953-YARN-5734.001.patch > Create CLI for changing YARN configurations >

[jira] [Commented] (YARN-6663) Backport YARN-5333 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032369#comment-16032369 ] Sunil G commented on YARN-6663: --- I ll commit branch-2.7 patch meantime so that other dependent jiras could go

[jira] [Commented] (YARN-6663) Backport YARN-5333 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032365#comment-16032365 ] Rohith Sharma K S commented on YARN-6663: - It appears like issue with jenkins to run branch-2.8

[jira] [Updated] (YARN-6511) Federation Intercepting and propagating AM-RM communications (part two: secondary subclusters added)

[ https://issues.apache.org/jira/browse/YARN-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-6511: --- Attachment: YARN-6511-YARN-2915.v2.patch > Federation Intercepting and propagating AM-RM

[jira] [Assigned] (YARN-5094) some YARN container events have timestamp of -1 in REST output

[ https://issues.apache.org/jira/browse/YARN-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen reassigned YARN-5094: Assignee: Haibo Chen (was: Li Lu) > some YARN container events have timestamp of -1 in REST output

[jira] [Assigned] (YARN-6199) Support for listing flows with filter userid

[ https://issues.apache.org/jira/browse/YARN-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen reassigned YARN-6199: Assignee: Haibo Chen > Support for listing flows with filter userid >

[jira] [Commented] (YARN-6511) Federation Intercepting and propagating AM-RM communications (part two: secondary subclusters added)

[ https://issues.apache.org/jira/browse/YARN-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032217#comment-16032217 ] Hadoop QA commented on YARN-6511: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6246) Identifying starved apps does not need the scheduler writelock

[ https://issues.apache.org/jira/browse/YARN-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032202#comment-16032202 ] Hudson commented on YARN-6246: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11807 (See

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032185#comment-16032185 ] Haibo Chen commented on YARN-6323: -- In rolling upgrade cases where the newer version of YARN cluster has

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032114#comment-16032114 ] Konstantin Shvachko commented on YARN-4140: --- Hey [~bibinchundatt] did you want to work on porting

[jira] [Updated] (YARN-6511) Federation Intercepting and propagating AM-RM communications (part two: secondary subclusters added)

[ https://issues.apache.org/jira/browse/YARN-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-6511: --- Attachment: YARN-6511-YARN-2915.v1.patch > Federation Intercepting and propagating AM-RM

[jira] [Comment Edited] (YARN-6634) [API] Define an API for ResourceManager WebServices

[ https://issues.apache.org/jira/browse/YARN-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032053#comment-16032053 ] Subru Krishnan edited comment on YARN-6634 at 5/31/17 9:55 PM: ---

[jira] [Commented] (YARN-6634) [API] Define an API for ResourceManager WebServices

[ https://issues.apache.org/jira/browse/YARN-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032053#comment-16032053 ] Subru Krishnan commented on YARN-6634: -- [~giovanni.fumarola], I know it's a nit but you can try

[jira] [Commented] (YARN-6323) Rolling upgrade/config change is broken on timeline v2.

[ https://issues.apache.org/jira/browse/YARN-6323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16032023#comment-16032023 ] Vrushali C commented on YARN-6323: -- Hmm, I have been thinking over this and I think we all discussed a bit

[jira] [Commented] (YARN-6663) Backport YARN-5333 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031967#comment-16031967 ] Hadoop QA commented on YARN-6663: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-3666) Federation Intercepting and propagating AM- home RM communications

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031930#comment-16031930 ] Botong Huang commented on YARN-3666: Great, thanks [~subru] and [~curino] for the feedback! @All

[jira] [Updated] (YARN-6677) Pause and preempt containers when root container cgroup goes over memory limit

[ https://issues.apache.org/jira/browse/YARN-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-6677: - Issue Type: Sub-task (was: Bug) Parent: YARN-1011 > Pause and preempt containers when root

[jira] [Created] (YARN-6677) Pause and preempt containers when root container cgroup goes over memory limit

Haibo Chen created YARN-6677: Summary: Pause and preempt containers when root container cgroup goes over memory limit Key: YARN-6677 URL: https://issues.apache.org/jira/browse/YARN-6677 Project: Hadoop

[jira] [Updated] (YARN-6670) Add separate configurations for cpu and memory oversubscription

[ https://issues.apache.org/jira/browse/YARN-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen updated YARN-6670: - Summary: Add separate configurations for cpu and memory oversubscription (was: Add over-allocation

[jira] [Reopened] (YARN-6670) Add over-allocation thresholds to allow per-node oversubscription

[ https://issues.apache.org/jira/browse/YARN-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen reopened YARN-6670: -- Reopen to add separate thresholds for CPU and memory over allocation > Add over-allocation thresholds to

[jira] [Updated] (YARN-3666) Federation Intercepting and propagating AM- home RM communications

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3666: - Summary: Federation Intercepting and propagating AM- home RM communications (was: Federation

[jira] [Commented] (YARN-4925) ContainerRequest in AMRMClient, application should be able to specify nodes/racks together with nodeLabelExpression

[ https://issues.apache.org/jira/browse/YARN-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031876#comment-16031876 ] Konstantin Shvachko commented on YARN-4925: --- I've done quite a few runs for the client tests. I

[jira] [Commented] (YARN-3666) Federation Intercepting and propagating AM-RM communications (part one: home RM only)

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031825#comment-16031825 ] Botong Huang commented on YARN-3666: Unit test

[jira] [Assigned] (YARN-5978) ContainerScheduler and Container state machine changes to support ExecType update

[ https://issues.apache.org/jira/browse/YARN-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh reassigned YARN-5978: - Assignee: Arun Suresh > ContainerScheduler and Container state machine changes to support

[jira] [Resolved] (YARN-6670) Add over-allocation thresholds to allow per-node oversubscription

[ https://issues.apache.org/jira/browse/YARN-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haibo Chen resolved YARN-6670. -- Resolution: Duplicate > Add over-allocation thresholds to allow per-node oversubscription >

[jira] [Created] (YARN-6676) ComputeFairShares#computeSharesInternal() is inefficient and lossy

Daniel Templeton created YARN-6676: -- Summary: ComputeFairShares#computeSharesInternal() is inefficient and lossy Key: YARN-6676 URL: https://issues.apache.org/jira/browse/YARN-6676 Project: Hadoop

[jira] [Commented] (YARN-6649) RollingLevelDBTimelineServer throws RuntimeException if object decoding ever fails runtime exception

[ https://issues.apache.org/jira/browse/YARN-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031773#comment-16031773 ] Hudson commented on YARN-6649: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11806 (See

[jira] [Commented] (YARN-6547) Enhance SLS-based tests leveraging invariant checker

[ https://issues.apache.org/jira/browse/YARN-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031700#comment-16031700 ] Carlo Curino commented on YARN-6547: [~wangda] thanks for the feedback. I will need to slightly change

[jira] [Updated] (YARN-6649) RollingLevelDBTimelineServer throws RuntimeException if object decoding ever fails runtime exception

[ https://issues.apache.org/jira/browse/YARN-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Roberts updated YARN-6649: - Fix Version/s: 2.8.2 2.8.1 2.9.0 >

[jira] [Updated] (YARN-6649) RollingLevelDBTimelineServer throws RuntimeException if object decoding ever fails runtime exception

[ https://issues.apache.org/jira/browse/YARN-6649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Roberts updated YARN-6649: - Fix Version/s: 3.0.0-alpha4 > RollingLevelDBTimelineServer throws RuntimeException if object

[jira] [Commented] (YARN-6246) Identifying starved apps does not need the scheduler writelock

[ https://issues.apache.org/jira/browse/YARN-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031478#comment-16031478 ] Daniel Templeton commented on YARN-6246: I agree. Seems like a good choice to me. > Identifying

[jira] [Commented] (YARN-1471) The SLS simulator is not running the preemption policy for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031475#comment-16031475 ] Carlo Curino commented on YARN-1471: I believe it should be. YARN-6608 will need some more massaging,

[jira] [Commented] (YARN-6599) Support rich placement constraints in scheduler

[ https://issues.apache.org/jira/browse/YARN-6599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031469#comment-16031469 ] Carlo Curino commented on YARN-6599: (Pardon my own delay... moving/travelling) I hear you... There

[jira] [Commented] (YARN-3666) Federation Intercepting and propagating AM-RM communications (part one: home RM only)

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031438#comment-16031438 ] Hadoop QA commented on YARN-3666: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6497) Method length of ResourceManager#serviceInit() is too long

[ https://issues.apache.org/jira/browse/YARN-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031407#comment-16031407 ] Hudson commented on YARN-6497: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11804 (See

[jira] [Commented] (YARN-6484) [Documentation] Documenting the YARN Federation feature

[ https://issues.apache.org/jira/browse/YARN-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031390#comment-16031390 ] Carlo Curino commented on YARN-6484: Thanks [~subru] for reviewing and committing. > [Documentation]

[jira] [Commented] (YARN-5892) Capacity Scheduler: Support user-specific minimum user limit percent

[ https://issues.apache.org/jira/browse/YARN-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031352#comment-16031352 ] Eric Payne commented on YARN-5892: -- The findbugs warning was in code that was not changed by this patch.

[jira] [Updated] (YARN-6497) Method length of ResourceManager#serviceInit() is too long

[ https://issues.apache.org/jira/browse/YARN-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-6497: -- Labels: checkstyle newbie++ (was: newbie++) > Method length of ResourceManager#serviceInit() is

[jira] [Updated] (YARN-3666) Federation Intercepting and propagating AM-RM communications (part one: home RM only)

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Botong Huang updated YARN-3666: --- Attachment: YARN-3666-YARN-2915.v9.patch The test failure in

[jira] [Commented] (YARN-6366) Refactor the NodeManager DeletionService to support additional DeletionTask types.

[ https://issues.apache.org/jira/browse/YARN-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031010#comment-16031010 ] Hudson commented on YARN-6366: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11802 (See

[jira] [Commented] (YARN-6663) Backport YARN-5333 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030848#comment-16030848 ] Hadoop QA commented on YARN-6663: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6280) Add a query parameter in ResourceManager Cluster Applications REST API to control whether or not returns ResourceRequest

[ https://issues.apache.org/jira/browse/YARN-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030708#comment-16030708 ] Rohith Sharma K S commented on YARN-6280: - Overall patch looks good. Some nits # DeSelectParam

[jira] [Commented] (YARN-6663) Backport YARN-5333 to branch-2.8, branch-2.7

[ https://issues.apache.org/jira/browse/YARN-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030695#comment-16030695 ] Hadoop QA commented on YARN-6663: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6497) Method length of ResourceManager#serviceInit() is too long

[ https://issues.apache.org/jira/browse/YARN-6497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030689#comment-16030689 ] Gergely Novák commented on YARN-6497: - [~jeagles] The test failures are definitely not related to the