[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384830#comment-14384830 ] Junping Du commented on YARN-3304: -- Thanks [~vinodkv] for comments! Agree that the second

[jira] [Updated] (YARN-3402) Security support for new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3402: - Assignee: (was: Junping Du) Security support for new timeline service.

[jira] [Commented] (YARN-3402) Security support for new timeline service.

[ https://issues.apache.org/jira/browse/YARN-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384849#comment-14384849 ] Junping Du commented on YARN-3402: -- Thanks [~vinodkv] for reminding on this. Mark it

[jira] [Updated] (YARN-3043) [Data Model] Create ATS configuration, metadata, etc. as part of entities

[ https://issues.apache.org/jira/browse/YARN-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3043: - Assignee: (was: Varun Saxena) [Data Model] Create ATS configuration, metadata, etc. as part of

[jira] [Commented] (YARN-3043) [Data Model] Create ATS configuration, metadata, etc. as part of entities

[ https://issues.apache.org/jira/browse/YARN-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384852#comment-14384852 ] Junping Du commented on YARN-3043: -- Mark it unassigned which is practice for duplicated

[jira] [Updated] (YARN-3042) [Data Model] Create ATS metrics API

[ https://issues.apache.org/jira/browse/YARN-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3042: - Assignee: (was: Siddharth Wagle) [Data Model] Create ATS metrics API

[jira] [Commented] (YARN-3258) FairScheduler: Need to add more logging to investigate allocations

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

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384868#comment-14384868 ] Vinod Kumar Vavilapalli commented on YARN-3304: --- I like the return negative

[jira] [Updated] (YARN-3412) RM tests should use MockRM where possible

[ https://issues.apache.org/jira/browse/YARN-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3412: --- Attachment: yarn-3412-1.patch Simple patch. RM tests should use MockRM where possible

[jira] [Created] (YARN-3412) RM tests should use MockRM where possible

Karthik Kambatla created YARN-3412: -- Summary: RM tests should use MockRM where possible Key: YARN-3412 URL: https://issues.apache.org/jira/browse/YARN-3412 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

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

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384899#comment-14384899 ] Karthik Kambatla commented on YARN-3304: The approach in the negative value patch

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384903#comment-14384903 ] Junping Du commented on YARN-3304: -- Yes. Please go ahead. [~kasha], thanks! I will post a

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-3304: - Attachment: YARN-3304-v4-negative-way-MR.patch MR changes for negative way. Need a new MR JIRA to put it

[jira] [Commented] (YARN-3412) RM tests should use MockRM where possible

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

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384992#comment-14384992 ] Karthik Kambatla commented on YARN-3304: Just uploaded the v5 patch. The changes

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385064#comment-14385064 ] Anubhav Dhoot commented on YARN-3304: - ProcfsProcessTree#getCumulativeCpuTime is

[jira] [Created] (YARN-3413) Node label attributes (like exclusive or not) should be able to set when addToClusterNodeLabels and shouldn't be changed during runtime

Wangda Tan created YARN-3413: Summary: Node label attributes (like exclusive or not) should be able to set when addToClusterNodeLabels and shouldn't be changed during runtime Key: YARN-3413 URL:

[jira] [Commented] (YARN-2495) Allow admin specify labels from each NM (Distributed configuration)

[ https://issues.apache.org/jira/browse/YARN-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384972#comment-14384972 ] Wangda Tan commented on YARN-2495: -- Last call for comments, I'm planning to commit this by

[jira] [Commented] (YARN-3047) [Data Serving] Set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384998#comment-14384998 ] Sangjin Lee commented on YARN-3047: --- I can understand both sides here. On the one hand,

[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=14385025#comment-14385025 ] Sangjin Lee commented on YARN-3051: --- Wanted to add my 2 cents before the weekend. As for

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

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

[jira] [Commented] (YARN-3345) Add non-exclusive node label API to RMAdmin protocol and NodeLabelsManager

[ https://issues.apache.org/jira/browse/YARN-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384947#comment-14384947 ] Vinod Kumar Vavilapalli commented on YARN-3345: --- Just looked at this. I think

[jira] [Updated] (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:all-tabpanel ] Naganarasimha G R updated YARN-2923: Attachment: YARN-2923.20150328-1.patch Hi [~john.jian.fang]. Have rebased the patch but this

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385099#comment-14385099 ] Peng Zhang commented on YARN-3405: -- bq. There is a possibility for the first scenario. If

[jira] [Commented] (YARN-3345) Add non-exclusive node label API to RMAdmin protocol and NodeLabelsManager

[ https://issues.apache.org/jira/browse/YARN-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14384955#comment-14384955 ] Wangda Tan commented on YARN-3345: -- Thanks for comments, [~vinodkv]. Make sense to me,

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3304: --- Attachment: yarn-3304-5.patch ResourceCalculatorProcessTree#getCpuUsagePercent default return

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3304: --- Attachment: yarn-3304-5.patch ResourceCalculatorProcessTree#getCpuUsagePercent default return

[jira] [Updated] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3304: --- Attachment: (was: yarn-3304-5.patch) ResourceCalculatorProcessTree#getCpuUsagePercent

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

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

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

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

[jira] [Commented] (YARN-3304) ResourceCalculatorProcessTree#getCpuUsagePercent default return value is inconsistent with other getters

[ https://issues.apache.org/jira/browse/YARN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385097#comment-14385097 ] Vinod Kumar Vavilapalli commented on YARN-3304: --- We should rename it to be

[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-tabpanelfocusedCommentId=14384983#comment-14384983 ] Jian Fang commented on YARN-2923: - Hi Naganarasimha, could you please update your patch? I

[jira] [Created] (YARN-3414) FairScheduler's preemption may cause livelock

Peng Zhang created YARN-3414: Summary: FairScheduler's preemption may cause livelock Key: YARN-3414 URL: https://issues.apache.org/jira/browse/YARN-3414 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385124#comment-14385124 ] Peng Zhang commented on YARN-3405: -- [~kasha] What the real problem I met in our cluster is

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3405: - Description: Queue hierarchy described as below: {noformat} root /

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3405: - Description: Queue hierarchy described as below: {noformat} root /

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3405: - Description: Queue hierarchy described as below: {noformat} root /

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3405: - Description: Queue hierarchy described as below: {noformat} root / \

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3405: - Description: Queue hierarchy described as below: {noformat} root /

[jira] [Updated] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peng Zhang updated YARN-3405: - Description: Queue hierarchy described as below: {noformat} root | \

[jira] [Commented] (YARN-3405) FairScheduler's preemption cannot happen between sibling in some case

[ https://issues.apache.org/jira/browse/YARN-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385135#comment-14385135 ] zhihai xu commented on YARN-3405: - This issue looks like a Comparator issue, It will be

[jira] [Assigned] (YARN-3410) YARN admin should be able to remove individual application records from RMStateStore

[ https://issues.apache.org/jira/browse/YARN-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith reassigned YARN-3410: Assignee: Rohith YARN admin should be able to remove individual application records from RMStateStore

[jira] [Commented] (YARN-3324) TestDockerContainerExecutor should clean test docker image from local repository after test is done

[ https://issues.apache.org/jira/browse/YARN-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385148#comment-14385148 ] Ravindra Kumar Naik commented on YARN-3324: --- Thanks [~raviprak] , [airbots] . I

<    1   2