[jira] [Commented] (YARN-3368) Improve YARN web UI

[ https://issues.apache.org/jira/browse/YARN-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725753#comment-14725753 ] Wangda Tan commented on YARN-3368: -- [~kasha], My thought for this: we should include this in branch-2 to

[jira] [Commented] (YARN-3970) REST api support for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725822#comment-14725822 ] Naganarasimha G R commented on YARN-3970: - Seems like test case failure is not related to this

[jira] [Commented] (YARN-3970) REST api support for Application Priority

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

[jira] [Commented] (YARN-3368) Improve YARN web UI

[ https://issues.apache.org/jira/browse/YARN-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725779#comment-14725779 ] Vinod Kumar Vavilapalli commented on YARN-3368: --- bq. When the patch is ready, do we intend to

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725852#comment-14725852 ] Varun Saxena commented on YARN-3901: Yes, exactly the same exception. > Populate flow run data in the

[jira] [Commented] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

[ https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725861#comment-14725861 ] Wangda Tan commented on YARN-1651: -- Removed WIP patch since it is very close to .1 patch and may cause

[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-tabpanel=14725914#comment-14725914 ] Varun Saxena commented on YARN-4074: Few comments : # As TreeSet has been used to sort

[jira] [Commented] (YARN-4024) YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725830#comment-14725830 ] Anubhav Dhoot commented on YARN-4024: - LGTM. Thanks for removing those sleep > YARN RM should avoid

[jira] [Created] (YARN-4101) RM should print alert messages if Zookeeper and Resourcemanager gets connection issue

Yesha Vora created YARN-4101: Summary: RM should print alert messages if Zookeeper and Resourcemanager gets connection issue Key: YARN-4101 URL: https://issues.apache.org/jira/browse/YARN-4101 Project:

[jira] [Updated] (YARN-4101) RM should print alert messages if Zookeeper and Resourcemanager gets connection issue

[ https://issues.apache.org/jira/browse/YARN-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yesha Vora updated YARN-4101: - Issue Type: Improvement (was: Bug) > RM should print alert messages if Zookeeper and Resourcemanager gets

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725845#comment-14725845 ] Sangjin Lee commented on YARN-3901: --- Yeah, I can basically reproduce this issue too. What you said is

[jira] [Commented] (YARN-4009) CORS support for ResourceManager REST API

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

[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-tabpanel=14725729#comment-14725729 ] Anubhav Dhoot commented on YARN-3920: - [~asuresh] appreciate your review. > FairScheduler Reserving a

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725770#comment-14725770 ] Vrushali C commented on YARN-3901: -- Thanks for the update [~varun_saxena]. I will try this out in the

[jira] [Commented] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

[ https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725859#comment-14725859 ] Wangda Tan commented on YARN-1651: -- Hi [~mding], Thanks for reviewing patch, it's very helpful! *1)*

[jira] [Commented] (YARN-3368) Improve YARN web UI

[ https://issues.apache.org/jira/browse/YARN-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725879#comment-14725879 ] Wangda Tan commented on YARN-3368: -- bq. I think we should get this into trunk, even if at the beginning as

[jira] [Commented] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

[ https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726075#comment-14726075 ] MENG DING commented on YARN-1651: - Thanks [~leftnoteasy] for the explanation. bq. For the example 1, I

[jira] [Updated] (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:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3238: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Ran compilation before the push.

[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-tabpanel=14725918#comment-14725918 ] Varun Saxena commented on YARN-4074: Correction to point 1 : As TreeSet has been used to sort

[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-tabpanel=14725761#comment-14725761 ] Vinod Kumar Vavilapalli commented on YARN-4087: --- Yes, I just checked that YARN-2019 added the

[jira] [Updated] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

[ https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-1651: - Attachment: (was: YARN-1651-WIP.YARN-1197.patch) > CapacityScheduler side changes to support

[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-tabpanel=14724856#comment-14724856 ] Varun Saxena commented on YARN-4074: Agree...+1 to changing the name. > [timeline reader] implement

[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=14724855#comment-14724855 ] Naganarasimha G R commented on YARN-4078: - {{getApplicationAttempt}} is specific to

[jira] [Commented] (YARN-4093) Encapsulate additional group information in the AM to RM heartbeat

[ https://issues.apache.org/jira/browse/YARN-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724876#comment-14724876 ] Varun Vasudev commented on YARN-4093: - [~rgrandl] - I think there's a large overlap between this and

[jira] [Created] (YARN-4098) Document ApplicationPriority feature

Rohith Sharma K S created YARN-4098: --- Summary: Document ApplicationPriority feature Key: YARN-4098 URL: https://issues.apache.org/jira/browse/YARN-4098 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-3970) REST api support for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724897#comment-14724897 ] Naganarasimha G R commented on YARN-3970: - Thanks for the comments [~vvasudev], bq. It's useful to

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

[ https://issues.apache.org/jira/browse/YARN-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4083: - Summary: Add a discovery mechanism for the scheduler address (was: Add a discovery mechanism for

[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=14726476#comment-14726476 ] Junping Du commented on YARN-3816: -- Nice catch, [~gtCarrera9]! For now, YARN_APPLICATION_AGGREGATION is

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726498#comment-14726498 ] Hudson commented on YARN-3222: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2279 (See

[jira] [Commented] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

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

[jira] [Updated] (YARN-4104) dryrun of schedule for diagnostic and tenant's complain

[ https://issues.apache.org/jira/browse/YARN-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hong Zhiguo updated YARN-4104: -- Description: We have more than 1 thousand queues and several hundreds of tenants in a busy cluster. We

[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-v2.patch Update patch with addressing above comments. In addition, add

[jira] [Updated] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

[ https://issues.apache.org/jira/browse/YARN-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-4105: --- Attachment: YARN-4105.patch > Capacity Scheduler headroom for DRF is wrong >

[jira] [Created] (YARN-4105) Capacity Scheduler headroom for DRF is wrong

Chang Li created YARN-4105: -- Summary: Capacity Scheduler headroom for DRF is wrong Key: YARN-4105 URL: https://issues.apache.org/jira/browse/YARN-4105 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brook Zhou updated YARN-3223: - Attachment: (was: YARN-3223-v0.1.patch) > Resource update during NM graceful decommission >

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

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

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726378#comment-14726378 ] Hudson commented on YARN-3222: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #338 (See

[jira] [Created] (YARN-4104) dryrun of schedule for diagnostic and tenant's complain

Hong Zhiguo created YARN-4104: - Summary: dryrun of schedule for diagnostic and tenant's complain Key: YARN-4104 URL: https://issues.apache.org/jira/browse/YARN-4104 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-3446) FairScheduler HeadRoom calculation should exclude nodes in the blacklist.

[ https://issues.apache.org/jira/browse/YARN-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3446: Attachment: YARN-3446.001.patch > FairScheduler HeadRoom calculation should exclude nodes in the blacklist.

[jira] [Updated] (YARN-3369) Missing NullPointer check in AppSchedulingInfo causes RM to die

[ https://issues.apache.org/jira/browse/YARN-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3369: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Ran compilation before the push.

[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=14726489#comment-14726489 ] Li Lu commented on YARN-3816: - OK that makes sense. Let's proceed in this way. Thanks! > [Aggregation]

[jira] [Updated] (YARN-4104) dryrun of schedule for diagnostic and tenant's complain

[ https://issues.apache.org/jira/browse/YARN-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hong Zhiguo updated YARN-4104: -- Description: We have more than 1 thousand queues and several hundreds of tenants in a busy cluster. We

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3267: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1, the patch applied well except for a

[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=14726484#comment-14726484 ] Junping Du commented on YARN-3816: -- I think we can only support toAggregate so far. About flag of

[jira] [Updated] (YARN-3393) Getting application(s) goes wrong when app finishes before starting the attempt

[ https://issues.apache.org/jira/browse/YARN-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3393: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. The patch applied cleanly for the

[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=14726634#comment-14726634 ] Srikanth Sampath commented on YARN-2571: Thanks [~steve_l]. I will ping you directly. > RM to

[jira] [Commented] (YARN-4104) dryrun of schedule for diagnostic and tenant's complain

[ https://issues.apache.org/jira/browse/YARN-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726646#comment-14726646 ] Rohith Sharma K S commented on YARN-4104: - Thanks [~zhiguohong] for brining up the customer pain

[jira] [Updated] (YARN-4104) dryrun of schedule for diagnostic and tenant's complain

[ https://issues.apache.org/jira/browse/YARN-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4104: Issue Type: Sub-task (was: Improvement) Parent: YARN-4091 > dryrun of schedule for

[jira] [Commented] (YARN-3901) Populate flow run data in the flow_run table

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726090#comment-14726090 ] Vrushali C commented on YARN-3901: -- [~varun_saxena] and [~sjlee0] I see from the code that value is being

[jira] [Updated] (YARN-4102) Add an "incremental" mode for timeline schema creator

[ https://issues.apache.org/jira/browse/YARN-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-4102: Attachment: YARN-4102-YARN-2928.001.patch Instead of an "incremental" mode I added a "force" mode that will continue

[jira] [Updated] (YARN-3227) Timeline renew delegation token fails when RM user's TGT is expired

[ https://issues.apache.org/jira/browse/YARN-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3227: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Ran compilation before the push.

[jira] [Updated] (YARN-3230) Clarify application states on the web UI

[ https://issues.apache.org/jira/browse/YARN-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3230: -- Labels: 2.6.1-candidate (was: ) > Clarify application states on the web UI >

[jira] [Updated] (YARN-3249) Add a "kill application" button to Resource Manager's Web UI

[ https://issues.apache.org/jira/browse/YARN-3249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3249: -- Labels: 2.6.1-candidate (was: ) Fix Version/s: 2.6.1 Pulled this

[jira] [Created] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

Jonathan Eagles created YARN-4103: - Summary: RM WebServices missing scheme for appattempts logLinks Key: YARN-4103 URL: https://issues.apache.org/jira/browse/YARN-4103 Project: Hadoop YARN

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726371#comment-14726371 ] Hudson commented on YARN-3222: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1065 (See

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

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

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726377#comment-14726377 ] Hudson commented on YARN-3222: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #330 (See

[jira] [Created] (YARN-4102) Add an "incremental" mode for timeline schema creator

Li Lu created YARN-4102: --- Summary: Add an "incremental" mode for timeline schema creator Key: YARN-4102 URL: https://issues.apache.org/jira/browse/YARN-4102 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-3231) FairScheduler: Changing queueMaxRunningApps interferes with pending jobs

[ https://issues.apache.org/jira/browse/YARN-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3231: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Ran compilation and

[jira] [Updated] (YARN-3223) Resource update during NM graceful decommission

[ https://issues.apache.org/jira/browse/YARN-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brook Zhou updated YARN-3223: - Attachment: YARN-3223-v0.1.patch > Resource update during NM graceful decommission >

[jira] [Commented] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726230#comment-14726230 ] Wangda Tan commented on YARN-2801: -- Thanks [~ozawa] and [~Naganarasimha]! > Add documentation for node

[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=14726232#comment-14726232 ] Wangda Tan commented on YARN-4082: -- Thanks for review and commit from [~vvasudev]! > Container shouldn't

[jira] [Commented] (YARN-3368) Improve YARN web UI

[ https://issues.apache.org/jira/browse/YARN-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726290#comment-14726290 ] Karthik Kambatla commented on YARN-3368: If one could turn it off, I am comfortable pulling this

[jira] [Comment Edited] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726306#comment-14726306 ] Vinod Kumar Vavilapalli edited comment on YARN-1809 at 9/1/15 10:15 PM:

[jira] [Updated] (YARN-3239) WebAppProxy does not support a final tracking url which has query fragments and params

[ https://issues.apache.org/jira/browse/YARN-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3239: -- Fix Version/s: 2.6.1 Patch did not apply cleanly to 2.6.1. Had to fix minor

[jira] [Updated] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3222: -- Fix Version/s: 2.6.1 The original commit missed CHANGES.txt entries, added them.

[jira] [Updated] (YARN-3242) Asynchrony in ZK-close can lead to ZKRMStateStore watcher receiving events for old client

[ https://issues.apache.org/jira/browse/YARN-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3242: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Ran compilation and

[jira] [Updated] (YARN-4103) RM WebServices missing scheme for appattempts logLinks

[ https://issues.apache.org/jira/browse/YARN-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-4103: -- Attachment: YARN-4103.1.patch > RM WebServices missing scheme for appattempts logLinks >

[jira] [Updated] (YARN-3287) TimelineClient kerberos authentication failure uses wrong login context.

[ https://issues.apache.org/jira/browse/YARN-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3287: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Ran compilation and

[jira] [Updated] (YARN-4101) RM should print alert messages if Zookeeper and Resourcemanager gets connection issue

[ https://issues.apache.org/jira/browse/YARN-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4101: Issue Type: Sub-task (was: Improvement) Parent: YARN-149 > RM should print alert messages if

[jira] [Assigned] (YARN-4101) RM should print alert messages if Zookeeper and Resourcemanager gets connection issue

[ https://issues.apache.org/jira/browse/YARN-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-4101: --- Assignee: Xuan Gong > RM should print alert messages if Zookeeper and Resourcemanager gets >

[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

[ https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726216#comment-14726216 ] Hudson commented on YARN-3222: -- FAILURE: Integrated in Hadoop-trunk-Commit #8382 (See

[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-tabpanel=14726295#comment-14726295 ] Sangjin Lee commented on YARN-4074: --- I'm addressing [~varun_saxena]'s latest comments. Thanks for those.

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1809: -- Attachment: YARN-1809-2.6.1.txt Patch committed to 2.6.1. > Synchronize RM and

[jira] [Updated] (YARN-1809) Synchronize RM and Generic History Service Web-UIs

[ https://issues.apache.org/jira/browse/YARN-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1809: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Ran compilation and

[jira] [Commented] (YARN-3368) Improve YARN web UI

[ https://issues.apache.org/jira/browse/YARN-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726323#comment-14726323 ] Wangda Tan commented on YARN-3368: -- Thanks [~kasha]. > Improve YARN web UI > --- > >

[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-tabpanel=14726097#comment-14726097 ] Jian He commented on YARN-4087: --- bq. as there are no retries or explicit app-failures Retry already happened

[jira] [Updated] (YARN-3230) Clarify application states on the web UI

[ https://issues.apache.org/jira/browse/YARN-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3230: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1 as a dependency for YARN-1809. Ran

[jira] [Commented] (YARN-1651) CapacityScheduler side changes to support increase/decrease container resource.

[ https://issues.apache.org/jira/browse/YARN-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726303#comment-14726303 ] Wangda Tan commented on YARN-1651: -- bq. In other words, the increase expiration logic must remember all

[jira] [Updated] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-2801: - Target Version/s: 2.8.0, 2.7.2 (was: 2.8.0) > Add documentation for node labels feature >

[jira] [Commented] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724999#comment-14724999 ] Tsuyoshi Ozawa commented on YARN-2801: -- +1, committing this shortly. > Add documentation for node

[jira] [Assigned] (YARN-4009) CORS support for ResourceManager REST API

[ https://issues.apache.org/jira/browse/YARN-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev reassigned YARN-4009: --- Assignee: Varun Vasudev > CORS support for ResourceManager REST API >

[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 ] Varun Vasudev updated YARN-4082: Fix Version/s: 2.8.0 > Container shouldn't be killed when node's label updated. >

[jira] [Created] (YARN-4100) Add Documentation for Distributed Node Labels feature

Naganarasimha G R created YARN-4100: --- Summary: Add Documentation for Distributed Node Labels feature Key: YARN-4100 URL: https://issues.apache.org/jira/browse/YARN-4100 Project: Hadoop YARN

[jira] [Created] (YARN-4099) Container LocalizedResource more than 10min was kill

tangshangwen created YARN-4099: -- Summary: Container LocalizedResource more than 10min was kill Key: YARN-4099 URL: https://issues.apache.org/jira/browse/YARN-4099 Project: Hadoop YARN Issue

[jira] [Updated] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsuyoshi Ozawa updated YARN-2801: - Summary: Add documentation for node labels feature (was: Documentation development for Node

[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=14725000#comment-14725000 ] Varun Vasudev commented on YARN-4082: - +1. Committed to trunk and branch-2. Thanks [~leftnoteasy]! >

[jira] [Commented] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725017#comment-14725017 ] Hudson commented on YARN-2801: -- FAILURE: Integrated in Hadoop-trunk-Commit #8378 (See

[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=14725016#comment-14725016 ] Hudson commented on YARN-4082: -- FAILURE: Integrated in Hadoop-trunk-Commit #8378 (See

[jira] [Commented] (YARN-3970) REST api support for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724930#comment-14724930 ] Varun Vasudev commented on YARN-3970: - bq. It would be good to know the scenario too, IMHO the

[jira] [Commented] (YARN-4099) Container LocalizedResource more than 10min was kill

[ https://issues.apache.org/jira/browse/YARN-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14724949#comment-14724949 ] tangshangwen commented on YARN-4099: 2015-08-28 15:10:37,434 INFO

[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=14725027#comment-14725027 ] Hudson commented on YARN-4082: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1060 (See

[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=14725091#comment-14725091 ] Hudson commented on YARN-4082: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #334 (See

[jira] [Commented] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725092#comment-14725092 ] Hudson commented on YARN-2801: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #334 (See

[jira] [Updated] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4034: Attachment: YARN-4034.PNG > Render cluster Max Priority in scheduler metrics in RM web UI >

[jira] [Updated] (YARN-3970) REST api support for Application Priority

[ https://issues.apache.org/jira/browse/YARN-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3970: Attachment: YARN-3970.20150901-1.patch Thanks [~vvasudev] & [~sunilg], I have updated a new

[jira] [Updated] (YARN-4034) Render cluster Max Priority in scheduler metrics in RM web UI

[ https://issues.apache.org/jira/browse/YARN-4034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4034: Attachment: 0001-YARN-4034.patch > Render cluster Max Priority in scheduler metrics in RM

[jira] [Commented] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725217#comment-14725217 ] Hudson commented on YARN-2801: -- FAILURE: Integrated in Hadoop-Yarn-trunk #1061 (See

[jira] [Commented] (YARN-2801) Add documentation for node labels feature

[ https://issues.apache.org/jira/browse/YARN-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14725283#comment-14725283 ] Hudson commented on YARN-2801: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2275 (See

[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=14725281#comment-14725281 ] Hudson commented on YARN-4082: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #2275 (See

  1   2   >