[jira] [Commented] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288522#comment-15288522 ] Varun Saxena commented on YARN-5093: Yes. Write it out only if its > 0. > created time

[jira] [Commented] (YARN-4887) AM-RM protocol changes for supporting delta protocol

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

[jira] [Commented] (YARN-5107) TestContainerMetrics fails

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

[jira] [Commented] (YARN-5096) timelinereader has a lot of logging that's not useful

[ https://issues.apache.org/jira/browse/YARN-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288490#comment-15288490 ] Varun Saxena commented on YARN-5096: +1. Will commit it shortly. > timelinereader has

[jira] [Reopened] (YARN-5038) [YARN-3368] Application and Container pages shows wrong values when RM is stopped

[ https://issues.apache.org/jira/browse/YARN-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan reopened YARN-5038: -- > [YARN-3368] Application and Container pages shows wrong values when RM is > stopped >

[jira] [Commented] (YARN-5000) [YARN-3368] App attempt page is not loading when timeline server is not started

[ https://issues.apache.org/jira/browse/YARN-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288470#comment-15288470 ] Wangda Tan commented on YARN-5000: -- Committed with YARN-4515. (72151c24452cfef250f7ce6f457

[jira] [Resolved] (YARN-5038) [YARN-3368] Application and Container pages shows wrong values when RM is stopped

[ https://issues.apache.org/jira/browse/YARN-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan resolved YARN-5038. -- Resolution: Fixed Hadoop Flags: Reviewed Fix Version/s: YARN-3368 Committed with YARN-4515. (

[jira] [Commented] (YARN-4515) [YARN-3368] Support hosting web UI framework inside YARN RM

[ https://issues.apache.org/jira/browse/YARN-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288465#comment-15288465 ] Wangda Tan commented on YARN-4515: -- Thanks [~sunilg], latest patch looks good to me, commi

[jira] [Commented] (YARN-5108) TestFileSystemApplicationHistoryStore fails

[ https://issues.apache.org/jira/browse/YARN-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288462#comment-15288462 ] Brahma Reddy Battula commented on YARN-5108: It's dupe of HADOOP-13140.. > Tes

[jira] [Updated] (YARN-5096) timelinereader has a lot of logging that's not useful

[ https://issues.apache.org/jira/browse/YARN-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-5096: -- Attachment: YARN-5096-YARN-2928.01.patch Posted the patch. Could you please take a quick look and commit

[jira] [Updated] (YARN-5096) timelinereader has a lot of logging that's not useful

[ https://issues.apache.org/jira/browse/YARN-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-5096: -- Description: After running about a dozen or so requests, the timelinereader log is filled with the follo

[jira] [Commented] (YARN-5109) timestamps are stored unencoded causing parse errors

[ https://issues.apache.org/jira/browse/YARN-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288444#comment-15288444 ] Sangjin Lee commented on YARN-5109: --- For example, code that creates the column name for e

[jira] [Created] (YARN-5109) timestamps are stored unencoded causing parse errors

Sangjin Lee created YARN-5109: - Summary: timestamps are stored unencoded causing parse errors Key: YARN-5109 URL: https://issues.apache.org/jira/browse/YARN-5109 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288193#comment-15288193 ] Allen Wittenauer commented on YARN-4757: Also, why is this a YARN JIRA? It seems

[jira] [Commented] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

[ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288191#comment-15288191 ] Allen Wittenauer commented on YARN-4757: So rather than add these capabilities to a

[jira] [Updated] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4844: - Attachment: YARN-4844.9.branch Attached ver.9 patch, rebased to latest trunk/branch-2 and fixed build failu

[jira] [Updated] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4844: - Attachment: YARN-4844.9.branch-2.patch > Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resour

[jira] [Updated] (YARN-2882) Add an OPPORTUNISTIC ExecutionType

[ https://issues.apache.org/jira/browse/YARN-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-2882: -- Issue Type: Sub-task (was: New Feature) Parent: YARN-2877 > Add an OPPORTUNISTIC ExecutionType >

[jira] [Commented] (YARN-4913) Yarn logs should take a -out option to write to a directory

[ https://issues.apache.org/jira/browse/YARN-4913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288120#comment-15288120 ] Varun Vasudev commented on YARN-4913: - After some offline discussion with [~xgong] and

[jira] [Commented] (YARN-5090) Add End-to-End test-cases for DistributedScheduling using MiniYarnCluster

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

[jira] [Updated] (YARN-4887) AM-RM protocol changes for supporting delta protocol

[ https://issues.apache.org/jira/browse/YARN-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-4887: - Attachment: YARN-4887-v1.patch Attaching a patch with the proposed API changes. The patch does not

[jira] [Commented] (YARN-5107) TestContainerMetrics fails

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

[jira] [Updated] (YARN-5090) Add End-to-End test-cases for DistributedScheduling using MiniYarnCluster

[ https://issues.apache.org/jira/browse/YARN-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-5090: -- Parent Issue: YARN-2877 (was: YARN-4742) > Add End-to-End test-cases for DistributedScheduling using Min

[jira] [Commented] (YARN-5090) Add End-to-End test-cases for DistributedScheduling using MiniYarnCluster

[ https://issues.apache.org/jira/browse/YARN-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288073#comment-15288073 ] Arun Suresh commented on YARN-5090: --- Thanks again for the review [~leftnoteasy]. Committi

[jira] [Commented] (YARN-2877) Extend YARN to support distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288066#comment-15288066 ] Konstantinos Karanasos commented on YARN-2877: -- Marked the JIRA as resolved an

[jira] [Resolved] (YARN-2877) Extend YARN to support distributed scheduling

[ https://issues.apache.org/jira/browse/YARN-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantinos Karanasos resolved YARN-2877. -- Resolution: Resolved Hadoop Flags: Reviewed Release Note: W

[jira] [Commented] (YARN-4308) ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats

[ https://issues.apache.org/jira/browse/YARN-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287992#comment-15287992 ] Naganarasimha G R commented on YARN-4308: - [~sunilg], As most of us agree that metr

[jira] [Updated] (YARN-5108) TestFileSystemApplicationHistoryStore fails

[ https://issues.apache.org/jira/browse/YARN-5108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-5108: - Description: Unit test failure is found in other JIRA Jenkins test (YARN-5100): {noformat} Running org.apa

[jira] [Commented] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287986#comment-15287986 ] Sangjin Lee commented on YARN-5093: --- The fix could be not writing the created column (and

[jira] [Assigned] (YARN-5096) timelinereader has a lot of logging that's not useful

[ https://issues.apache.org/jira/browse/YARN-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee reassigned YARN-5096: - Assignee: Sangjin Lee > timelinereader has a lot of logging that's not useful > --

[jira] [Commented] (YARN-5100) The YarnApplicationState is always running in ATS no matter the application is running or finishes.

[ https://issues.apache.org/jira/browse/YARN-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287968#comment-15287968 ] Xuan Gong commented on YARN-5100: - [~djp] The testcase failure is not related. Create htt

[jira] [Created] (YARN-5108) TestFileSystemApplicationHistoryStore fails

Xuan Gong created YARN-5108: --- Summary: TestFileSystemApplicationHistoryStore fails Key: YARN-5108 URL: https://issues.apache.org/jira/browse/YARN-5108 Project: Hadoop YARN Issue Type: Test

[jira] [Commented] (YARN-1151) Ability to configure auxiliary services from HDFS-based JAR files

[ https://issues.apache.org/jira/browse/YARN-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287966#comment-15287966 ] Hitesh Shah commented on YARN-1151: --- For paths, the impl should do auto-resolving i.e. us

[jira] [Commented] (YARN-1151) Ability to configure auxiliary services from HDFS-based JAR files

[ https://issues.apache.org/jira/browse/YARN-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287963#comment-15287963 ] Hitesh Shah commented on YARN-1151: --- How can one specify an archive? or would only simple

[jira] [Commented] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

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

[jira] [Assigned] (YARN-3621) FairScheduler doesn't count AM vcores towards max-share

[ https://issues.apache.org/jira/browse/YARN-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu reassigned YARN-3621: -- Assignee: Yufei Gu > FairScheduler doesn't count AM vcores towards max-share > -

[jira] [Updated] (YARN-4975) Fair Scheduler: exception thrown when a parent queue marked 'parent' has configured child queues

[ https://issues.apache.org/jira/browse/YARN-4975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-4975: - Assignee: Yufei Gu > Fair Scheduler: exception thrown when a parent queue marked 'parent' has > configured

[jira] [Resolved] (YARN-3621) FairScheduler doesn't count AM vcores towards max-share

[ https://issues.apache.org/jira/browse/YARN-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu resolved YARN-3621. Resolution: Duplicate > FairScheduler doesn't count AM vcores towards max-share > ---

[jira] [Updated] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

[ https://issues.apache.org/jira/browse/YARN-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-5106: - Assignee: Yufei Gu > Provide a builder interface for FairScheduler allocations for use in tests > -

[jira] [Updated] (YARN-3890) FairScheduler should show the scheduler health metrics similar to ones added in CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-3890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-3890: - Assignee: Yufei Gu > FairScheduler should show the scheduler health metrics similar to ones added > in Cap

[jira] [Commented] (YARN-4832) NM side resource value should get updated if change applied in RM side

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

[jira] [Commented] (YARN-1942) Many of ConverterUtils methods need to have public interfaces

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

[jira] [Commented] (YARN-5107) TestContainerMetrics fails

[ https://issues.apache.org/jira/browse/YARN-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287879#comment-15287879 ] Akira AJISAKA commented on YARN-5107: - This issue seems to be related to JDK8 because t

[jira] [Commented] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287866#comment-15287866 ] Yufei Gu commented on YARN-5104: The failed test is unrelated. > TestNMProxy.testNMProxyRP

[jira] [Commented] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287864#comment-15287864 ] Sangjin Lee commented on YARN-5093: --- Yes, I think you're right. I initially thought this

[jira] [Updated] (YARN-5107) TestContainerMetrics fails

[ https://issues.apache.org/jira/browse/YARN-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-5107: Attachment: YARN-5107.01.patch > TestContainerMetrics fails > -- > >

[jira] [Assigned] (YARN-5107) TestContainerMetrics fails

[ https://issues.apache.org/jira/browse/YARN-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA reassigned YARN-5107: --- Assignee: Akira AJISAKA > TestContainerMetrics fails > -- > >

[jira] [Updated] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-5093: -- Description: When querying the REST API, I find that the created time value is returned as "0" for most

[jira] [Updated] (YARN-5107) TestContainerMetrics fails

[ https://issues.apache.org/jira/browse/YARN-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-5107: Description: {noformat} testContainerMetricsFlow(org.apache.hadoop.yarn.server.nodemanager.containerm

[jira] [Created] (YARN-5107) TestContainerMetrics fails

Akira AJISAKA created YARN-5107: --- Summary: TestContainerMetrics fails Key: YARN-5107 URL: https://issues.apache.org/jira/browse/YARN-5107 Project: Hadoop YARN Issue Type: Bug Componen

[jira] [Commented] (YARN-3344) procfs stat file is not in the expected format warning

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

[jira] [Commented] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

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

[jira] [Updated] (YARN-5089) Improve "yarn log" command-line "logFiles" option to support regex

[ https://issues.apache.org/jira/browse/YARN-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-5089: -- Summary: Improve "yarn log" command-line "logFiles" option to support regex (wa

[jira] [Updated] (YARN-5047) Refactor nodeUpdate across schedulers

[ https://issues.apache.org/jira/browse/YARN-5047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-5047: --- Summary: Refactor nodeUpdate across schedulers (was: Refactor nodeUpdate() from FairScheduler,

[jira] [Commented] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287828#comment-15287828 ] Daniel Templeton commented on YARN-3344: LGTM. +1 (non-binding) > procfs stat fil

[jira] [Updated] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA updated YARN-3344: Attachment: YARN-3344.09.patch Fixed checkstyle issues. Thanks! > procfs stat file is not in the exp

[jira] [Commented] (YARN-5077) Fix FSLeafQueue#getFairShare() for queues with weight 0.0

[ https://issues.apache.org/jira/browse/YARN-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287817#comment-15287817 ] Karthik Kambatla commented on YARN-5077: This has been a long standing inconvenienc

[jira] [Created] (YARN-5106) Provide a builder interface for FairScheduler allocations for use in tests

Karthik Kambatla created YARN-5106: -- Summary: Provide a builder interface for FairScheduler allocations for use in tests Key: YARN-5106 URL: https://issues.apache.org/jira/browse/YARN-5106 Project: H

[jira] [Commented] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287799#comment-15287799 ] Varun Saxena commented on YARN-5093: Checked the code. The issue with created time in c

[jira] [Commented] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287790#comment-15287790 ] Daniel Templeton commented on YARN-3344: See https://builds.apache.org/job/PreComm

[jira] [Assigned] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-5093: -- Assignee: Varun Saxena > created time shows 0 in most REST output >

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues with 'Fair' policy should compute shares of all resources for its children during a recompute

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

[jira] [Commented] (YARN-4457) Cleanup unchecked types for EventHandler

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

[jira] [Assigned] (YARN-4212) FairScheduler: Parent queues with 'Fair' policy should compute shares of all resources for its children during a recompute

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu reassigned YARN-4212: -- Assignee: Yufei Gu (was: Arun Suresh) > FairScheduler: Parent queues with 'Fair' policy should compute

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues with 'Fair' policy should compute shares of all resources for its children during a recompute

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287784#comment-15287784 ] Yufei Gu commented on YARN-4212: Thanks [~asuresh]. > FairScheduler: Parent queues with '

[jira] [Commented] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

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

[jira] [Commented] (YARN-3344) procfs stat file is not in the expected format warning

[ https://issues.apache.org/jira/browse/YARN-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287779#comment-15287779 ] Akira AJISAKA commented on YARN-3344: - bq. Clean up your whitespace issues Is there any

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues with 'Fair' policy should compute shares of all resources for its children during a recompute

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287778#comment-15287778 ] Arun Suresh commented on YARN-4212: --- Sure... feel free to take over.. > FairScheduler: P

[jira] [Commented] (YARN-4212) FairScheduler: Parent queues with 'Fair' policy should compute shares of all resources for its children during a recompute

[ https://issues.apache.org/jira/browse/YARN-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287774#comment-15287774 ] Yufei Gu commented on YARN-4212: Hi [~asuresh], are you still working on this? If not, can

[jira] [Commented] (YARN-4308) ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats

[ https://issues.apache.org/jira/browse/YARN-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287771#comment-15287771 ] Karthik Kambatla commented on YARN-4308: Given we expect to see -1 exactly once, do

[jira] [Commented] (YARN-4832) NM side resource value should get updated if change applied in RM side

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

[jira] [Commented] (YARN-4457) Cleanup unchecked types for EventHandler

[ https://issues.apache.org/jira/browse/YARN-4457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287757#comment-15287757 ] Karthik Kambatla commented on YARN-4457: Thanks for taking the time to clean these

[jira] [Commented] (YARN-4958) The file localization process should allow for wildcards to reduce the application footprint in the state store

[ https://issues.apache.org/jira/browse/YARN-4958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287735#comment-15287735 ] Daniel Templeton commented on YARN-4958: The test failures are unrelated. I filed

[jira] [Commented] (YARN-4832) NM side resource value should get updated if change applied in RM side

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

[jira] [Assigned] (YARN-5105) entire time series is returned for YARN container system metrics (CPU and memory)

[ https://issues.apache.org/jira/browse/YARN-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena reassigned YARN-5105: -- Assignee: Varun Saxena > entire time series is returned for YARN container system metrics (CPU a

[jira] [Commented] (YARN-5093) created time shows 0 in most REST output

[ https://issues.apache.org/jira/browse/YARN-5093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287708#comment-15287708 ] Varun Saxena commented on YARN-5093: [~sjlee0], For flow activities we do not populate

[jira] [Updated] (YARN-4844) Add getMemoryLong/getVirtualCoreLong to o.a.h.y.api.records.Resource

[ https://issues.apache.org/jira/browse/YARN-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-4844: - Attachment: YARN-4844.8.branch-2.patch Uploaded patch for branch-2: {{YARN-4844.8.branch-2.patch}} > Add g

[jira] [Commented] (YARN-4494) Recover completed apps asynchronously

[ https://issues.apache.org/jira/browse/YARN-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287681#comment-15287681 ] Karthik Kambatla commented on YARN-4494: [~sunilg] - can you elaborate on the on-de

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Attachment: YARN-5104.001.patch > TestNMProxy.testNMProxyRPCRetry failed >

[jira] [Commented] (YARN-4464) default value of yarn.resourcemanager.state-store.max-completed-applications should lower.

[ https://issues.apache.org/jira/browse/YARN-4464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287674#comment-15287674 ] Karthik Kambatla commented on YARN-4464: [~jianhe] - do you think it is okay to low

[jira] [Commented] (YARN-4002) make ResourceTrackerService.nodeHeartbeat more concurrent

[ https://issues.apache.org/jira/browse/YARN-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287663#comment-15287663 ] Jian He commented on YARN-4002: --- [~rohithsharma], could you fix the findbugs warning ? also,

[jira] [Commented] (YARN-4866) FairScheduler: AMs can consume all vcores leading to a livelock when using FAIR policy

[ https://issues.apache.org/jira/browse/YARN-4866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287660#comment-15287660 ] Karthik Kambatla commented on YARN-4866: Thanks for working on this, Yufei. Comment

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Description: TestNMProxy.testNMProxyRPCRetry throws an exception and expected to be caught and handled. YARN

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Description: TestNMProxy.testNMProxyRPCRetry throws an exception and expected to be caught and handled. YARN

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Description: TestNMProxy.testNMProxyRPCRetry throws an exception and expected to be caught and handled. YARN

[jira] [Commented] (YARN-5105) entire time series is returned for YARN container system metrics (CPU and memory)

[ https://issues.apache.org/jira/browse/YARN-5105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287624#comment-15287624 ] Varun Saxena commented on YARN-5105: How do we handle it ? Have an explicit limit from

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Description: YARN-4916 did solve this exception: {code} java.net.BindException: Problem binding to [xxx] java.

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Description: YARN-4916 did solve this problem: {code} java.net.BindException: Problem binding to [xxx] java.net

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Description: YARN-4916 did solve this problem: {code} java.net.BindException: Problem binding to [xxx] java.net

[jira] [Updated] (YARN-5104) TestNMProxy.testNMProxyRPCRetry failed

[ https://issues.apache.org/jira/browse/YARN-5104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-5104: --- Description: YARN-4916 did solve this problem: {code} java.net.BindException: Problem binding to [xxx] java.net

[jira] [Updated] (YARN-4832) NM side resource value should get updated if change applied in RM side

[ https://issues.apache.org/jira/browse/YARN-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4832: - Attachment: YARN-4832-branch-2.patch put a patch against branch-2 also. > NM side resource value should ge

[jira] [Commented] (YARN-5100) The YarnApplicationState is always running in ATS no matter the application is running or finishes.

[ https://issues.apache.org/jira/browse/YARN-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287596#comment-15287596 ] Junping Du commented on YARN-5100: -- bq. This would affect YARN_APPLICATION_UPDATED event a

[jira] [Commented] (YARN-5098) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token

[ https://issues.apache.org/jira/browse/YARN-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287561#comment-15287561 ] Jian He commented on YARN-5098: --- bq. the app needs to be submitted without an HDFS token so t

[jira] [Assigned] (YARN-5098) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token

[ https://issues.apache.org/jira/browse/YARN-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He reassigned YARN-5098: - Assignee: Jian He > Yarn Application log Aggreagation fails due to NM can not get correct HDFS > delegati

[jira] [Updated] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated YARN-5018: -- Labels: yarn-2928-1st-milestone (was: ) > Online aggregation logic should not run immediately after coll

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287551#comment-15287551 ] Li Lu commented on YARN-5018: - Agree that we should mark this as a merge blocker. For the missi

[jira] [Created] (YARN-5105) entire time series is returned for YARN container system metrics (CPU and memory)

Sangjin Lee created YARN-5105: - Summary: entire time series is returned for YARN container system metrics (CPU and memory) Key: YARN-5105 URL: https://issues.apache.org/jira/browse/YARN-5105 Project: Hado

[jira] [Commented] (YARN-4832) NM side resource value should get updated if change applied in RM side

[ https://issues.apache.org/jira/browse/YARN-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287550#comment-15287550 ] Junping Du commented on YARN-4832: -- Per discussion in YARN-2877, I put an addendum patch t

[jira] [Updated] (YARN-4832) NM side resource value should get updated if change applied in RM side

[ https://issues.apache.org/jira/browse/YARN-4832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-4832: - Attachment: YARN-4832-addendum.patch > NM side resource value should get updated if change applied in RM si

[jira] [Commented] (YARN-5018) Online aggregation logic should not run immediately after collectors got started

[ https://issues.apache.org/jira/browse/YARN-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287548#comment-15287548 ] Sangjin Lee commented on YARN-5018: --- Should this also be marked as the merge blocker? An

  1   2   >