[jira] [Commented] (YARN-4062) Add the flush and compaction functionality via coprocessors and scanners for flow run table

[ https://issues.apache.org/jira/browse/YARN-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791625#comment-14791625 ] Vrushali C commented on YARN-4062: -- No, we do use it in ColumnHelper#getPutTimestamp to be able to get the

[jira] [Assigned] (YARN-4174) Fix javadoc warnings floating up from hbase

[ https://issues.apache.org/jira/browse/YARN-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee reassigned YARN-4174: - Assignee: Sangjin Lee > Fix javadoc warnings floating up from hbase >

[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.10.patch Thanks [~sjlee0] for the javadoc warnings fix. I have included it

[jira] [Updated] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4000: --- Attachment: (was: YARN-4000.03.patch) > RM crashes with NPE if leaf queue becomes parent queue

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

[jira] [Commented] (YARN-1897) CLI and core support for signal container functionality

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

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM every x interval for distributed nodelabels

[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791704#comment-14791704 ] Naganarasimha G R commented on YARN-4176: - Hi [~bibinchundatt], Seems like this would be a better

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

[jira] [Created] (YARN-4177) yarn.util.Clock should not be used to time a duration or time interval

Xianyin Xin created YARN-4177: - Summary: yarn.util.Clock should not be used to time a duration or time interval Key: YARN-4177 URL: https://issues.apache.org/jira/browse/YARN-4177 Project: Hadoop YARN

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

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791775#comment-14791775 ] Varun Saxena commented on YARN-3816: [~djp], {quote} In TimelineMetric#accumulateTo, can latestMetric

[jira] [Updated] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4000: --- Attachment: YARN-4000.03.patch > RM crashes with NPE if leaf queue becomes parent queue during restart

[jira] [Updated] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4000: --- Attachment: YARN-4000.03.patch > RM crashes with NPE if leaf queue becomes parent queue during restart

[jira] [Updated] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4000: --- Attachment: YARN-4000.03.patch > RM crashes with NPE if leaf queue becomes parent queue during restart

[jira] [Updated] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4000: --- Attachment: (was: YARN-4000.03.patch) > RM crashes with NPE if leaf queue becomes parent queue

[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=14791626#comment-14791626 ] Vrushali C commented on YARN-3901: -- Thanks [~jrottinghuis], it is quite exciting to work on hbase cell

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

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM every x interval for distributed nodelabels

[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14791827#comment-14791827 ] Bibin A Chundatt commented on YARN-4176: Hi [~Naganarasimha] Thnks for the comments. {quote} I

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802698#comment-14802698 ] Jian He commented on YARN-4000: --- - is this if condition a typo ? {code} if

[jira] [Comment Edited] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802698#comment-14802698 ] Jian He edited comment on YARN-4000 at 9/17/15 10:04 AM: - - is this if condition a

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

[jira] [Updated] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4000: --- Attachment: YARN-4000.04.patch > RM crashes with NPE if leaf queue becomes parent queue during restart

[jira] [Commented] (YARN-4171) Resolve findbugs/javac warnings in YARN-1197 branch

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

[jira] [Commented] (YARN-4155) TestLogAggregationService.testLogAggregationServiceWithInterval failing

[ https://issues.apache.org/jira/browse/YARN-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802731#comment-14802731 ] Bibin A Chundatt commented on YARN-4155: Hi [~ste...@apache.org] Could you please review patch

[jira] [Commented] (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:comment-tabpanel=14802739#comment-14802739 ] Hudson commented on YARN-4034: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #2322 (See

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802738#comment-14802738 ] Varun Saxena commented on YARN-4000: bq. is this if condition a typo ? Yes. Had updated wrong patch.

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

[jira] [Commented] (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:comment-tabpanel=14791805#comment-14791805 ] Hudson commented on YARN-4034: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #407 (See

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

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

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM every x interval for distributed nodelabels

[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802688#comment-14802688 ] Steve Loughran commented on YARN-4176: -- I no longer trust nanoTime(). I'll do a blog post on it, but

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

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802848#comment-14802848 ] Varun Saxena commented on YARN-3816: I mean for TIME_SERIES we can take value associated with latest

[jira] [Updated] (YARN-4177) yarn.util.Clock should not be used to time a duration or time interval

[ https://issues.apache.org/jira/browse/YARN-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-4177: -- Attachment: YARN-4177.001.patch Provide a MonotonicClock. > yarn.util.Clock should not be used to time

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803122#comment-14803122 ] MENG DING commented on YARN-4138: - There is an issue with the current logic:

[jira] [Updated] (YARN-4066) Large number of queues choke fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4066: --- Assignee: Johan Gustavsson > Large number of queues choke fair scheduler >

[jira] [Commented] (YARN-4176) Resync NM nodelabels with RM every x interval for distributed nodelabels

[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802943#comment-14802943 ] Naganarasimha G R commented on YARN-4176: - [~ste...@apache.org], Thanks for the comments, but

[jira] [Commented] (YARN-4160) Dynamic NM Resources Configuration file should be simplified.

[ https://issues.apache.org/jira/browse/YARN-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803112#comment-14803112 ] Junping Du commented on YARN-4160: -- The proposed new configuration is as following: {noformat}      

[jira] [Commented] (YARN-4066) Large number of queues choke fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803151#comment-14803151 ] Karthik Kambatla commented on YARN-4066: Thanks again for working on this, Johan. Took a closer

[jira] [Commented] (YARN-4066) Large number of queues choke fair scheduler

[ https://issues.apache.org/jira/browse/YARN-4066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803119#comment-14803119 ] Karthik Kambatla commented on YARN-4066: Looking into it. > Large number of queues choke fair

[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=14803137#comment-14803137 ] Junping Du commented on YARN-3901: -- Patch LGTM too. Looks like Jenkins doesn't be triggered against v10

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

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

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803190#comment-14803190 ] Hadoop QA commented on YARN-4141: - \\ \\ | (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=14803109#comment-14803109 ] Sangjin Lee commented on YARN-3901: --- The latest patch (v.10) LGTM. Thanks much [~vrushalic] for the

[jira] [Commented] (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:comment-tabpanel=14803100#comment-14803100 ] Karthik Kambatla commented on YARN-3446: Thanks for rebasing the patch, [~zxu]. Comments:

[jira] [Commented] (YARN-4177) yarn.util.Clock should not be used to time a duration or time interval

[ https://issues.apache.org/jira/browse/YARN-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802911#comment-14802911 ] Xianyin Xin commented on YARN-4177: --- In a following steps I would try to fix several important places

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

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

[jira] [Updated] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4141: -- Attachment: 0005-YARN-4141.patch Thank you [~jlowe]. Yes, its a good optimization. Updating a patch based on

[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=14802894#comment-14802894 ] Varun Vasudev commented on YARN-4009: - bq. What happens when both of these are enabled at the same time

[jira] [Commented] (YARN-1897) CLI and core support for signal container functionality

[ https://issues.apache.org/jira/browse/YARN-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803039#comment-14803039 ] Junping Du commented on YARN-1897: -- Thanks [~mingma] for replying the comments. bq. Yes, the approach

[jira] [Commented] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

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

[jira] [Updated] (YARN-3816) [Aggregation] App-level aggregation and accumulation 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-v3.1.patch Fix checkstyle issue (3 of 4, the last one shouldn't be fixed)

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

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

[jira] [Updated] (YARN-4000) RM crashes with NPE if leaf queue becomes parent queue during restart

[ https://issues.apache.org/jira/browse/YARN-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-4000: --- Attachment: YARN-4000.05.patch > RM crashes with NPE if leaf queue becomes parent queue during restart

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

[ https://issues.apache.org/jira/browse/YARN-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14802898#comment-14802898 ] Junping Du commented on YARN-3816: -- bq. This is more from the context of caller. I am not sure if Li's

[jira] [Commented] (YARN-4170) AM need to be notified with priority in AllocateResponse

[ https://issues.apache.org/jira/browse/YARN-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803040#comment-14803040 ] Sunil G commented on YARN-4170: --- Adding the comment from

[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=14803213#comment-14803213 ] Li Lu commented on YARN-3901: - Patch LGTM. Pending Jenkins. > Populate flow run data in the flow_run & flow

[jira] [Updated] (YARN-4170) AM need to be notified with priority in AllocateResponse

[ https://issues.apache.org/jira/browse/YARN-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-4170: -- Attachment: 0001-YARN-4170.patch Uploading an initial version of patch. Kindly help to check the same. > AM

[jira] [Updated] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-4140: --- Attachment: 0005-YARN-4140.patch > RM container allocation delayed incase of app submitted to

[jira] [Commented] (YARN-914) (Umbrella) Support graceful decommission of nodemanager

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803230#comment-14803230 ] Parvez commented on YARN-914: - Hi, I am facing issues when trying to resize the AWS EMR cluster which is

[jira] [Resolved] (YARN-4174) Fix javadoc warnings floating up from hbase

[ https://issues.apache.org/jira/browse/YARN-4174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee resolved YARN-4174. --- Resolution: Done Fix Version/s: YARN-2928 This ended up getting fixed as part of YARN-3901. >

[jira] [Commented] (YARN-4141) Runtime Application Priority change should not throw exception for applications at finishing states

[ https://issues.apache.org/jira/browse/YARN-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803206#comment-14803206 ] Sunil G commented on YARN-4141: --- Test case failures are *not* related. TestRMRestart failed due to

[jira] [Commented] (YARN-3127) Avoid timeline events during RM recovery or restart

[ https://issues.apache.org/jira/browse/YARN-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803381#comment-14803381 ] Naganarasimha G R commented on YARN-3127: - Hi [~xgong]/ [~ozawa], I feel the issue is valid and

[jira] [Created] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

Sangjin Lee created YARN-4178: - Summary: [storage implementation] app id as string can cause incorrect ordering Key: YARN-4178 URL: https://issues.apache.org/jira/browse/YARN-4178 Project: Hadoop YARN

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803201#comment-14803201 ] Sunil G commented on YARN-4138: --- HI [~mding] In the same case, if we 2 incremental requests, like 2G --> 4G

[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=14803384#comment-14803384 ] Sangjin Lee commented on YARN-4074: --- {quote} In TimelineEntityReader#readMetrics it seems safe to assume

[jira] [Created] (YARN-4179) [reader implementation] support flow activity queries based on time

Sangjin Lee created YARN-4179: - Summary: [reader implementation] support flow activity queries based on time Key: YARN-4179 URL: https://issues.apache.org/jira/browse/YARN-4179 Project: Hadoop YARN

[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=14803240#comment-14803240 ] Sangjin Lee commented on YARN-3901: --- Jenkins does kick in but for some reason, it cannot post the result

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

[ https://issues.apache.org/jira/browse/YARN-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803398#comment-14803398 ] Bibin A Chundatt commented on YARN-4140: Thanks [~leftnoteasy] for review and comments. > RM

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

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4074: -- Attachment: YARN-4074-YARN-2928.007.patch v.7 patch posted. This is now based on the YARN-2928 branch

[jira] [Commented] (YARN-2597) MiniYARNCluster doesn't propagate reason for AHS not starting

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

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

[jira] [Assigned] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-4178: -- Assignee: Varun Saxena > [storage implementation] app id as string can cause incorrect ordering

[jira] [Commented] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

[ https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804344#comment-14804344 ] Anubhav Dhoot commented on YARN-4143: - I think we can minimize the impact of checking on every allocate

[jira] [Updated] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

[ https://issues.apache.org/jira/browse/YARN-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4143: Attachment: YARN-4143.001.patch Attached patch ensures checks are done only when AM is not allocated

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804423#comment-14804423 ] Vrushali C commented on YARN-4178: -- In hRaven, we started with storing hadoop job ids as a tuple of JT/RM

[jira] [Updated] (YARN-1897) CLI and core support for signal container functionality

[ https://issues.apache.org/jira/browse/YARN-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated YARN-1897: -- Attachment: YARN-1897-7.patch Thanks [~djp]! bq. Number of preempted containers won't be count as container

[jira] [Updated] (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:all-tabpanel ] Sunil G updated YARN-4044: -- Attachment: 0004-YARN-4044.patch Thank you Naga for the comments. Yes, for now we are setting all information's

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1480#comment-1480 ] Li Lu commented on YARN-4178: - We can rely on ApplicationId class in YARN api to fix this, right? As

[jira] [Commented] (YARN-4140) RM container allocation delayed incase of app submitted to Nodelabel partition

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

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804414#comment-14804414 ] Varun Saxena commented on YARN-4178: ApplicationId is basically a combination of cluster timestamp and

[jira] [Commented] (YARN-4178) [storage implementation] app id as string can cause incorrect ordering

[ https://issues.apache.org/jira/browse/YARN-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804487#comment-14804487 ] Joep Rottinghuis commented on YARN-4178: [~vrushalic] we certainly have to store the application_

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

[ https://issues.apache.org/jira/browse/YARN-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-4074: -- Attachment: YARN-4074-YARN-2928.008.patch v.8 patch posted. Fixed the checkstyle and findbugs issues.

[jira] [Created] (YARN-4180) AMLauncher does not retry on failures when talking to NM

Anubhav Dhoot created YARN-4180: --- Summary: AMLauncher does not retry on failures when talking to NM Key: YARN-4180 URL: https://issues.apache.org/jira/browse/YARN-4180 Project: Hadoop YARN

[jira] [Assigned] (YARN-4179) [reader implementation] support flow activity queries based on time

[ https://issues.apache.org/jira/browse/YARN-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-4179: -- Assignee: Varun Saxena > [reader implementation] support flow activity queries based on time >

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

[jira] [Commented] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804619#comment-14804619 ] Anubhav Dhoot commented on YARN-4180: - Propose using retries in the ContainerManagement proxy used by

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

[jira] [Commented] (YARN-4138) Roll back container resource allocation after resource increase token expires

[ https://issues.apache.org/jira/browse/YARN-4138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14803287#comment-14803287 ] MENG DING commented on YARN-4138: - Hi, [~sunilg] The case you mentioned is covered. When RM rolls back

[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=14803340#comment-14803340 ] Sangjin Lee commented on YARN-4074: --- That's correct. In other words, those are used to do

[jira] [Commented] (YARN-1897) CLI and core support for signal container functionality

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

[jira] [Commented] (YARN-3985) Make ReservationSystem persist state using RMStateStore reservation APIs

[ https://issues.apache.org/jira/browse/YARN-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804746#comment-14804746 ] Subru Krishnan commented on YARN-3985: -- Thanks [~adhoot] for the patch. LGTM, just a minor nit -

[jira] [Updated] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4135: Hadoop Flags: Reviewed > Improve the assertion message in MockRM while failing after waiting

[jira] [Updated] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-4135: Priority: Trivial (was: Minor) > Improve the assertion message in MockRM while failing

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

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

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

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

[jira] [Commented] (YARN-4143) Optimize the check for AMContainer allocation needed by blacklisting and ContainerType

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

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

[ https://issues.apache.org/jira/browse/YARN-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804904#comment-14804904 ] Rohith Sharma K S commented on YARN-4135: - +1 lgtm > Improve the assertion message in MockRM while

[jira] [Commented] (YARN-4135) Improve the assertion message in MockRM while failing after waiting for the state.

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

[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=14804943#comment-14804943 ] Naganarasimha G R commented on YARN-4044: - Hi [~sunilg], Thanks for updating the patch, few nits #

[jira] [Commented] (YARN-4167) NPE on RMActiveServices#serviceStop when store is null

[ https://issues.apache.org/jira/browse/YARN-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804952#comment-14804952 ] Rohith Sharma K S commented on YARN-4167: - +1 lgtm.. pending jenkins > NPE on

[jira] [Updated] (YARN-4180) AMLauncher does not retry on failures when talking to NM

[ https://issues.apache.org/jira/browse/YARN-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-4180: --- Affects Version/s: 2.7.1 Target Version/s: 2.7.2 Priority: Critical (was:

[jira] [Commented] (YARN-4152) NM crash with NPE when LogAggregationService#stopContainer called for absent container

[ https://issues.apache.org/jira/browse/YARN-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14804967#comment-14804967 ] Rohith Sharma K S commented on YARN-4152: - Can you extract

  1   2   >