[jira] [Commented] (YARN-3697) FairScheduler: ContinuousSchedulingThread can't be shutdown after stop sometimes.

[ https://issues.apache.org/jira/browse/YARN-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707921#comment-14707921 ] Karthik Kambatla commented on YARN-3697: The patch itself looks good. Can we add a

[jira] [Commented] (YARN-4058) Miscellaneous issues in NodeManager project

[ https://issues.apache.org/jira/browse/YARN-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707818#comment-14707818 ] Sangjin Lee commented on YARN-4058: --- I see. We might then want to address it on our branc

[jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707720#comment-14707720 ] Jun Gong commented on YARN-3896: [~rohithsharma] Thanks for the help. Re-submit your same

[jira] [Updated] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3896: --- Attachment: YARN-3896.07.patch > RMNode transitioned from RUNNING to REBOOTED because its response id had not

[jira] [Commented] (YARN-4058) Miscellaneous issues in NodeManager project

[ https://issues.apache.org/jira/browse/YARN-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707703#comment-14707703 ] Naganarasimha G R commented on YARN-4058: - thanks [~sjlee0] for the review comments

[jira] [Commented] (YARN-3814) REST API implementation for getting raw entities in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707632#comment-14707632 ] Junping Du commented on YARN-3814: -- The patch LGTM too. [~sjlee0], please feel free to go

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

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C updated YARN-3901: - Attachment: YARN-3901-YARN-2928.1.patch Uploading patch v01. This patch contains the code that creates and

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

[ https://issues.apache.org/jira/browse/YARN-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707617#comment-14707617 ] Vrushali C commented on YARN-3901: -- For long running apps, an entry needs to be made into

[jira] [Resolved] (YARN-4063) Populate the flow activity table

[ https://issues.apache.org/jira/browse/YARN-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrushali C resolved YARN-4063. -- Resolution: Duplicate Release Note: The code for flow activity table creation, population and testi

[jira] [Commented] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707607#comment-14707607 ] Hudson commented on YARN-3986: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #2221 (See [https://

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

[ https://issues.apache.org/jira/browse/YARN-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707609#comment-14707609 ] Hudson commented on YARN-2923: -- SUCCESS: Integrated in Hadoop-Hdfs-trunk #2221 (See [https://

[jira] [Created] (YARN-4070) Add the flush and compaction functionality via coprocessors and scanners for flow activity table

Vrushali C created YARN-4070: Summary: Add the flush and compaction functionality via coprocessors and scanners for flow activity table Key: YARN-4070 URL: https://issues.apache.org/jira/browse/YARN-4070

[jira] [Updated] (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:all-tabpanel ] Vrushali C updated YARN-4062: - Summary: Add the flush and compaction functionality via coprocessors and scanners for flow run table (was:

[jira] [Created] (YARN-4069) For long running apps (> 2 days), populate flow activity table

Vrushali C created YARN-4069: Summary: For long running apps (> 2 days), populate flow activity table Key: YARN-4069 URL: https://issues.apache.org/jira/browse/YARN-4069 Project: Hadoop YARN Iss

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

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

[jira] [Commented] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Commented] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

[ https://issues.apache.org/jira/browse/YARN-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707544#comment-14707544 ] Hudson commented on YARN-3986: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2240 (See [htt

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

[ https://issues.apache.org/jira/browse/YARN-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707545#comment-14707545 ] Hudson commented on YARN-2923: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2240 (See [htt

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

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

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

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

[jira] [Commented] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

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

[jira] [Commented] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Commented] (YARN-2884) Proxying all AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707325#comment-14707325 ] Subru Krishnan commented on YARN-2884: -- [~jianhe] had an offline clarification - how d

[jira] [Commented] (YARN-3986) getTransferredContainers in AbstractYarnScheduler should be present in YarnScheduler interface instead

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

[jira] [Commented] (YARN-2923) Support configuration based NodeLabelsProvider Service in Distributed Node Label Configuration Setup

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

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

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707290#comment-14707290 ] Anubhav Dhoot commented on YARN-4024: - Hi [~zhiguohong] the fix looks good. We can avoi

[jira] [Updated] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] MENG DING updated YARN-1197: Attachment: YARN-1197_Design.2015.08.21.pdf The NodeManager side of the implementation has been completed. Ma

[jira] [Commented] (YARN-4063) Populate the flow activity table

[ https://issues.apache.org/jira/browse/YARN-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707256#comment-14707256 ] Joep Rottinghuis commented on YARN-4063: Min max should work well. Wondering how we

[jira] [Commented] (YARN-4067) available resource could be set negative

[ https://issues.apache.org/jira/browse/YARN-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707237#comment-14707237 ] Ravi Prakash commented on YARN-4067: 2.7.1 has already been released. Please choose eit

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

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-4024: Component/s: resourcemanager > YARN RM should avoid unnecessary resolving IP when NMs doing heartbeat

[jira] [Updated] (YARN-4067) available resource could be set negative

[ https://issues.apache.org/jira/browse/YARN-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ravi Prakash updated YARN-4067: --- Fix Version/s: (was: 2.7.1) > available resource could be set negative > --

[jira] [Commented] (YARN-4045) Negative avaialbleMB is being reported for root queue.

[ https://issues.apache.org/jira/browse/YARN-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707158#comment-14707158 ] Wangda Tan commented on YARN-4045: -- Hi [~lichangleo], I think the comprehensive fix is, wh

[jira] [Commented] (YARN-4058) Miscellaneous issues in NodeManager project

[ https://issues.apache.org/jira/browse/YARN-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707144#comment-14707144 ] Sangjin Lee commented on YARN-4058: --- If I'm not mistaken, the issues with {{ContainerMana

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

[ https://issues.apache.org/jira/browse/YARN-4024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707086#comment-14707086 ] Wangda Tan commented on YARN-4024: -- By some reason Jenkins wasn't triggerred, manual trigg

[jira] [Commented] (YARN-3814) REST API implementation for getting raw entities in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707083#comment-14707083 ] Sangjin Lee commented on YARN-3814: --- The latest patch (v.6) LGTM. I'll wait for [~djp]'s

[jira] [Commented] (YARN-3862) Decide which contents to retrieve and send back in response in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14707073#comment-14707073 ] Sangjin Lee commented on YARN-3862: --- I understand that the distiction between what select

[jira] [Commented] (YARN-3814) REST API implementation for getting raw entities in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706966#comment-14706966 ] Junping Du commented on YARN-3814: -- Thanks [~varun_saxena] for your patient. I am still re

[jira] [Commented] (YARN-3862) Decide which contents to retrieve and send back in response in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706566#comment-14706566 ] Varun Saxena commented on YARN-3862: bq. As for the timeline filters, strictly speaking

[jira] [Commented] (YARN-3814) REST API implementation for getting raw entities in TimelineReader

[ https://issues.apache.org/jira/browse/YARN-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706562#comment-14706562 ] Varun Saxena commented on YARN-3814: [~sjlee0], [~djp], any more comments ? > REST API

[jira] [Updated] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith Sharma K S updated YARN-3896: Attachment: 0001-YARN-3896.patch When I applying the patch, patch apply was failing for 2 chu

[jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706464#comment-14706464 ] Rohith Sharma K S commented on YARN-3896: - Thanks for the clariffication.. > RMNod

[jira] [Commented] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

[ https://issues.apache.org/jira/browse/YARN-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706342#comment-14706342 ] Brahma Reddy Battula commented on YARN-3573: Attached the patch..kindly review.

[jira] [Updated] (YARN-3573) MiniMRYarnCluster constructor that starts the timeline server using a boolean should be marked depricated

[ https://issues.apache.org/jira/browse/YARN-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-3573: --- Attachment: YARN-3573-002.patch > MiniMRYarnCluster constructor that starts the timelin

[jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset

[ https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14706327#comment-14706327 ] Jun Gong commented on YARN-3896: Thanks [~rohithsharma] for the review. RMNode is a public