[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.3.patch Update patch to v2.3 to fix findbugs issues. > [Aggregation]

[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=14729204#comment-14729204 ] Hudson commented on YARN-3970: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2267 (See

[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=14729244#comment-14729244 ] Sunil G commented on YARN-4108: --- Adding to the locality preemption improvement suggestion from [~jlowe]

[jira] [Created] (YARN-4112) YARN HA secondary-RM/NM redirect not parseable by Ambari/curl in a Kerberoized deployment

Andrew Robertson created YARN-4112: -- Summary: YARN HA secondary-RM/NM redirect not parseable by Ambari/curl in a Kerberoized deployment Key: YARN-4112 URL: https://issues.apache.org/jira/browse/YARN-4112

[jira] [Commented] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729078#comment-14729078 ] nijel commented on YARN-4110: - Sorry attached wrong patch so deleting the same > RMappImpl and

[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=14729169#comment-14729169 ] Hudson commented on YARN-3970: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #329 (See

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

[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.003.patch {quote} 1) Uses String instead of URI for resource key? I

[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=14729119#comment-14729119 ] Sunil G commented on YARN-2005: --- Hi [~adhoot] Thank you for updating the patch. I have a comment here.

[jira] [Updated] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-4110: Attachment: (was: 01-YARN-4110.patch) > RMappImpl and RmAppAttemptImpl should override hashcode() & equals() >

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

[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=14729100#comment-14729100 ] Jason Lowe commented on YARN-4108: -- For the case where we are preempting containers but the other

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

[jira] [Commented] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

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

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

[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=14729127#comment-14729127 ] Varun Saxena commented on YARN-3816: [~djp], bq. Which issue you are raising? I can take a look as

[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=14729155#comment-14729155 ] Junping Du commented on YARN-3816: -- I see. Will keep watching on this JIRA and make sure it active and get

[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=14729422#comment-14729422 ] Anubhav Dhoot commented on YARN-4087: - In general if we are not failing the daemon if fail fast flag is

[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=14729435#comment-14729435 ] Xuan Gong commented on YARN-4107: - bq. Is this when using ZKRMStateStore? If yes, the store should take

[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=14729436#comment-14729436 ] Xuan Gong commented on YARN-4107: - bq. Is it caused by network split brain ? We did it on purpose. Using

[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.004.patch Uploaded a new patch to address the findbugs and

[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=14729503#comment-14729503 ] Jonathan Eagles commented on YARN-4103: --- You can do it if you like. Please ensure it makes it into

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

[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=14729556#comment-14729556 ] Sangjin Lee commented on YARN-4074: --- Just to be clear, the current POC patch already handles the null

[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=14729511#comment-14729511 ] Vrushali C commented on YARN-3901: -- Thanks [~gtCarrera9] for the review. Let me try to give some

[jira] [Updated] (YARN-3641) NodeManager: stopRecoveryStore() shouldn't be skipped when exceptions happen in stopping NM's sub-services.

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

[jira] [Updated] (YARN-3526) ApplicationMaster tracking URL is incorrectly redirected on a QJM cluster

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

[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=14729515#comment-14729515 ] Varun Saxena commented on YARN-4074: The 2nd point I guess even I can handle even in YARN-4075. I can

[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=14729558#comment-14729558 ] Varun Saxena commented on YARN-4074: [~sjlee0], yeah it handles null case. I meant we can handle

[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=14729560#comment-14729560 ] Varun Saxena commented on YARN-4074: Its fine though if you are handling negatives as part of

[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=14729561#comment-14729561 ] Varun Vasudev commented on YARN-4103: - Sounds good. I'll commit it tomorrow morning IST. > RM

[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=14729444#comment-14729444 ] Naganarasimha G R commented on YARN-4044: - [~sunilg], As per the offline discussion we had,

[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=14729389#comment-14729389 ] Varun Vasudev commented on YARN-4103: - +1 for the latest patch. Will you go ahead and commit it or

[jira] [Commented] (YARN-4102) Add a "skip existing table" mode for timeline schema creator

[ https://issues.apache.org/jira/browse/YARN-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729390#comment-14729390 ] Joep Rottinghuis commented on YARN-4102: Yup that looks good. I noticed one more thing, you decide

[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=14729308#comment-14729308 ] Jason Lowe commented on YARN-4059: -- bq. do you think if it acceptable to you if adding an option to CS

[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=14729331#comment-14729331 ] Li Lu commented on YARN-3874: - bq. For fallback from HBase when HBase cluster is temporary unavailable.

[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=14729378#comment-14729378 ] Jonathan Eagles commented on YARN-4103: --- Looks like YARN-1553 introduced this error. You can see that

[jira] [Commented] (YARN-4112) YARN HA secondary-RM/NM redirect not parseable by Ambari/curl in a Kerberoized deployment

[ https://issues.apache.org/jira/browse/YARN-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729404#comment-14729404 ] Xuan Gong commented on YARN-4112: - [~arobertson] Looks like duplicate with

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

[jira] [Updated] (YARN-4102) Add a "skip existing table" 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.003.patch Nice catch [~jrottinghuis]! Fixed in the v3 patch. Thanks for your help!

[jira] [Updated] (YARN-2766) ApplicationHistoryManager is expected to return a sorted list of apps/attempts/containers

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

[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=14729749#comment-14729749 ] Wangda Tan commented on YARN-4059: -- [~jlowe], thanks for your comments: bq. Wondering if we should scale

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729815#comment-14729815 ] Hitesh Shah commented on YARN-3942: --- Some ideas from an offline discussion with [~bikassaha] and

[jira] [Updated] (YARN-3700) ATS Web Performance issue at load time when large number of jobs

[ https://issues.apache.org/jira/browse/YARN-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3700: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1. Had to fix merge conflicts in

[jira] [Created] (YARN-4113) RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER

Wangda Tan created YARN-4113: Summary: RM should respect retry-interval when uses RetryPolicies.RETRY_FOREVER Key: YARN-4113 URL: https://issues.apache.org/jira/browse/YARN-4113 Project: Hadoop YARN

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

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

[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=14729886#comment-14729886 ] Vrushali C commented on YARN-3901: -- bq. From the code I can see we add the newly created cell to the list

[jira] [Updated] (YARN-3725) App submission via REST API is broken in secure mode due to Timeline DT service address is empty

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

[jira] [Updated] (YARN-3725) App submission via REST API is broken in secure mode due to Timeline DT service address is empty

[ https://issues.apache.org/jira/browse/YARN-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3725: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1 after fixing a few merge issues.

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729843#comment-14729843 ] Jason Lowe commented on YARN-3942: -- Option 1 will add some latency (not clear how much yet) to

[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=14729706#comment-14729706 ] MENG DING commented on YARN-1651: - Hi, [~leftnoteasy] I think it is fine to reuse Expire for now for

[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=14729798#comment-14729798 ] Jason Lowe commented on YARN-4059: -- bq. I think this cannot handle the case if an app wants only a small

[jira] [Assigned] (YARN-4109) Exception on RM scheduler page loading with labels

[ https://issues.apache.org/jira/browse/YARN-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammad Shahid Khan reassigned YARN-4109: -- Assignee: Mohammad Shahid Khan > Exception on RM scheduler page loading with

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

[jira] [Commented] (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:comment-tabpanel=14728555#comment-14728555 ] zhihai xu commented on YARN-2170: - Hi [~hex108], It is a good catch. Java doesn't allow overriding of

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

[jira] [Created] (YARN-4109) Exception on RM scheduler page loading with labels

Bibin A Chundatt created YARN-4109: -- Summary: Exception on RM scheduler page loading with labels Key: YARN-4109 URL: https://issues.apache.org/jira/browse/YARN-4109 Project: Hadoop YARN

[jira] [Updated] (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:all-tabpanel ] Lavkesh Lahngir updated YARN-3591: -- Attachment: YARN-3591.9.patch Thanks [~vvasudev] for comments. Updated the patch. > Resource

[jira] [Updated] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3216: --- Priority: Critical (was: Major) > Max-AM-Resource-Percentage should respect node labels >

[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=14728639#comment-14728639 ] Naganarasimha G R commented on YARN-4044: - Hi [~sunilg], IIUC intention of this jira is to show in

[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=14728743#comment-14728743 ] Varun Vasudev commented on YARN-4103: - Thanks for the patch [~jeagles]. Can you clarify something -

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728656#comment-14728656 ] Naganarasimha G R commented on YARN-3216: - Hi [~sunilg] & [~leftnoteasy], This issue is very

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728663#comment-14728663 ] Sunil G commented on YARN-3216: --- hi [~Naganarasimha Garla] Option2 may come with more complexity and user may

[jira] [Created] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

Rohith Sharma K S created YARN-4110: --- Summary: RMappImpl and RmAppAttemptImpl should override hashcode() & equals() Key: YARN-4110 URL: https://issues.apache.org/jira/browse/YARN-4110 Project:

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728858#comment-14728858 ] Naganarasimha G R commented on YARN-3813: - Hi All \[

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

[ https://issues.apache.org/jira/browse/YARN-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4029: --- Attachment: 0003-YARN-4029.patch Updated testcase for store updation. > Update

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728772#comment-14728772 ] Naganarasimha G R commented on YARN-3216: - Hi [~sunilg], Ideal would have been that

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728790#comment-14728790 ] Sunil G commented on YARN-3216: --- Synced up with [~Naganarasimha Garla] offline. One of the concern with

[jira] [Commented] (YARN-261) Ability to kill AM attempts

[ https://issues.apache.org/jira/browse/YARN-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728827#comment-14728827 ] Rohith Sharma K S commented on YARN-261: We have requirement for killing the app attempts. It would

[jira] [Assigned] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel reassigned YARN-3813: --- Assignee: nijel > Support Application timeout feature in YARN. >

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

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

[jira] [Updated] (YARN-4036) Findbugs warnings in hadoop-yarn-server-common

[ https://issues.apache.org/jira/browse/YARN-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-4036: Attachment: findbugsHtml.html Attaching the findbugs report generated locally. > Findbugs warnings

[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=14728876#comment-14728876 ] Hudson commented on YARN-3970: -- FAILURE: Integrated in Hadoop-trunk-Commit #8394 (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=14728885#comment-14728885 ] Hudson commented on YARN-3970: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #339 (See

[jira] [Updated] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nijel updated YARN-3813: Attachment: 0001-YARN-3813.patch Sorry for the long delay.. Adding an initial patch. The action on timeout is

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728911#comment-14728911 ] Sunil G commented on YARN-3813: --- As I see this, the trigger point to identify an application to be Timedout

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728917#comment-14728917 ] Naganarasimha G R commented on YARN-3813: - True, your point is correct so basically it should fail

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728918#comment-14728918 ] Naganarasimha G R commented on YARN-3813: - True, your point is correct so basically it should fail

[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=14728938#comment-14728938 ] Sunil G commented on YARN-4044: --- Thank You [~Naganarasimha] for sharing the comments.

[jira] [Commented] (YARN-3813) Support Application timeout feature in YARN.

[ https://issues.apache.org/jira/browse/YARN-3813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14728898#comment-14728898 ] nijel commented on YARN-3813: - This patch will address the initial issue. But this will kill the application

[jira] [Created] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

Rohith Sharma K S created YARN-4111: --- Summary: Killed application diagnostics message should be set rather having static mesage Key: YARN-4111 URL: https://issues.apache.org/jira/browse/YARN-4111

[jira] [Assigned] (YARN-4111) Killed application diagnostics message should be set rather having static mesage

[ https://issues.apache.org/jira/browse/YARN-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-4111: --- Assignee: nijel (was: Rohith Sharma K S) > Killed application diagnostics message

[jira] [Assigned] (YARN-4110) RMappImpl and RmAppAttemptImpl should override hashcode() & equals()

[ https://issues.apache.org/jira/browse/YARN-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S reassigned YARN-4110: --- Assignee: nijel (was: Rohith Sharma K S) > RMappImpl and RmAppAttemptImpl should

[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=14728906#comment-14728906 ] Naganarasimha G R commented on YARN-3368: - Hi Well came across an issue while installing as per

[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=14728866#comment-14728866 ] Varun Vasudev commented on YARN-3970: - Committed to trunk and branch-2. Thanks [~Naganarasimha]! >

[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 ] Varun Vasudev updated YARN-3970: Fix Version/s: 2.8.0 > REST api support for Application Priority >

[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=14728900#comment-14728900 ] Hudson commented on YARN-3970: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #346 (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=14728909#comment-14728909 ] Naganarasimha G R commented on YARN-3970: - Thanks for review and commit [~vvasudev], [~sunilg] &

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

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

[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=14729890#comment-14729890 ] Li Lu commented on YARN-3901: - bq. Yes, in this code, we are only "reading" or returning back cells to the

[jira] [Commented] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729905#comment-14729905 ] Jian He commented on YARN-4087: --- Right, we should make sure the state is correct if the error is ignored.

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Description: Several fixes: 1. Set YARN_FAIL_FAST to be false by default, since this makes more sense in

[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=14729910#comment-14729910 ] Joep Rottinghuis commented on YARN-3901: Not sure if [~gtCarrera9] is asking what happens if we

[jira] [Commented] (YARN-3942) Timeline store to read events from HDFS

[ https://issues.apache.org/jira/browse/YARN-3942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14729917#comment-14729917 ] Bikas Saha commented on YARN-3942: -- In Option 1 the latency would be the time to read the entire session

[jira] [Commented] (YARN-4102) Add a "skip existing table" mode for timeline schema creator

[ https://issues.apache.org/jira/browse/YARN-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730086#comment-14730086 ] Joep Rottinghuis commented on YARN-4102: s/in/it > Add a "skip existing table" mode for timeline

[jira] [Updated] (YARN-4087) Followup fixes after YARN-2019 regarding RM behavior when state-store error occurs

[ https://issues.apache.org/jira/browse/YARN-4087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-4087: -- Description: Several fixes: 1. Set YARN_FAIL_FAST to be false by default, since this makes more sense in

[jira] [Updated] (YARN-3850) NM fails to read files from full disks which can lead to container logs being lost and other issues

[ https://issues.apache.org/jira/browse/YARN-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-3850: -- Fix Version/s: 2.6.1 Pulled this into 2.6.1 after fixing a minor conflict in

[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=14730060#comment-14730060 ] Wangda Tan commented on YARN-4108: -- Thanks [~jlowe]/[~sunilg] for sharing your thoughts! I think the

[jira] [Commented] (YARN-3216) Max-AM-Resource-Percentage should respect node labels

[ https://issues.apache.org/jira/browse/YARN-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14730073#comment-14730073 ] Wangda Tan commented on YARN-3216: -- Thanks for sharing your thoughts, [~sunilg], [~Naganarasimha].

[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=14729983#comment-14729983 ] Wangda Tan commented on YARN-4059: -- Hi [~jlowe], Thanks for explanation, now I can better understand why

  1   2   >