[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 p

[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-tabpanel&focusedCommentId=14712560#comment-14712560 ] Ved Prakash Pandey commented on YARN-4084: -- To fix this I have created a new profi

[jira] [Updated] (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:all-tabpanel ] Ved Prakash Pandey updated YARN-4084: - Attachment: YARN-4084.patch > Yarn should allow to skip hadoop-yarn-server-tests project fr

[jira] [Updated] (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:all-tabpanel ] Ved Prakash Pandey updated YARN-4084: - Description: For fast compilation one can try to skip the test code compilation by using {

[jira] [Updated] (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:all-tabpanel ] Ved Prakash Pandey updated YARN-4084: - Priority: Minor (was: Major) > Yarn should allow to skip hadoop-yarn-server-tests project

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

Ved Prakash Pandey created YARN-4084: Summary: Yarn should allow to skip hadoop-yarn-server-tests project from build.. Key: YARN-4084 URL: https://issues.apache.org/jira/browse/YARN-4084 Project:

[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-tabpanel&focusedCommentId=14712477#comment-14712477 ] Sunil G commented on YARN-3250: --- Latest patch looks good to me. Could you please check the te

[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-tabpanel&focusedCommentId=14712446#comment-14712446 ] Hadoop QA commented on YARN-2884: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (YARN-3854) Add localization support for docker images

[ https://issues.apache.org/jira/browse/YARN-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712426#comment-14712426 ] Jun Gong commented on YARN-3854: I think what we need is a private registry. Push local ima

[jira] [Commented] (YARN-4065) container-executor error should include effective user id

[ https://issues.apache.org/jira/browse/YARN-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712391#comment-14712391 ] Casey Brotherton commented on YARN-4065: Absolutely. Will start working on it > c

[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-V10.patch Uploaded YARN-2884-V10.patch. The changes in Containe

[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-tabpanel&focusedCommentId=14712308#comment-14712308 ] Rohith Sharma K S commented on YARN-3893: - Hi [~varun_saxena], trying to understand

[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-tabpanel&focusedCommentId=14712271#comment-14712271 ] Robert Kanter commented on YARN-3528: - Oops, wrong person. [~brahmareddy] > Tests wit

[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-tabpanel&focusedCommentId=14712269#comment-14712269 ] Robert Kanter commented on YARN-3528: - [~brahma], have you had a chance to look at the

[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-tabpanel&focusedCommentId=14712261#comment-14712261 ] Varun Saxena commented on YARN-3816: Hmm...Not being called by client is not a problem.

[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-tabpanel&focusedCommentId=14712230#comment-14712230 ] Li Lu commented on YARN-3816: - bq. Also I was wondering if TimelineMetric#aggregateTo should be

[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-tabpanel&focusedCommentId=14712224#comment-14712224 ] Hadoop QA commented on YARN-4082: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14712220#comment-14712220 ] Varun Saxena commented on YARN-3816: BTW, while TimelineMetric#toAggregate flag is mean

[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-tabpanel&focusedCommentId=14712209#comment-14712209 ] Subru Krishnan commented on YARN-2884: -- Thanks [~jianhe], have created YARN-4083. > P

[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-tabpanel&focusedCommentId=14712210#comment-14712210 ] Varun Saxena commented on YARN-3816: [~djp], thanks for the patch. Few comments and que

[jira] [Commented] (YARN-4083) Add a discovery mechanism for the scheduler addresss

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712206#comment-14712206 ] Subru Krishnan commented on YARN-4083: -- Based on the [discussion | https://issues.apa

[jira] [Updated] (YARN-4083) Add a discovery mechanism for the scheduler addresss

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4083: - Issue Type: Improvement (was: Sub-task) Parent: (was: YARN-2877) > Add a discovery mec

[jira] [Updated] (YARN-4083) Add a discovery mechanism for the scheduler addresss

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4083: - Description: Today many apps like Distributed Shell, REEF, etc rely on the fact that the HADOOP_CON

[jira] [Updated] (YARN-4083) Add a discovery mechanism for the scheduler addresss

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4083: - Description: (was: We introduce the notion of an RMProxy, running on each node (or once per rac

[jira] [Assigned] (YARN-4083) Add a discovery mechanism for the scheduler addresss

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan reassigned YARN-4083: Assignee: Subru Krishnan (was: Kishore Chaliparambil) > Add a discovery mechanism for the s

[jira] [Created] (YARN-4083) Add a discovery mechanism for the scheduler addresss

Subru Krishnan created YARN-4083: Summary: Add a discovery mechanism for the scheduler addresss Key: YARN-4083 URL: https://issues.apache.org/jira/browse/YARN-4083 Project: Hadoop YARN Issue

[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.1.patch Uploaded initial patch. > Container shouldn't be killed when node's label up

[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: - Component/s: (was: capacityscheduler) capacity scheduler > Container shouldn't be kill

[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: - Component/s: (was: api) (was: client) (was: resourcemanager)

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

Wangda Tan created YARN-4082: Summary: Container shouldn't be killed when node's label updated. Key: YARN-4082 URL: https://issues.apache.org/jira/browse/YARN-4082 Project: Hadoop YARN Issue Type

[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-tabpanel&focusedCommentId=14711987#comment-14711987 ] Jian He commented on YARN-2884: --- To make this move faster, I think we can have a separate jir

[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-tabpanel&focusedCommentId=14711941#comment-14711941 ] Hadoop QA commented on YARN-3717: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14711863#comment-14711863 ] Subru Krishnan commented on YARN-2884: -- Just to add more context based on the offline

[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-tabpanel&focusedCommentId=14711804#comment-14711804 ] Hadoop QA commented on YARN-4081: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14711766#comment-14711766 ] Subru Krishnan commented on YARN-2884: -- [~vinodkv], thanks for your feedback. Let me f

[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.20150825-1.patch Fixing following test case failures related to the pat

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

[ https://issues.apache.org/jira/browse/YARN-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711738#comment-14711738 ] Benoit Sigoure commented on YARN-3238: -- What's the setting to tune down to avoid the 4

[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-tabpanel&focusedCommentId=14711730#comment-14711730 ] Hadoop QA commented on YARN-3816: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14711711#comment-14711711 ] Vinod Kumar Vavilapalli commented on YARN-2884: --- [~jianhe] mentioned this off

[jira] [Commented] (YARN-3458) CPU resource monitoring in Windows

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

[jira] [Commented] (YARN-4061) [Fault tolerance] Fault tolerant writer for timeline v2

[ https://issues.apache.org/jira/browse/YARN-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711671#comment-14711671 ] Junping Du commented on YARN-4061: -- Thanks [~gtCarrera9] for working on a document for thi

[jira] [Updated] (YARN-3458) CPU resource monitoring in Windows

[ https://issues.apache.org/jira/browse/YARN-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Inigo Goiri updated YARN-3458: -- Attachment: YARN-3458-8.patch Rebase > CPU resource monitoring in Windows >

[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-tabpanel&focusedCommentId=14711652#comment-14711652 ] Varun Vasudev commented on YARN-4081: - [~leftnoteasy], [~asuresh], [~jianhe] - can you

[jira] [Commented] (YARN-3926) Extend the YARN resource model for easier resource-type management and profiles

[ https://issues.apache.org/jira/browse/YARN-3926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711651#comment-14711651 ] Varun Vasudev commented on YARN-3926: - I've created a YARN-3926 branch for this feature

[jira] [Updated] (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:all-tabpanel ] Varun Vasudev updated YARN-4081: Attachment: YARN-4081-YARN-3926.001.patch Uploaded a patch with support for multiple resource types i

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

Varun Vasudev created YARN-4081: --- Summary: Add support for multiple resource types in the Resource class Key: YARN-4081 URL: https://issues.apache.org/jira/browse/YARN-4081 Project: Hadoop YARN

[jira] [Updated] (YARN-4080) Capacity planning for long running services on YARN

[ https://issues.apache.org/jira/browse/YARN-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-4080: Description: YARN-1197 addresses the functionality of container resource resize. One major use case of this

[jira] [Commented] (YARN-2571) RM to support YARN registry

[ https://issues.apache.org/jira/browse/YARN-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711631#comment-14711631 ] Steve Loughran commented on YARN-2571: -- All the registry code is there (slider uses it

[jira] [Commented] (YARN-4080) Capacity planning for long running services on YARN

[ https://issues.apache.org/jira/browse/YARN-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711622#comment-14711622 ] MENG DING commented on YARN-4080: - Not sure if the title accurately reflects the problem. I

[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-tabpanel&focusedCommentId=14711592#comment-14711592 ] Junping Du commented on YARN-3816: -- bq. When we are doing sum operation, what if the value

[jira] [Updated] (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:all-tabpanel ] Junping Du updated YARN-3816: - Attachment: YARN-3816-YARN-2928-v1.patch Update PoC patch with following updates: - rebase patch according

[jira] [Created] (YARN-4080) Capacity planning for long running services on YARN

MENG DING created YARN-4080: --- Summary: Capacity planning for long running services on YARN Key: YARN-4080 URL: https://issues.apache.org/jira/browse/YARN-4080 Project: Hadoop YARN Issue Type: Impro

[jira] [Commented] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711464#comment-14711464 ] Varun Saxena commented on YARN-4079: Let us see what others think about how to handle t

[jira] [Commented] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711462#comment-14711462 ] Varun Saxena commented on YARN-4079: Hmm...I wasnt necessarily thinking of making it pu

[jira] [Commented] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711431#comment-14711431 ] Junping Du commented on YARN-4079: -- Thanks for filing this JIRA, [~varun_saxena]. bq. Prob

[jira] [Commented] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711414#comment-14711414 ] Varun Saxena commented on YARN-4079: This JIRA has been raised based on the discussion

[jira] [Commented] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711415#comment-14711415 ] Varun Saxena commented on YARN-4079: cc [~djp] > Retrospect on the decision of making

[jira] [Updated] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4079: --- Description: Currently in all daemons this config is explicitly set to true so that daemons can crash

[jira] [Created] (YARN-4079) Retrospect on making yarn.dispatcher.exit-on-error as explicitly true in daemons

Varun Saxena created YARN-4079: -- Summary: Retrospect on making yarn.dispatcher.exit-on-error as explicitly true in daemons Key: YARN-4079 URL: https://issues.apache.org/jira/browse/YARN-4079 Project: Had

[jira] [Updated] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as explicitly true in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4079: --- Summary: Retrospect on the decision of making yarn.dispatcher.exit-on-error as explicitly true in daemo

[jira] [Updated] (YARN-4079) Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemons

[ https://issues.apache.org/jira/browse/YARN-4079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4079: --- Summary: Retrospect on the decision of making yarn.dispatcher.exit-on-error as true explicitly in daemo

[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-tabpanel&focusedCommentId=14711290#comment-14711290 ] Varun Saxena commented on YARN-3893: Saw your comments above. We cant do what we were d

[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-tabpanel&focusedCommentId=14711278#comment-14711278 ] Varun Saxena commented on YARN-3893: In previous patches, we were delaying reinitializa

[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-tabpanel&focusedCommentId=14711274#comment-14711274 ] Varun Saxena commented on YARN-3893: Hmm...my point of view based on the fact that 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-tabpanel&focusedCommentId=14711201#comment-14711201 ] Rohith Sharma K S commented on YARN-3893: - There are 2 type of refresh can happen i

[jira] [Commented] (YARN-3011) NM dies because of the failure of resource localization

[ https://issues.apache.org/jira/browse/YARN-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711196#comment-14711196 ] Varun Saxena commented on YARN-3011: [~djp], the only thing which we can do here is tha

[jira] [Commented] (YARN-3011) NM dies because of the failure of resource localization

[ https://issues.apache.org/jira/browse/YARN-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711181#comment-14711181 ] Junping Du commented on YARN-3011: -- I see. Thanks Varun for reminding on this. "all daemon

[jira] [Resolved] (YARN-4013) Publisher V2 should write the unmanaged AM flag and application priority

[ https://issues.apache.org/jira/browse/YARN-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G resolved YARN-4013. --- Resolution: Won't Fix Already handled in YARN-4058 > Publisher V2 should write the unmanaged AM flag and appli

[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-tabpanel&focusedCommentId=14711171#comment-14711171 ] Varun Saxena commented on YARN-3893: Sorry I meant we can handle fail fast config being

[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-tabpanel&focusedCommentId=14711164#comment-14711164 ] Varun Saxena commented on YARN-3893: Moreover, the fail fast configuration doesnt quite

[jira] [Commented] (YARN-4044) Running applications information changes such as movequeue is not published to TimeLine server

[ https://issues.apache.org/jira/browse/YARN-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711147#comment-14711147 ] Sunil G commented on YARN-4044: --- Test case failures are not related. > Running applications

[jira] [Commented] (YARN-3933) Resources(both core and memory) are being negative

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711132#comment-14711132 ] Shiwei Guo commented on YARN-3933: -- I think so, and so is [YRAN-4045|https://issues.apach

[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-tabpanel&focusedCommentId=14711083#comment-14711083 ] Hadoop QA commented on YARN-3250: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[jira] [Commented] (YARN-3933) Resources(both core and memory) are being negative

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711056#comment-14711056 ] Lavkesh Lahngir commented on YARN-3933: --- Is it related to this ? https://issues.apach

[jira] [Commented] (YARN-3933) Resources(both core and memory) are being negative

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711051#comment-14711051 ] Shiwei Guo commented on YARN-3933: -- So I should better open a new issue instead? > Resour

[jira] [Commented] (YARN-3933) Resources(both core and memory) are being negative

[ https://issues.apache.org/jira/browse/YARN-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711050#comment-14711050 ] Shiwei Guo commented on YARN-3933: -- So I should better open a new issue instead? > Resour

[jira] [Commented] (YARN-2571) RM to support YARN registry

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

[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-tabpanel&focusedCommentId=14711036#comment-14711036 ] Varun Saxena commented on YARN-3893: Few additional comments : * Below exception block

[jira] [Commented] (YARN-4078) Unchecked typecast to AbstractYarnScheduler in AppInfo

[ https://issues.apache.org/jira/browse/YARN-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711024#comment-14711024 ] Naganarasimha G R commented on YARN-4078: - Yes [~rohithsharma] & [~varun_saxena],

[jira] [Commented] (YARN-4044) Running applications information changes such as movequeue is not published to TimeLine server

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

[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-tabpanel&focusedCommentId=14710955#comment-14710955 ] Rohith Sharma K S commented on YARN-3893: - To be more clear on the 3rd point, {{han

[jira] [Commented] (YARN-2571) RM to support YARN registry

[ https://issues.apache.org/jira/browse/YARN-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710946#comment-14710946 ] Srikanth Sampath commented on YARN-2571: What's the status of this patch - [~ste...

[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-tabpanel&focusedCommentId=14710942#comment-14710942 ] Rohith Sharma K S commented on YARN-3893: - Thanks [~bibinchundatt] for updating the

[jira] [Commented] (YARN-3972) Work Preserving AM Restart for MapReduce

[ https://issues.apache.org/jira/browse/YARN-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710927#comment-14710927 ] Srikanth Sampath commented on YARN-3972: Upon discussing with [~vvasudev] exploring

[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-tabpanel&focusedCommentId=14710853#comment-14710853 ] Rohith Sharma K S commented on YARN-3250: - Updated the patch fixing review comments

[jira] [Updated] (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:all-tabpanel ] Rohith Sharma K S updated YARN-3250: Attachment: 0003-YARN-3250.patch > Support admin cli interface in for Application Priority >

[jira] [Commented] (YARN-3874) Optimize and synchronize FS Reader and Writer Implementations

[ https://issues.apache.org/jira/browse/YARN-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710850#comment-14710850 ] Varun Saxena commented on YARN-3874: [~sjlee0], [~djp], although not urgent but eventua

[jira] [Commented] (YARN-4014) Support user cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710765#comment-14710765 ] Hudson commented on YARN-4014: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #294 (See [htt

[jira] [Commented] (YARN-4014) Support user cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710760#comment-14710760 ] Hudson commented on YARN-4014: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2251 (See [htt

[jira] [Commented] (YARN-4014) Support user cli interface in for Application Priority

[ https://issues.apache.org/jira/browse/YARN-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710758#comment-14710758 ] Hudson commented on YARN-4014: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2232 (See [https://