[jira] [Commented] (YARN-4084) Yarn should allow to skip hadoop-yarn-server-tests project from build..

[ https://issues.apache.org/jira/browse/YARN-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715306#comment-14715306 ] Ved Prakash Pandey commented on YARN-4084: -- Thanks for reply Allen. Actually I

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715342#comment-14715342 ] Ben Podgursky commented on YARN-2962: - Hi, We're looking at switching to a HA RM and

[jira] [Created] (YARN-4086) Allow Aggregated Log readers to handle HAR files

Robert Kanter created YARN-4086: --- Summary: Allow Aggregated Log readers to handle HAR files Key: YARN-4086 URL: https://issues.apache.org/jira/browse/YARN-4086 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-3717) Improve RM node labels web UI

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

[jira] [Comment Edited] (YARN-4084) Yarn should allow to skip hadoop-yarn-server-tests project from build..

[ https://issues.apache.org/jira/browse/YARN-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715429#comment-14715429 ] Allen Wittenauer edited comment on YARN-4084 at 8/26/15 8:10 PM:

[jira] [Commented] (YARN-4084) Yarn should allow to skip hadoop-yarn-server-tests project from build..

[ https://issues.apache.org/jira/browse/YARN-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715429#comment-14715429 ] Allen Wittenauer commented on YARN-4084: So then mvn compile is actually what you

[jira] [Commented] (YARN-4084) Yarn should allow to skip hadoop-yarn-server-tests project from build..

[ https://issues.apache.org/jira/browse/YARN-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715338#comment-14715338 ] Ved Prakash Pandey commented on YARN-4084: -- I realize that my patch enforces to

[jira] [Commented] (YARN-4082) Container shouldn't be killed when node's label updated.

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

[jira] [Updated] (YARN-2884) Proxying all AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishore Chaliparambil updated YARN-2884: Attachment: YARN-2884-V11.patch Removed the ApplicationConstants.java file from the

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712619#comment-14712619 ] Varun Saxena commented on YARN-3893: I do not have any concern for exiting JVM. If fail

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

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

[jira] [Commented] (YARN-3816) [Aggregation] App-level Aggregation for YARN system metrics

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14714416#comment-14714416 ] Junping Du commented on YARN-3816: -- Thanks [~varun_saxena] for review and comments! bq. If

[jira] [Updated] (YARN-4082) Container shouldn't be killed when node's label updated.

[ https://issues.apache.org/jira/browse/YARN-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4082: - Attachment: YARN-4082.2.patch Attached .2 patch, fixed findbugs warnings. Container shouldn't be killed

[jira] [Updated] (YARN-3717) Improve RM node labels web UI

[ https://issues.apache.org/jira/browse/YARN-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3717: Attachment: YARN-3717.20150826-1.patch Fixing reported testcase failure and locally ran

[jira] [Created] (YARN-4085) Generate file with container resource limits in the container work dir

Varun Vasudev created YARN-4085: --- Summary: Generate file with container resource limits in the container work dir Key: YARN-4085 URL: https://issues.apache.org/jira/browse/YARN-4085 Project: Hadoop

[jira] [Commented] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715208#comment-14715208 ] Vrushali C commented on YARN-4074: -- My take is that we can make things as generic as

[jira] [Commented] (YARN-4053) Change the way metric values are stored in HBase Storage

[ https://issues.apache.org/jira/browse/YARN-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715192#comment-14715192 ] Vrushali C commented on YARN-4053: -- The way I see this, it comes down to a basic question

[jira] [Updated] (YARN-4076) FairScheduler does not allow AM to choose which containers to preempt

[ https://issues.apache.org/jira/browse/YARN-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4076: --- Component/s: fairscheduler FairScheduler does not allow AM to choose which containers to

[jira] [Updated] (YARN-4077) FairScheduler Reservation should wait for most relaxed scheduling delay permitted before issuing reservation

[ https://issues.apache.org/jira/browse/YARN-4077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4077: --- Component/s: fairscheduler FairScheduler Reservation should wait for most relaxed scheduling

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715681#comment-14715681 ] Varun Saxena commented on YARN-3528: Will have a look. Tests with 12345 as hard-coded

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715519#comment-14715519 ] Varun Saxena commented on YARN-2962: bq. how many applications did you have in the RM

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715641#comment-14715641 ] Robert Kanter commented on YARN-3528: - +1 LGTM. Any other comments [~varun_saxena]?

[jira] [Updated] (YARN-4086) Allow Aggregated Log readers to handle HAR files

[ https://issues.apache.org/jira/browse/YARN-4086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated YARN-4086: Attachment: YARN-4086.001.patch The YARN-4086.001.patch allows the yarn CLI and web UIs to read

[jira] [Commented] (YARN-4086) Allow Aggregated Log readers to handle HAR files

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

[jira] [Commented] (YARN-2962) ZKRMStateStore: Limit the number of znodes under a znode

[ https://issues.apache.org/jira/browse/YARN-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715591#comment-14715591 ] Ben Podgursky commented on YARN-2962: - Got it. Thanks for the details. It sounds like

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712637#comment-14712637 ] Varun Saxena commented on YARN-3893: Infact according to me, we can crash RM on all

[jira] [Commented] (YARN-2884) Proxying all AM-RM communications

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

[jira] [Updated] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3893: --- Attachment: 0006-YARN-3893.patch So JVM exit is the conclusion after discussion. Attaching

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712896#comment-14712896 ] Varun Saxena commented on YARN-3893: The latest patch, 0008-YARN-3893.patch LGTM. +1

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712745#comment-14712745 ] Sunil G commented on YARN-3893: --- As I see this, JVM exit is reasonable as proposed by Rohith

[jira] [Updated] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3893: --- Attachment: 0007-YARN-3893.patch Missed one comment {{isRMActive}} check is not

[jira] [Updated] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3893: --- Attachment: 0008-YARN-3893.patch Both RM in active state when Admin#transitionToActive

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

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

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

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

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712984#comment-14712984 ] Brahma Reddy Battula commented on YARN-3528: Testcase failures are

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713001#comment-14713001 ] Bibin A Chundatt commented on YARN-3893: Test failures are not related to this

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712931#comment-14712931 ] Brahma Reddy Battula commented on YARN-3528: [~rkanter] Sorry for delay and

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

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

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713002#comment-14713002 ] Bibin A Chundatt commented on YARN-3893: Above comments are for

[jira] [Updated] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3528: --- Attachment: YARN-3528-006.patch Tests with 12345 as hard-coded port break jenkins

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712999#comment-14712999 ] Hadoop QA commented on YARN-3893: - \\ \\ | (/) *{color:green}+1 overall{color}* | \\ \\ ||

[jira] [Commented] (YARN-4084) Yarn should allow to skip hadoop-yarn-server-tests project from build..

[ https://issues.apache.org/jira/browse/YARN-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713541#comment-14713541 ] Allen Wittenauer commented on YARN-4084: Use -PskipTests in addition to

[jira] [Comment Edited] (YARN-4084) Yarn should allow to skip hadoop-yarn-server-tests project from build..

[ https://issues.apache.org/jira/browse/YARN-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713541#comment-14713541 ] Allen Wittenauer edited comment on YARN-4084 at 8/26/15 2:36 PM:

[jira] [Commented] (YARN-3798) ZKRMStateStore shouldn't create new session without occurrance of SESSIONEXPIED

[ https://issues.apache.org/jira/browse/YARN-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712700#comment-14712700 ] Tsuyoshi Ozawa commented on YARN-3798: -- [~vinodkv] [~zxu] could you check the latest

[jira] [Commented] (YARN-3893) Both RM in active state when Admin#transitionToActive failure from refeshAll()

[ https://issues.apache.org/jira/browse/YARN-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14712767#comment-14712767 ] Varun Saxena commented on YARN-3893: Yes I agree. We can exit JVM directly. No need of

[jira] [Commented] (YARN-4029) Update LogAggregationStatus to store on finish

[ https://issues.apache.org/jira/browse/YARN-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14713076#comment-14713076 ] Bibin A Chundatt commented on YARN-4029: Hi [~xgong] Could you please review patch

[jira] [Commented] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715765#comment-14715765 ] Sangjin Lee commented on YARN-4074: --- I am about 90% done with the POC patch for this. I'm

[jira] [Updated] (YARN-4087) Set YARN_FAIL_FAST to be false by default

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Summary: Set YARN_FAIL_FAST to be false by default (was: Set RM_FAIL_FAST to be false by default) Set

[jira] [Commented] (YARN-3816) [Aggregation] App-level Aggregation for YARN system metrics

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715809#comment-14715809 ] Li Lu commented on YARN-3816: - Hi [~djp], I briefly looked at the patch, and have one quick

[jira] [Commented] (YARN-4087) Set YARN_FAIL_FAST to be false by default

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715829#comment-14715829 ] Karthik Kambatla commented on YARN-4087: +1, if fail-fast hasn't been in any prior

[jira] [Commented] (YARN-3528) Tests with 12345 as hard-coded port break jenkins

[ https://issues.apache.org/jira/browse/YARN-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715754#comment-14715754 ] Varun Saxena commented on YARN-3528: # In TestNodeStatusUpdater#createNMConfig, change

[jira] [Created] (YARN-4087) Set RM_FAIL_FAST to be false by default

Jian He created YARN-4087: - Summary: Set RM_FAIL_FAST to be false by default Key: YARN-4087 URL: https://issues.apache.org/jira/browse/YARN-4087 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-4087) Set YARN_FAIL_FAST to be false by default

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Attachment: YARN-4087.1.patch simple patch which flips the config Set YARN_FAIL_FAST to be false by default

[jira] [Commented] (YARN-4087) Set YARN_FAIL_FAST to be false by default

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715872#comment-14715872 ] Bibin A Chundatt commented on YARN-4087: So by default in yarn-default.xml

[jira] [Commented] (YARN-4048) Linux kernel panic under strict CPU limits

[ https://issues.apache.org/jira/browse/YARN-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715561#comment-14715561 ] Craig Condit commented on YARN-4048: Just my two cents: Using cgroups on CentOS/RHEL

[jira] [Updated] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: YARN-3920.004.patch Attaching a patch based on the multiple of increment approach

[jira] [Updated] (YARN-4074) [timeline reader] implement support for querying for flows and flow runs

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4074: -- Attachment: YARN-4074-YARN-2928.POC.001.patch Posting a v.1 POC patch. This implements the first query

[jira] [Updated] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

[ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-3920: Attachment: YARN-3920.004.patch Updated configuration in FairSchedulerConfiguration FairScheduler

[jira] [Commented] (YARN-3920) FairScheduler Reserving a node for a container should be configurable to allow it used only for large containers

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

[jira] [Commented] (YARN-2745) Extend YARN to support multi-resource packing of tasks

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716019#comment-14716019 ] Srikanth Kandula commented on YARN-2745: Just a brief update on this JIRA... 1)

[jira] [Commented] (YARN-2745) Extend YARN to support multi-resource packing of tasks

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716023#comment-14716023 ] Srikanth Kandula commented on YARN-2745: [~aw] Done by [~chris.douglas]! Extend

[jira] [Commented] (YARN-2745) Extend YARN to support multi-resource packing of tasks

[ https://issues.apache.org/jira/browse/YARN-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716021#comment-14716021 ] Srikanth Kandula commented on YARN-2745: [~vinodkv] Thanks for the related. The

[jira] [Commented] (YARN-1012) Report NM aggregated container resource utilization in heartbeat

[ https://issues.apache.org/jira/browse/YARN-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716029#comment-14716029 ] Srikanth Kandula commented on YARN-1012: [~elgoiri], [~kasha] Could you comment on

[jira] [Commented] (YARN-4087) Set YARN_FAIL_FAST to be false by default

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

[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-tabpanelfocusedCommentId=14716034#comment-14716034 ] Srikanth Kandula commented on YARN-1011: This is a great idea. Is there an ETA for

[jira] [Created] (YARN-4088) RM should be able to process heartbeats from NM asynchronously

Srikanth Kandula created YARN-4088: -- Summary: RM should be able to process heartbeats from NM asynchronously Key: YARN-4088 URL: https://issues.apache.org/jira/browse/YARN-4088 Project: Hadoop YARN

[jira] [Commented] (YARN-4081) Add support for multiple resource types in the Resource class

[ https://issues.apache.org/jira/browse/YARN-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715991#comment-14715991 ] Srikanth Kandula commented on YARN-4081: Extending to multiple resources is great,

[jira] [Commented] (YARN-3250) Support admin cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715998#comment-14715998 ] Rohith Sharma K S commented on YARN-3250: - Thanks Sunil G for reviewing the patch.

[jira] [Commented] (YARN-3534) Collect memory/cpu usage on the node

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716031#comment-14716031 ] Srikanth Kandula commented on YARN-3534: [~elgoiri], [~kasha], could you comment on

[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-tabpanelfocusedCommentId=14716032#comment-14716032 ] Srikanth Kandula commented on YARN-3980: +1 this would be very useful to have...

[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-tabpanelfocusedCommentId=14716062#comment-14716062 ] Srikanth Kandula commented on YARN-1011: +1 [Umbrella] RM should dynamically