[jira] [Commented] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

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

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-3901: - Attachment: YARN-3901-YARN-2928.2.patch Attaching patch v2 that addresses review suggestions as well as

[jira] [Commented] (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:comment-tabpanel=14726986#comment-14726986 ] Steve Loughran commented on YARN-4101: -- breaks a test {code} java.lang.AssertionError: incorrect

[jira] [Commented] (YARN-4073) Unused ApplicationACLsManager in ContainerManagerImpl

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

[jira] [Updated] (YARN-4073) Unused ApplicationACLsManager in ContainerManagerImpl

[ https://issues.apache.org/jira/browse/YARN-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4073: Priority: Trivial (was: Minor) > Unused ApplicationACLsManager in ContainerManagerImpl >

[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=14727050#comment-14727050 ] Varun Saxena commented on YARN-3816: Ok... > [Aggregation] App-level Aggregation for YARN system

[jira] [Resolved] (YARN-3998) Add retry-times to let NM re-launch container when it fails to run

[ https://issues.apache.org/jira/browse/YARN-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong resolved YARN-3998. Resolution: Won't Fix > Add retry-times to let NM re-launch container when it fails to run >

[jira] [Assigned] (YARN-2170) Fix components' version information in the web page 'About the Cluster'

[ https://issues.apache.org/jira/browse/YARN-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong reassigned YARN-2170: -- Assignee: Jun Gong > Fix components' version information in the web page 'About the Cluster' >

[jira] [Commented] (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:comment-tabpanel=14726925#comment-14726925 ] Hadoop QA commented on YARN-4101: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (YARN-4073) Unused ApplicationACLsManager in ContainerManagerImpl

[ https://issues.apache.org/jira/browse/YARN-4073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727023#comment-14727023 ] Rohith Sharma K S commented on YARN-4073: - +1 lgtm.. committing.. > Unused ApplicationACLsManager

[jira] [Commented] (YARN-4073) Unused ApplicationACLsManager in ContainerManagerImpl

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

[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14726816#comment-14726816 ] Naganarasimha G R commented on YARN-4106: - Thanks for raising this issue [~bibinchundatt], This

[jira] [Updated] (YARN-3964) Support NodeLabelsProvider at Resource Manager side

[ https://issues.apache.org/jira/browse/YARN-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dian Fu updated YARN-3964: -- Attachment: YARN-3964.005.patch rebase the patch. > Support NodeLabelsProvider at Resource Manager side >

[jira] [Commented] (YARN-3863) Enhance filters in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727635#comment-14727635 ] Junping Du commented on YARN-3863: -- Copy my comments in YARN-4074 for TimelineReader API: "Actually, I

[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-tabpanel=14727641#comment-14727641 ] Varun Saxena commented on YARN-4053: bq. to use cell tag identify metrics value type In YARN-3816, by

[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.2.patch > [Aggregation] App-level Aggregation for YARN system metrics >

[jira] [Updated] (YARN-3901) Populate flow run data in the flow_run & flow activity tables

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3901: - Summary: Populate flow run data in the flow_run & flow activity tables (was: Populate flow run data in

[jira] [Updated] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.007.patch Attached patch makes a couple of changes. Instead of adding a new

[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=14727643#comment-14727643 ] Hadoop QA commented on YARN-3816: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[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: Attachment: YARN-4101.2.patch Fix the testcase failure > RM should print alert messages if Zookeeper and

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727698#comment-14727698 ] Varun Vasudev commented on YARN-3591: - Thanks for the latest patch Lavkesh! Couple of comments - 1.

[jira] [Commented] (YARN-4059) Preemption should delay assignments back to the preempted queue

[ https://issues.apache.org/jira/browse/YARN-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727502#comment-14727502 ] Chang Li commented on YARN-4059: All tests passed on my machine with my patch on. That failed test is not

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

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

[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 ] Jason Lowe updated YARN-4105: - Affects Version/s: 2.6.0 Target Version/s: 2.7.2 Component/s: capacityscheduler Thanks for

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

[ https://issues.apache.org/jira/browse/YARN-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3368: - Attachment: (was: YARN-3368.poc.1.patch) > Improve YARN web UI > --- > >

[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=14727573#comment-14727573 ] Hadoop QA commented on YARN-4103: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[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-tabpanel=14727620#comment-14727620 ] Junping Du commented on YARN-4053: -- Hi [~sjlee0] and all, sorry for coming late for this good discussion.

[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=14727692#comment-14727692 ] Junping Du commented on YARN-3816: -- Checkstyle issues are all unrelated to this patch. Findbugs warning

[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=14727719#comment-14727719 ] Junping Du commented on YARN-3874: -- Hi [~ozawa] and [~varun_saxena], thanks for asking me for ideas. In my

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

[ https://issues.apache.org/jira/browse/YARN-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3368: - Attachment: YARN-3368.poc.1.patch There's one typo in previous patch, it should be "ember serve" instead

[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727590#comment-14727590 ] Wangda Tan commented on YARN-4106: -- [~Naganarasimha], I think do the sync on periodic intervals seems

[jira] [Commented] (YARN-4059) Preemption should delay assignments back to the preempted queue

[ https://issues.apache.org/jira/browse/YARN-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727662#comment-14727662 ] Jason Lowe commented on YARN-4059: -- Thanks for the patch, Chang! I'm wondering if this delay is the right

[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=14727683#comment-14727683 ] MENG DING commented on YARN-1651: - I think that should work. We probably need to make sure to properly log

[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.3.patch > Capacity Scheduler headroom for DRF is wrong >

[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=14727637#comment-14727637 ] Hadoop QA commented on YARN-3816: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[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=14727686#comment-14727686 ] Wangda Tan commented on YARN-1651: -- [~mding], that's make sense, maybe we need to put these roll back

[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727678#comment-14727678 ] Naganarasimha G R commented on YARN-4106: - Thanks for the thoughts [~leftnoteasy], Initially we

[jira] [Updated] (YARN-3901) Populate flow run data in the flow_run & flow activity tables

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3901: - Attachment: YARN-3901-YARN-2928.3.patch Thanks [~varun_saxena], looks like the patch was missing 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=14727613#comment-14727613 ] Wangda Tan commented on YARN-1651: -- [~mding], I think for your last example, if RM decides to rollback

[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=14727640#comment-14727640 ] Varun Vasudev commented on YARN-3970: - +1 for the latest patch. I'll commit this tomorrow if no one

[jira] [Commented] (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:comment-tabpanel=14727775#comment-14727775 ] Joep Rottinghuis commented on YARN-4102: Looks good to me. One caveat is in the naming. The

[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=14727837#comment-14727837 ] Sunil G commented on YARN-4044: --- Hi [~rohithsharma] Could you please take a look on this patch. > Running

[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.3.patch Addressing unit test failures in patch 3 > RM WebServices missing

[jira] [Commented] (YARN-4092) RM HA UI redirection needs to be fixed when both RMs are in standby mode

[ https://issues.apache.org/jira/browse/YARN-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727962#comment-14727962 ] Jonathan Eagles commented on YARN-4092: --- [~jianhe] [~xgong], this jira introduced a new findbugs

[jira] [Created] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

Wangda Tan created YARN-4108: Summary: CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request Key: YARN-4108 URL:

[jira] [Commented] (YARN-4059) Preemption should delay assignments back to the preempted queue

[ https://issues.apache.org/jira/browse/YARN-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728308#comment-14728308 ] Wangda Tan commented on YARN-4059: -- Thanks [~lichangleo]. I agree with [~jlowe], maybe we need to modify

[jira] [Commented] (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:comment-tabpanel=14728233#comment-14728233 ] Xuan Gong commented on YARN-4101: - The unit testcase failures are not related > RM should print alert

[jira] [Commented] (YARN-3769) Preemption occurring unnecessarily because preemption doesn't consider user limit

[ https://issues.apache.org/jira/browse/YARN-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728251#comment-14728251 ] Wangda Tan commented on YARN-3769: -- [~eepayne]. Thanks for working on the patch, the approach general

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728290#comment-14728290 ] Wangda Tan commented on YARN-4108: -- Choices to handle this issue: *Approach #1: Do some dry-runs before

[jira] [Updated] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4108: - Description: This is sibling JIRA for YARN-2154. We should make sure container preemption is more

[jira] [Updated] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2005: Attachment: YARN-2005.008.patch Addressed test failures caused because of missing appattempt data in

[jira] [Commented] (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:comment-tabpanel=14728301#comment-14728301 ] Hadoop QA commented on YARN-4101: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[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: YARN-1651-2.YARN-1197.patch Attached ver.2 patch, addressed most of [~mding]'s comments,

[jira] [Commented] (YARN-4108) CapacityScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

[ https://issues.apache.org/jira/browse/YARN-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728291#comment-14728291 ] Wangda Tan commented on YARN-4108: -- Linked this to YARN-2154. > CapacityScheduler: Improve preemption to

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

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728367#comment-14728367 ] Li Lu commented on YARN-3901: - Hi [~vrushalic], thanks for the work! I looked at the current patch and have

[jira] [Commented] (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:comment-tabpanel=14728405#comment-14728405 ] Hudson commented on YARN-4101: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #338 (See

[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=14728412#comment-14728412 ] Hadoop QA commented on YARN-4024: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (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:comment-tabpanel=14728462#comment-14728462 ] Hudson commented on YARN-4101: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #1074 (See

[jira] [Updated] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4106: --- Attachment: 0001-YARN-4106.patch > NodeLabels for NM in distributed mode is not updated even

[jira] [Commented] (YARN-4107) Both RM becomes Active if all zookeepers can not connect to active RM

[ https://issues.apache.org/jira/browse/YARN-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728424#comment-14728424 ] Rohith Sharma K S commented on YARN-4107: - Is it caused by network split brain ? > Both RM becomes

[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=14728495#comment-14728495 ] Hadoop QA commented on YARN-1651: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[jira] [Commented] (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:comment-tabpanel=14728526#comment-14728526 ] Hudson commented on YARN-4101: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2287 (See

[jira] [Updated] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM

[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4106: --- Attachment: 0002-YARN-4106.patch Hi [~leftnoteasy] & [~Naganarasimha] Thanks a lot for looking

[jira] [Commented] (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:comment-tabpanel=14728542#comment-14728542 ] Hudson commented on YARN-4101: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #328 (See

[jira] [Commented] (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:comment-tabpanel=14728478#comment-14728478 ] Hudson commented on YARN-4101: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2266 (See

[jira] [Commented] (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:comment-tabpanel=14728494#comment-14728494 ] Hudson commented on YARN-4101: -- SUCCESS: Integrated in Hadoop-Yarn-trunk-Java8 #345 (See

[jira] [Commented] (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:comment-tabpanel=14728389#comment-14728389 ] Hudson commented on YARN-4101: -- FAILURE: Integrated in Hadoop-trunk-Commit #8392 (See

[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=14728471#comment-14728471 ] Jonathan Eagles commented on YARN-4009: --- The general approach seems to be correct, allowing for

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

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

[jira] [Assigned] (YARN-3869) Add app name to RM audit log

[ https://issues.apache.org/jira/browse/YARN-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3869: --- Assignee: (was: nijel) Keeping it open for further comments and opinion > Add app name to RM audit log >

[jira] [Commented] (YARN-2953) TestWorkPreservingRMRestart fails on trunk

[ https://issues.apache.org/jira/browse/YARN-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728536#comment-14728536 ] Rohith Sharma K S commented on YARN-2953: - Verified the test , it has got fixed. We can close this.

[jira] [Commented] (YARN-4107) Both RM becomes Active if all zookeepers can not connect to active RM

[ https://issues.apache.org/jira/browse/YARN-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728544#comment-14728544 ] Karthik Kambatla commented on YARN-4107: Is this when using ZKRMStateStore? If yes, the store

[jira] [Resolved] (YARN-2953) TestWorkPreservingRMRestart fails on trunk

[ https://issues.apache.org/jira/browse/YARN-2953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S resolved YARN-2953. - Resolution: Invalid Assignee: (was: nijel) Closing as invalid >

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

[ https://issues.apache.org/jira/browse/YARN-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727761#comment-14727761 ] Srikanth Kandula commented on YARN-4088: True. a) Not sure if this (out-of-band heartbeat upon

[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-tabpanel=14727816#comment-14727816 ] Joep Rottinghuis commented on YARN-4053: Part of the issue is that there are many moving components

[jira] [Commented] (YARN-2410) Nodemanager ShuffleHandler can possible exhaust file descriptors

[ https://issues.apache.org/jira/browse/YARN-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14727927#comment-14727927 ] Kuhu Shukla commented on YARN-2410: --- Requesting [~nroberts] , [~jlowe] , [~jeagles] for their

[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=14727928#comment-14727928 ] Varun Saxena commented on YARN-3816: [~djp], bq. Findbugs warning doesn't hint anything. Actually

[jira] [Updated] (YARN-3493) RM fails to come up with error "Failed to load/recover state" when mem settings are changed

[ https://issues.apache.org/jira/browse/YARN-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3493: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Patch had minor conflicts , fixed

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

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

[jira] [Commented] (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:comment-tabpanel=14727912#comment-14727912 ] Hadoop QA commented on YARN-4101: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[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=14727959#comment-14727959 ] Wangda Tan commented on YARN-4024: -- Rekicked Jenkins, will commit once Jenkins get back. > YARN RM should

[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=14727746#comment-14727746 ] Varun Saxena commented on YARN-3874: bq. Do you have any solid scenarios and cases that need this

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

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

[jira] [Updated] (YARN-3487) CapacityScheduler scheduler lock obtained unnecessarily when calling getQueue

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

[jira] [Commented] (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:comment-tabpanel=14727780#comment-14727780 ] Hadoop QA commented on YARN-4102: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[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.002.patch Thanks [~jrottinghuis] for the review! In the second version I changed the

[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=14728082#comment-14728082 ] Hadoop QA commented on YARN-4103: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem

[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: Attachment: YARN-4101.3.patch fix a findbug issue introduced by YARN-4092 > RM should print alert messages

[jira] [Updated] (YARN-3024) LocalizerRunner should give DIE action when all resources are localized

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

[jira] [Updated] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3464: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Patch had 3 merge conflicts, fixed

[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.4.patch Thanks [~leftnoteasy] for review! Updated the test comment > Capacity Scheduler

[jira] [Commented] (YARN-4092) RM HA UI redirection needs to be fixed when both RMs are in standby mode

[ https://issues.apache.org/jira/browse/YARN-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728099#comment-14728099 ] Xuan Gong commented on YARN-4092: - Thanks, [~jeagles]. Will fix this findbug warning with YARN-4101 > RM

[jira] [Created] (YARN-4107) Both RM becomes Active if all zookeepers can not connect to active RM

Xuan Gong created YARN-4107: --- Summary: Both RM becomes Active if all zookeepers can not connect to active RM Key: YARN-4107 URL: https://issues.apache.org/jira/browse/YARN-4107 Project: Hadoop YARN

[jira] [Commented] (YARN-4107) Both RM becomes Active if all zookeepers can not connect to active RM

[ https://issues.apache.org/jira/browse/YARN-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728135#comment-14728135 ] Xuan Gong commented on YARN-4107: - The ActiveStandbyElector would go to enterNeutralMode if it lost

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

[ https://issues.apache.org/jira/browse/YARN-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728158#comment-14728158 ] Jason Lowe commented on YARN-4088: -- bq. Not sure if this (out-of-band heartbeat upon container completion)

[jira] [Updated] (YARN-3464) Race condition in LocalizerRunner kills localizer before localizing all resources

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3464: -- Attachment: YARN-3464-branch-2.6.1.txt Attaching the 2.6.1 patch that I

[jira] [Updated] (YARN-4107) Both RM becomes Active if all zookeepers can not connect to active RM

[ https://issues.apache.org/jira/browse/YARN-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-4107: Attachment: YARN-4107.1.patch > Both RM becomes Active if all zookeepers can not connect to active RM >

[jira] [Commented] (YARN-4107) Both RM becomes Active if all zookeepers can not connect to active RM

[ https://issues.apache.org/jira/browse/YARN-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728139#comment-14728139 ] Xuan Gong commented on YARN-4107: - create a patch to override enterNeutralMode() in EmbeddedElectorService

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

[ https://issues.apache.org/jira/browse/YARN-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728183#comment-14728183 ] Wangda Tan commented on YARN-4105: -- Patch LGTM too, thanks [~lichangleo]. Only one nit: could you update

[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=14728216#comment-14728216 ] Wangda Tan commented on YARN-4024: -- Strange test failures, rekicked Jenkins again.. > YARN RM should

  1   2   >