[jira] [Commented] (YARN-3459) TestLog4jWarningErrorMetricsAppender breaks in trunk

[ https://issues.apache.org/jira/browse/YARN-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484798#comment-14484798 ] Hadoop QA commented on YARN-3459: - {color:red}-1 overall{color}. Here are the results of

[jira] [Updated] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3391: -- Attachment: YARN-3391.4.patch Clearly define flow ID/ flow run / flow version in API and storage

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

[ https://issues.apache.org/jira/browse/YARN-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484813#comment-14484813 ] Hadoop QA commented on YARN-3457: - {color:red}-1 overall{color}. Here are the results of

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484815#comment-14484815 ] Zhijie Shen commented on YARN-3391: --- I created a new patch: bq. So in general, I think

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

[ https://issues.apache.org/jira/browse/YARN-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484845#comment-14484845 ] Tsuyoshi Ozawa commented on YARN-3457: -- +1, committing this shortly. NPE when

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485071#comment-14485071 ] Devaraj K commented on YARN-3225: - Thanks [~djp] for your review. bq. I think we should

[jira] [Commented] (YARN-3462) Patches applied for YARN-2424 are inconsistent between trunk and branch-2

[ https://issues.apache.org/jira/browse/YARN-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485151#comment-14485151 ] Naganarasimha G R commented on YARN-3462: - [~qwertymaniac]/[~aw] Can you guys take

[jira] [Commented] (YARN-3110) Few issues in ApplicationHistory web ui

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

[jira] [Commented] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

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

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

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

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

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

[jira] [Commented] (YARN-3110) Few issues in ApplicationHistory web ui

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

[jira] [Commented] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

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

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

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

[jira] [Commented] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

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

[jira] [Commented] (YARN-3110) Few issues in ApplicationHistory web ui

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

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

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

[jira] [Commented] (YARN-3110) Few issues in ApplicationHistory web ui

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

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Commented] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

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

[jira] [Commented] (YARN-3326) ReST support for getLabelsToNodes

[ https://issues.apache.org/jira/browse/YARN-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485159#comment-14485159 ] Naganarasimha G R commented on YARN-3326: - Hi [~ozawa], Test case failure is not

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

[ https://issues.apache.org/jira/browse/YARN-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484931#comment-14484931 ] Bibin A Chundatt commented on YARN-3457: Thank you [~ozawa] for checking and

[jira] [Updated] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3464: Description: Race condition in LocalizerRunner causes container localization timeout. Currently

[jira] [Created] (YARN-3465) use LinkedHashMap to keep the order of LocalResourceRequest in ContainerImpl

zhihai xu created YARN-3465: --- Summary: use LinkedHashMap to keep the order of LocalResourceRequest in ContainerImpl Key: YARN-3465 URL: https://issues.apache.org/jira/browse/YARN-3465 Project: Hadoop YARN

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Created] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

zhihai xu created YARN-3464: --- Summary: Race condition in LocalizerRunner causes container localization timeout. Key: YARN-3464 URL: https://issues.apache.org/jira/browse/YARN-3464 Project: Hadoop YARN

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

[ https://issues.apache.org/jira/browse/YARN-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484917#comment-14484917 ] Ravi Prakash commented on YARN-3429: You may have inadvertantly used the wrong JIRA

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484920#comment-14484920 ] zhihai xu commented on YARN-3464: - This issue only happened for PRIVATE/APPLICATION

[jira] [Commented] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485466#comment-14485466 ] Craig Welch commented on YARN-3293: --- Overall +1 looks good to me. One additional thing

[jira] [Commented] (YARN-2003) Support to process Job priority from Submission Context in AppAttemptAddedSchedulerEvent [RM side]

[ https://issues.apache.org/jira/browse/YARN-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485392#comment-14485392 ] Sunil G commented on YARN-2003: --- Findbugs warnings are not related. Support to process Job

[jira] [Commented] (YARN-3388) Allocation in LeafQueue could get stuck because DRF calculator isn't well supported when computing user-limit

[ https://issues.apache.org/jira/browse/YARN-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485413#comment-14485413 ] Nathan Roberts commented on YARN-3388: -- Test failures don't appear related to patch.

[jira] [Commented] (YARN-3466) RM nodes web page does not sort by node HTTP address or containers

[ https://issues.apache.org/jira/browse/YARN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485451#comment-14485451 ] Jason Lowe commented on YARN-3466: -- This was caused by YARN-2943. A new column was added

[jira] [Updated] (YARN-3466) RM nodes web page does not sort by node HTTP address or containers

[ https://issues.apache.org/jira/browse/YARN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3466: - Attachment: YARN-3466.001.patch Patch to bump the column indices to take into account the new node label

[jira] [Commented] (YARN-3448) Add Rolling Time To Lives Level DB Plugin Capabilities

[ https://issues.apache.org/jira/browse/YARN-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485446#comment-14485446 ] Zhijie Shen commented on YARN-3448: --- bq. In fact, all rolling dbs from now unto ttl may

[jira] [Updated] (YARN-3466) RM nodes web page does not sort by node HTTP address or containers

[ https://issues.apache.org/jira/browse/YARN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3466: - Affects Version/s: (was: 2.6.0) 2.7.0 RM nodes web page does not sort by node

[jira] [Commented] (YARN-2890) MiniMRYarnCluster should turn on timeline service if configured to do so

[ https://issues.apache.org/jira/browse/YARN-2890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485303#comment-14485303 ] Mit Desai commented on YARN-2890: - [~hitesh] any comments on the latest patch?

[jira] [Commented] (YARN-2637) maximum-am-resource-percent could be respected for both LeafQueue/User when trying to activate applications.

[ https://issues.apache.org/jira/browse/YARN-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485551#comment-14485551 ] Junping Du commented on YARN-2637: -- Hi [~cwelch] and [~jianhe], I think MAPREDUCE-6189

[jira] [Commented] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485557#comment-14485557 ] Craig Welch commented on YARN-3293: --- Your call, I think it's also fine to wait to do this

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485566#comment-14485566 ] Karthik Kambatla commented on YARN-3464: I have been investigating a similar issue.

[jira] [Updated] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3361: - Attachment: YARN-3361.3.patch Thanks for your comments, [~vinodkv]/[~jianhe]: * Main code comments from

[jira] [Commented] (YARN-3051) [Storage abstraction] Create backing storage read interface for ATS readers

[ https://issues.apache.org/jira/browse/YARN-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485607#comment-14485607 ] Zhijie Shen commented on YARN-3051: --- bq. My sense is that it should be fine to use the

[jira] [Commented] (YARN-3225) New parameter or CLI for decommissioning node gracefully in RMAdmin CLI

[ https://issues.apache.org/jira/browse/YARN-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485199#comment-14485199 ] Junping Du commented on YARN-3225: -- Thanks [~devaraj.k] for replying. bq. If the user

[jira] [Commented] (YARN-3127) Apphistory url crashes when RM switches with ATS enabled

[ https://issues.apache.org/jira/browse/YARN-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485235#comment-14485235 ] Xuan Gong commented on YARN-3127: - [~Naganarasimha] Thanks for working on this. I will take

[jira] [Commented] (YARN-3348) Add a 'yarn top' tool to help understand cluster usage

[ https://issues.apache.org/jira/browse/YARN-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485242#comment-14485242 ] Varun Vasudev commented on YARN-3348: - The last line Moved the cache to YarnClientImpl

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485237#comment-14485237 ] Junping Du commented on YARN-3391: -- Thanks [~zjshen] for updating the patch! bq. According

[jira] [Updated] (YARN-3348) Add a 'yarn top' tool to help understand cluster usage

[ https://issues.apache.org/jira/browse/YARN-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3348: Attachment: apache-yarn-3348.2.patch Thanks for the reviews [~aw] and [~jianhe]. bq. Why are we

[jira] [Updated] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Vasudev updated YARN-3293: Attachment: apache-yarn-3293.6.patch Uploaded a new patch with getters so that findbugs doesn't

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485295#comment-14485295 ] Junping Du commented on YARN-3347: -- Hi [~xgong], thanks for reporting this issue and

[jira] [Commented] (YARN-3466) Fix RM nodes web page to sort by node HTTP-address, #containers and node-label column

[ https://issues.apache.org/jira/browse/YARN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485717#comment-14485717 ] Wangda Tan commented on YARN-3466: -- Updated title and description, added node-label column

[jira] [Updated] (YARN-3466) Fix RM nodes web page to sort by node HTTP-address, #containers and node-label column

[ https://issues.apache.org/jira/browse/YARN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3466: - Description: The ResourceManager does not support sorting by the node HTTP address, container count and

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

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

[jira] [Created] (YARN-3467) Expose allocatedMB, allocatedVCores, and runningContainers metrics on running Applications on RM Web UI

Anthony Rojas created YARN-3467: --- Summary: Expose allocatedMB, allocatedVCores, and runningContainers metrics on running Applications on RM Web UI Key: YARN-3467 URL: https://issues.apache.org/jira/browse/YARN-3467

[jira] [Commented] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

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

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Commented] (YARN-3110) Few issues in ApplicationHistory web ui

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

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485741#comment-14485741 ] Jian He commented on YARN-3136: --- [~sunilg], sorry for the late response. we can suppress the

[jira] [Updated] (YARN-3055) The token is not renewed properly if it's shared by jobs (oozie) in DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daryn Sharp updated YARN-3055: -- Attachment: YARN-3055.patch Haven't had a chance to run findbugs. Might grumble about sync

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

[ https://issues.apache.org/jira/browse/YARN-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485751#comment-14485751 ] Robert Kanter commented on YARN-3429: - Ya, sorry about that; I only noticed yesterday,

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485775#comment-14485775 ] zhihai xu commented on YARN-3464: - [~kasha], thanks for the information. I just looked at

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485781#comment-14485781 ] Vinod Kumar Vavilapalli commented on YARN-3391: --- A cosmetic suggestion:

[jira] [Commented] (YARN-3391) Clearly define flow ID/ flow run / flow version in API and storage

[ https://issues.apache.org/jira/browse/YARN-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485791#comment-14485791 ] Vrushali C commented on YARN-3391: -- [~vinodkv] , +1 for flow_run to be called as

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485797#comment-14485797 ] Naganarasimha G R commented on YARN-3044: - Thanks for the review comments

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485794#comment-14485794 ] zhihai xu commented on YARN-3464: - I also created another JIRA YARN-3465, which can help

[jira] [Commented] (YARN-3434) Interaction between reservations and userlimit can result in significant ULF violation

[ https://issues.apache.org/jira/browse/YARN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485798#comment-14485798 ] Thomas Graves commented on YARN-3434: - [~wangda] YARN-3243 fixes part of the problem

[jira] [Comment Edited] (YARN-3434) Interaction between reservations and userlimit can result in significant ULF violation

[ https://issues.apache.org/jira/browse/YARN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485798#comment-14485798 ] Thomas Graves edited comment on YARN-3434 at 4/8/15 6:59 PM: -

[jira] [Updated] (YARN-3467) Expose allocatedMB, allocatedVCores, and runningContainers metrics on running Applications in RM Web UI

[ https://issues.apache.org/jira/browse/YARN-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Rojas updated YARN-3467: Summary: Expose allocatedMB, allocatedVCores, and runningContainers metrics on running Applications

[jira] [Commented] (YARN-3467) Expose allocatedMB, allocatedVCores, and runningContainers metrics on running Applications on RM Web UI

[ https://issues.apache.org/jira/browse/YARN-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485792#comment-14485792 ] Rohith commented on YARN-3467: -- I think ApplicationAttempt page would give these information.

[jira] [Updated] (YARN-3434) Interaction between reservations and userlimit can result in significant ULF violation

[ https://issues.apache.org/jira/browse/YARN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-3434: Attachment: YARN-3434.patch Interaction between reservations and userlimit can result in

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485818#comment-14485818 ] Karthik Kambatla commented on YARN-3464: We can may be discuss this more on

[jira] [Commented] (YARN-2423) TimelineClient should wrap all GET APIs to facilitate Java users

[ https://issues.apache.org/jira/browse/YARN-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485827#comment-14485827 ] Robert Kanter commented on YARN-2423: - Thanks for the comments Steve; those definitely

[jira] [Commented] (YARN-3434) Interaction between reservations and userlimit can result in significant ULF violation

[ https://issues.apache.org/jira/browse/YARN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485834#comment-14485834 ] Thomas Graves commented on YARN-3434: - Note I had a reproducible test case for this.

[jira] [Commented] (YARN-3136) getTransferredContainers can be a bottleneck during AM registration

[ https://issues.apache.org/jira/browse/YARN-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485396#comment-14485396 ] Sunil G commented on YARN-3136: --- Hi [~jlowe] and [~jianhe] Cud u pls have a look on the

[jira] [Created] (YARN-3466) RM nodes web page does not sort by node HTTP address or containers

Jason Lowe created YARN-3466: Summary: RM nodes web page does not sort by node HTTP address or containers Key: YARN-3466 URL: https://issues.apache.org/jira/browse/YARN-3466 Project: Hadoop YARN

[jira] [Commented] (YARN-3055) The token is not renewed properly if it's shared by jobs (oozie) in DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485461#comment-14485461 ] Daryn Sharp commented on YARN-3055: --- bq. It does seem odd to get the expiration date by

[jira] [Commented] (YARN-3044) [Event producers] Implement RM writing app lifecycle events to ATS

[ https://issues.apache.org/jira/browse/YARN-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485527#comment-14485527 ] Zhijie Shen commented on YARN-3044: --- Before screening the patch details, I have some high

[jira] [Commented] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485530#comment-14485530 ] Xuan Gong commented on YARN-3347: - Thanks for the review. bq. For comma-separated value,

[jira] [Updated] (YARN-3347) Improve YARN log command to get AMContainer logs as well as running containers logs

[ https://issues.apache.org/jira/browse/YARN-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-3347: Attachment: YARN-3347.3.patch Improve YARN log command to get AMContainer logs as well as running

[jira] [Commented] (YARN-3293) Track and display capacity scheduler health metrics in web UI

[ https://issues.apache.org/jira/browse/YARN-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485541#comment-14485541 ] Varun Vasudev commented on YARN-3293: - Thanks for the review Craig! I thought about it

[jira] [Updated] (YARN-3361) CapacityScheduler side changes to support non-exclusive node labels

[ https://issues.apache.org/jira/browse/YARN-3361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3361: - Attachment: YARN-3361.4.patch Attached patch fixed several naming issues. (ver.4) CapacityScheduler side

[jira] [Commented] (YARN-3055) The token is not renewed properly if it's shared by jobs (oozie) in DelegationTokenRenewer

[ https://issues.apache.org/jira/browse/YARN-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485638#comment-14485638 ] Jian He commented on YARN-3055: --- sure, looking forward to your patch. bq. The correct fix

[jira] [Updated] (YARN-3459) TestLog4jWarningErrorMetricsAppender breaks in trunk

[ https://issues.apache.org/jira/browse/YARN-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3459: - Fix Version/s: (was: 2.7.0) 2.8.0 TestLog4jWarningErrorMetricsAppender breaks in

[jira] [Updated] (YARN-3459) Fix failiure of TestLog4jWarningErrorMetricsAppender

[ https://issues.apache.org/jira/browse/YARN-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3459: - Assignee: Varun Vasudev (was: Li Lu) Fix failiure of TestLog4jWarningErrorMetricsAppender

[jira] [Commented] (YARN-2684) FairScheduler should tolerate queue configuration changes across RM restarts

[ https://issues.apache.org/jira/browse/YARN-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485655#comment-14485655 ] Rohith commented on YARN-2684: -- [~kasha] kindly provide your thoughts any more changes to be

[jira] [Assigned] (YARN-2901) Add errors and warning metrics page to RM, NM web UI

[ https://issues.apache.org/jira/browse/YARN-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reassigned YARN-2901: Assignee: Wangda Tan (was: Varun Vasudev) Add errors and warning metrics page to RM, NM web UI

[jira] [Commented] (YARN-3466) RM nodes web page does not sort by node HTTP address or containers

[ https://issues.apache.org/jira/browse/YARN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485711#comment-14485711 ] Wangda Tan commented on YARN-3466: -- Tried in a local cluster, HTTP address, #containers

[jira] [Updated] (YARN-3459) Fix failiure of TestLog4jWarningErrorMetricsAppender

[ https://issues.apache.org/jira/browse/YARN-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3459: - Summary: Fix failiure of TestLog4jWarningErrorMetricsAppender (was: TestLog4jWarningErrorMetricsAppender

[jira] [Updated] (YARN-2901) Add errors and warning metrics page to RM, NM web UI

[ https://issues.apache.org/jira/browse/YARN-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2901: - Assignee: Varun Vasudev (was: Wangda Tan) Add errors and warning metrics page to RM, NM web UI

[jira] [Commented] (YARN-3459) Fix failiure of TestLog4jWarningErrorMetricsAppender

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

[jira] [Commented] (YARN-3110) Few issues in ApplicationHistory web ui

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

[jira] [Commented] (YARN-3457) NPE when NodeManager.serviceInit fails and stopRecoveryStore called

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

[jira] [Commented] (YARN-3464) Race condition in LocalizerRunner causes container localization timeout.

[ https://issues.apache.org/jira/browse/YARN-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14485687#comment-14485687 ] Karthik Kambatla commented on YARN-3464: bq. Looking at the code closely, I don't

[jira] [Commented] (YARN-3429) TestAMRMTokens.testTokenExpiry fails Intermittently with error message:Invalid AMRMToken

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

[jira] [Commented] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

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

[jira] [Updated] (YARN-3466) Fix RM nodes web page to sort by node HTTP-address, #containers and node-label column

[ https://issues.apache.org/jira/browse/YARN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3466: - Summary: Fix RM nodes web page to sort by node HTTP-address, #containers and node-label column (was: RM

[jira] [Commented] (YARN-2901) Add errors and warning metrics page to RM, NM web UI

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

[jira] [Updated] (YARN-3448) Add Rolling Time To Lives Level DB Plugin Capabilities

[ https://issues.apache.org/jira/browse/YARN-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated YARN-3448: -- Attachment: YARN-3448.4.patch Couple of more bug fixes in patch 4. Next I try out the index

[jira] [Updated] (YARN-3426) Add jdiff support to YARN

[ https://issues.apache.org/jira/browse/YARN-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3426: Attachment: YARN-3426-040815.patch Fixed the problem in hadoop-annotate for our javadoc doclet (missing some

  1   2   >