[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3566) YARN Scheduler Web UI not properly sorting through Application ID or Progress bar

[ https://issues.apache.org/jira/browse/YARN-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522872#comment-14522872 ] Ryu Kobayashi commented on YARN-3566: - This issue has been fixed in this ticket(YARN-34

[jira] [Commented] (YARN-3114) It would be better to consider integer(long) overflow when compare the time in DelegationTokenRenewer.

[ https://issues.apache.org/jira/browse/YARN-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522880#comment-14522880 ] zhihai xu commented on YARN-3114: - System.nanoTime require using difference to compare two

[jira] [Reopened] (YARN-3114) It would be better to consider integer(long) overflow when compare the time in DelegationTokenRenewer.

[ https://issues.apache.org/jira/browse/YARN-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu reopened YARN-3114: - > It would be better to consider integer(long) overflow when compare the time > in DelegationTokenRenewer. > -

[jira] [Resolved] (YARN-3114) It would be better to consider integer(long) overflow when compare the time in DelegationTokenRenewer.

[ https://issues.apache.org/jira/browse/YARN-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu resolved YARN-3114. - Resolution: Not A Problem > It would be better to consider integer(long) overflow when compare the time >

[jira] [Resolved] (YARN-2873) improve LevelDB error handling for missing files DBException to avoid NM start failure.

[ https://issues.apache.org/jira/browse/YARN-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu resolved YARN-2873. - Resolution: Not A Problem > improve LevelDB error handling for missing files DBException to avoid NM > sta

[jira] [Reopened] (YARN-2873) improve LevelDB error handling for missing files DBException to avoid NM start failure.

[ https://issues.apache.org/jira/browse/YARN-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu reopened YARN-2873: - > improve LevelDB error handling for missing files DBException to avoid NM > start failure. >

[jira] [Commented] (YARN-2873) improve LevelDB error handling for missing files DBException to avoid NM start failure.

[ https://issues.apache.org/jira/browse/YARN-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522890#comment-14522890 ] zhihai xu commented on YARN-2873: - We didn't see this problem any more after store levelDB

[jira] [Updated] (YARN-3534) Collect node resource utilization

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Inigo Goiri updated YARN-3534: -- Attachment: YARN-3534-6.patch Diff to the latest trunk. > Collect node resource utilization > --

[jira] [Commented] (YARN-3534) Collect node resource utilization

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522895#comment-14522895 ] Inigo Goiri commented on YARN-3534: --- Sorry about that, I did the diff and then I did the

[jira] [Commented] (YARN-3551) Consolidate data model change according to the backend implementation

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

[jira] [Commented] (YARN-3534) Collect node resource utilization

[ https://issues.apache.org/jira/browse/YARN-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522964#comment-14522964 ] Hadoop QA commented on YARN-3534: - (!) The patch artifact directory has been removed! This

[jira] [Commented] (YARN-1462) AHS API and other AHS changes to handle tags for completed MR jobs

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

[jira] [Commented] (YARN-3564) Fix TestContainerAllocation.testAMContainerAllocationWhenDNSUnavailable fails randomly

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

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

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

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

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

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3564) Fix TestContainerAllocation.testAMContainerAllocationWhenDNSUnavailable fails randomly

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

[jira] [Updated] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

[ https://issues.apache.org/jira/browse/YARN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-3521: -- Attachment: 0003-YARN-3521.patch Thank you [~leftnoteasy] for the comments. I am uploading now an interim patch

[jira] [Updated] (YARN-868) YarnClient should set the service address in tokens returned by getRMDelegationToken()

[ https://issues.apache.org/jira/browse/YARN-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-868: Target Version/s: 2.8.0 (was: 2.6.0) > YarnClient should set the service address in tokens returned by > get

[jira] [Commented] (YARN-868) YarnClient should set the service address in tokens returned by getRMDelegationToken()

[ https://issues.apache.org/jira/browse/YARN-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523070#comment-14523070 ] Junping Du commented on YARN-868: - [~hitesh] and [~varun_saxena], can you provide some backg

[jira] [Commented] (YARN-880) Configuring map/reduce memory equal to nodemanager's memory, hangs the job execution

[ https://issues.apache.org/jira/browse/YARN-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523073#comment-14523073 ] Junping Du commented on YARN-880: - This sounds like a wrong configuration problem. If you ha

[jira] [Resolved] (YARN-880) Configuring map/reduce memory equal to nodemanager's memory, hangs the job execution

[ https://issues.apache.org/jira/browse/YARN-880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-880. - Resolution: Not A Problem Assignee: (was: Omkar Vinit Joshi) > Configuring map/reduce memory equal

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

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

[jira] [Updated] (YARN-882) Specify per user quota for private/application cache and user log files

[ https://issues.apache.org/jira/browse/YARN-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-882: Target Version/s: 2.8.0 Issue Type: New Feature (was: Bug) > Specify per user quota for private/app

[jira] [Commented] (YARN-3564) Fix TestContainerAllocation.testAMContainerAllocationWhenDNSUnavailable fails randomly

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

[jira] [Commented] (YARN-3564) Fix TestContainerAllocation.testAMContainerAllocationWhenDNSUnavailable fails randomly

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

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

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

[jira] [Commented] (YARN-885) TestBinaryTokenFile (and others) fail

[ https://issues.apache.org/jira/browse/YARN-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523100#comment-14523100 ] Junping Du commented on YARN-885: - Just tried it again. Cannot reproduce the failure. Let's

[jira] [Commented] (YARN-868) YarnClient should set the service address in tokens returned by getRMDelegationToken()

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

[jira] [Commented] (YARN-886) make APPLICATION_STOP consistent with APPLICATION_INIT

[ https://issues.apache.org/jira/browse/YARN-886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523125#comment-14523125 ] Junping Du commented on YARN-886: - Hi [~sseth], I just quickly check the current code base a

[jira] [Updated] (YARN-887) WebAppProxyServlet should not create HttpClient object for each request

[ https://issues.apache.org/jira/browse/YARN-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-887: Component/s: webapp > WebAppProxyServlet should not create HttpClient object for each request > --

[jira] [Commented] (YARN-3521) Support return structured NodeLabel objects in REST API when call getClusterNodeLabels

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

[jira] [Commented] (YARN-900) YarnClientApplication uses composition to hold GetNewApplicationResponse instead of having a simpler flattened structure

[ https://issues.apache.org/jira/browse/YARN-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523148#comment-14523148 ] Junping Du commented on YARN-900: - Shouldn't be incompatible change if only deprecated GetNe

[jira] [Commented] (YARN-907) MRAppMaster failed to initialize second attempt when first attempt is FAILED.

[ https://issues.apache.org/jira/browse/YARN-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523149#comment-14523149 ] Junping Du commented on YARN-907: - Should be fixed in MAPREDUCE-5476. Resolve it so far as c

[jira] [Resolved] (YARN-907) MRAppMaster failed to initialize second attempt when first attempt is FAILED.

[ https://issues.apache.org/jira/browse/YARN-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-907. - Resolution: Cannot Reproduce > MRAppMaster failed to initialize second attempt when first attempt is FAILED.

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

[ https://issues.apache.org/jira/browse/YARN-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-914: Target Version/s: 2.8.0 (was: ) > (Umbrella) Support graceful decommission of nodemanager > -

[jira] [Updated] (YARN-913) Umbrella: Add a way to register long-lived services in a YARN cluster

[ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-913: Target Version/s: 2.8.0 (was: 2.6.0) > Umbrella: Add a way to register long-lived services in a YARN cluster

[jira] [Commented] (YARN-908) URL is a YARN API record instead of being java.net.url

[ https://issues.apache.org/jira/browse/YARN-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523157#comment-14523157 ] Junping Du commented on YARN-908: - Agree. It should be serialized as PB object. [~bikassaha]

[jira] [Commented] (YARN-931) Overlapping classes across hadoop-yarn-api and hadoop-yarn-common

[ https://issues.apache.org/jira/browse/YARN-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523173#comment-14523173 ] Junping Du commented on YARN-931: - I suspect it could be unnecessary for some of these packa

[jira] [Commented] (YARN-943) RM starts 2 attempts of failed app even though am-max-retries is set to 1

[ https://issues.apache.org/jira/browse/YARN-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523182#comment-14523182 ] Junping Du commented on YARN-943: - Aha~ This is probably because "yarn.resourcemanager.am.ma

[jira] [Resolved] (YARN-943) RM starts 2 attempts of failed app even though am-max-retries is set to 1

[ https://issues.apache.org/jira/browse/YARN-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-943. - Resolution: Not A Problem Assignee: (was: Zhijie Shen) > RM starts 2 attempts of failed app even t

[jira] [Commented] (YARN-3243) CapacityScheduler should pass headroom from parent to children to make sure ParentQueue obey its capacity limits.

[ https://issues.apache.org/jira/browse/YARN-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523187#comment-14523187 ] Thomas Graves commented on YARN-3243: - thanks [~leftnoteasy] I'll attempt to merge YARN

[jira] [Updated] (YARN-3243) CapacityScheduler should pass headroom from parent to children to make sure ParentQueue obey its capacity limits.

[ https://issues.apache.org/jira/browse/YARN-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-3243: Fix Version/s: 2.7.1 > CapacityScheduler should pass headroom from parent to children to make sure >

[jira] [Assigned] (YARN-3562) unit tests fail with the failure to bring up node manager

[ https://issues.apache.org/jira/browse/YARN-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-3562: --- Assignee: Naganarasimha G R > unit tests fail with the failure to bring up node manage

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

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

[jira] [Commented] (YARN-3134) [Storage implementation] Exploiting the option of using Phoenix to access HBase backend

[ https://issues.apache.org/jira/browse/YARN-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523303#comment-14523303 ] Junping Du commented on YARN-3134: -- Thanks [~gtCarrera9] for updating the patch! Some com

[jira] [Commented] (YARN-3564) Fix TestContainerAllocation.testAMContainerAllocationWhenDNSUnavailable fails randomly

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

[jira] [Updated] (YARN-944) App failed with container launch failed even though container started

[ https://issues.apache.org/jira/browse/YARN-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-944: Assignee: Jian He (was: Omkar Vinit Joshi) > App failed with container launch failed even though container st

[jira] [Commented] (YARN-2619) NodeManager: Add cgroups support for disk I/O isolation

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

[jira] [Commented] (YARN-3544) AM logs link missing in the RM UI for a completed app

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

[jira] [Commented] (YARN-3564) Fix TestContainerAllocation.testAMContainerAllocationWhenDNSUnavailable fails randomly

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

[jira] [Commented] (YARN-944) App failed with container launch failed even though container started

[ https://issues.apache.org/jira/browse/YARN-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523347#comment-14523347 ] Junping Du commented on YARN-944: - [~jianhe], we have improved diagnostics info a lot since

[jira] [Updated] (YARN-950) Ability to limit or avoid aggregating logs beyond a certain size

[ https://issues.apache.org/jira/browse/YARN-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-950: Affects Version/s: 2.6.0 > Ability to limit or avoid aggregating logs beyond a certain size >

[jira] [Commented] (YARN-950) Ability to limit or avoid aggregating logs beyond a certain size

[ https://issues.apache.org/jira/browse/YARN-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523363#comment-14523363 ] Junping Du commented on YARN-950: - +1 on the idea of limiting the size of log aggregation. W

[jira] [Commented] (YARN-958) NM may miss a heartbeat response from RM resulting into missed finished applications information.

[ https://issues.apache.org/jira/browse/YARN-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523389#comment-14523389 ] Junping Du commented on YARN-958: - Sounds like the problem is still valid. Shall we delay to

[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-tabpanel&focusedCommentId=14523390#comment-14523390 ] Naganarasimha G R commented on YARN-3044: - Hi [~vinodkv], bq. But it's really about

[jira] [Commented] (YARN-3271) FairScheduler: Move tests related to max-runnable-apps from TestFairScheduler to TestAppRunnability

[ https://issues.apache.org/jira/browse/YARN-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523393#comment-14523393 ] Karthik Kambatla commented on YARN-3271: In TestAppRunnability, # tearDown need no

[jira] [Commented] (YARN-908) URL is a YARN API record instead of being java.net.url

[ https://issues.apache.org/jira/browse/YARN-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523396#comment-14523396 ] Bikas Saha commented on YARN-908: - The issue is why not use standard java URL instead of YAR

[jira] [Commented] (YARN-900) YarnClientApplication uses composition to hold GetNewApplicationResponse instead of having a simpler flattened structure

[ https://issues.apache.org/jira/browse/YARN-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523409#comment-14523409 ] Hitesh Shah commented on YARN-900: -- Probably too late to make this change now due to compat

[jira] [Updated] (YARN-959) Add ApplicationAttemptId into container environment

[ https://issues.apache.org/jira/browse/YARN-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-959: Affects Version/s: 2.6.0 > Add ApplicationAttemptId into container environment > -

[jira] [Commented] (YARN-959) Add ApplicationAttemptId into container environment

[ https://issues.apache.org/jira/browse/YARN-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523414#comment-14523414 ] Junping Du commented on YARN-959: - It sounds cleaner if we expose ApplicationAttemptId direc

[jira] [Updated] (YARN-959) Add ApplicationAttemptId into container environment

[ https://issues.apache.org/jira/browse/YARN-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-959: Target Version/s: 2.8.0 > Add ApplicationAttemptId into container environment > --

[jira] [Assigned] (YARN-959) Add ApplicationAttemptId into container environment

[ https://issues.apache.org/jira/browse/YARN-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du reassigned YARN-959: --- Assignee: Junping Du > Add ApplicationAttemptId into container environment > --

[jira] [Commented] (YARN-2021) Allow AM to set failed final status

[ https://issues.apache.org/jira/browse/YARN-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523458#comment-14523458 ] Zhijie Shen commented on YARN-2021: --- AM can report FinalApplicationStatus#FAILED when unr

[jira] [Resolved] (YARN-964) Give a parameter that can set AM retry interval

[ https://issues.apache.org/jira/browse/YARN-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-964. - Resolution: Won't Fix Agree with [~vinodkv]. Resolve this as won't fix. > Give a parameter that can set AM

[jira] [Resolved] (YARN-2021) Allow AM to set failed final status

[ https://issues.apache.org/jira/browse/YARN-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-2021. --- Resolution: Invalid > Allow AM to set failed final status > --- > >

[jira] [Updated] (YARN-2024) IOException in AppLogAggregatorImpl does not give stacktrace and leaves aggregated TFile in a bad state.

[ https://issues.apache.org/jira/browse/YARN-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2024: -- Target Version/s: 2.8.0 (was: 2.4.1) > IOException in AppLogAggregatorImpl does not give stacktrace and

[jira] [Commented] (YARN-3366) Outbound network bandwidth : classify/shape traffic originating from YARN containers

[ https://issues.apache.org/jira/browse/YARN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523471#comment-14523471 ] Sidharta Seethana commented on YARN-3366: - [~hex108] , The goal here is to allocate

[jira] [Assigned] (YARN-2024) IOException in AppLogAggregatorImpl does not give stacktrace and leaves aggregated TFile in a bad state.

[ https://issues.apache.org/jira/browse/YARN-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong reassigned YARN-2024: --- Assignee: Xuan Gong > IOException in AppLogAggregatorImpl does not give stacktrace and leaves > aggre

[jira] [Updated] (YARN-3069) Document missing properties in yarn-default.xml

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Lu updated YARN-3069: Component/s: documentation > Document missing properties in yarn-default.xml > --

[jira] [Updated] (YARN-2200) Rename related container start time to container creation time

[ https://issues.apache.org/jira/browse/YARN-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2200: -- Target Version/s: (was: 2.6.0) > Rename related container start time to container creation time > -

[jira] [Commented] (YARN-2200) Rename related container start time to container creation time

[ https://issues.apache.org/jira/browse/YARN-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523565#comment-14523565 ] Zhijie Shen commented on YARN-2200: --- Remove it from 2.6.0, which is already released. >

[jira] [Commented] (YARN-2333) RM UI : show pending containers at cluster level in the application/scheduler page

[ https://issues.apache.org/jira/browse/YARN-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523566#comment-14523566 ] Junping Du commented on YARN-2333: -- Thanks [~ashwinshankar77] for reporting this issue. Do

[jira] [Commented] (YARN-1050) Document the Fair Scheduler REST API

[ https://issues.apache.org/jira/browse/YARN-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523575#comment-14523575 ] Xuan Gong commented on YARN-1050: - [~kasha] Could you review this, please ? > Document the

[jira] [Updated] (YARN-2835) YARN WebApps should be a public API

[ https://issues.apache.org/jira/browse/YARN-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2835: - Target Version/s: 2.8.0 (was: 2.6.0) > YARN WebApps should be a public API > -

[jira] [Commented] (YARN-2199) FairScheduler: Allow max-AM-share to be specified in the root queue

[ https://issues.apache.org/jira/browse/YARN-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523583#comment-14523583 ] Zhijie Shen commented on YARN-2199: --- Remove it from 2.6.0, which is already released. >

[jira] [Updated] (YARN-2199) FairScheduler: Allow max-AM-share to be specified in the root queue

[ https://issues.apache.org/jira/browse/YARN-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2199: -- Issue Type: Improvement (was: Bug) > FairScheduler: Allow max-AM-share to be specified in the root queue

[jira] [Updated] (YARN-2334) Document exit codes and their meanings used by LinuxContainerExecutor.

[ https://issues.apache.org/jira/browse/YARN-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2334: - Summary: Document exit codes and their meanings used by LinuxContainerExecutor. (was: Document exit codes

[jira] [Commented] (YARN-2844) WebAppProxyServlet cannot handle urls which contain encoded characters

[ https://issues.apache.org/jira/browse/YARN-2844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523596#comment-14523596 ] Wangda Tan commented on YARN-2844: -- [~zsxwing], patch is not applied, could you update ple

[jira] [Resolved] (YARN-2916) MiniYARNCluster should support enabling Timeline and new services via config

[ https://issues.apache.org/jira/browse/YARN-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-2916. --- Resolution: Duplicate > MiniYARNCluster should support enabling Timeline and new services via config >

[jira] [Updated] (YARN-2839) YARN minicluster doesn't bail out if all the NM disks are dead

[ https://issues.apache.org/jira/browse/YARN-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2839: - Affects Version/s: (was: 2.6.0) 2.8.0 > YARN minicluster doesn't bail out if all

[jira] [Updated] (YARN-2199) FairScheduler: Allow max-AM-share to be specified in the root queue

[ https://issues.apache.org/jira/browse/YARN-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2199: -- Target Version/s: (was: 2.6.0) > FairScheduler: Allow max-AM-share to be specified in the root queue >

[jira] [Commented] (YARN-2839) YARN minicluster doesn't bail out if all the NM disks are dead

[ https://issues.apache.org/jira/browse/YARN-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523579#comment-14523579 ] Wangda Tan commented on YARN-2839: -- Moved to 2.8 > YARN minicluster doesn't bail out if a

[jira] [Updated] (YARN-2334) Document exit codes and their meanings used by linux task controller.

[ https://issues.apache.org/jira/browse/YARN-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2334: - Summary: Document exit codes and their meanings used by linux task controller. (was: Document exit codes a

[jira] [Commented] (YARN-2833) Timeline Domains should be immutable by default

[ https://issues.apache.org/jira/browse/YARN-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523602#comment-14523602 ] Hitesh Shah commented on YARN-2833: --- [~zjshen] Is there any thinking of how acls will wor

[jira] [Commented] (YARN-2840) Timeline should support creation of Domains where domainId is not provided by the user

[ https://issues.apache.org/jira/browse/YARN-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523603#comment-14523603 ] Hitesh Shah commented on YARN-2840: --- [~zjshen] Is there any thinking of how acls will wor

[jira] [Commented] (YARN-2199) FairScheduler: Allow max-AM-share to be specified in the root queue

[ https://issues.apache.org/jira/browse/YARN-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523605#comment-14523605 ] Zhijie Shen commented on YARN-2199: --- Take a quick look at the patch, it seems to be a goo

[jira] [Commented] (YARN-2845) MicroZookeeperService used in Yarn Registry tests doesn't shut down cleanly on windows

[ https://issues.apache.org/jira/browse/YARN-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523604#comment-14523604 ] Wangda Tan commented on YARN-2845: -- [~ste...@apache.org], is the problem still existed? Pl

[jira] [Updated] (YARN-867) Isolation of failures in aux services

[ https://issues.apache.org/jira/browse/YARN-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-867: - Target Version/s: 2.8.0 (was: 2.3.0) > Isolation of failures in aux services > ---

[jira] [Resolved] (YARN-900) YarnClientApplication uses composition to hold GetNewApplicationResponse instead of having a simpler flattened structure

[ https://issues.apache.org/jira/browse/YARN-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-900. -- Resolution: Not A Problem > YarnClientApplication uses composition to hold GetNewApplicationResponse > in

[jira] [Created] (YARN-3567) Document exit codes and their meanings used by LinuxContainerExecutor.

Junping Du created YARN-3567: Summary: Document exit codes and their meanings used by LinuxContainerExecutor. Key: YARN-3567 URL: https://issues.apache.org/jira/browse/YARN-3567 Project: Hadoop YARN

[jira] [Commented] (YARN-2202) Metrics recovery for nodemanager restart

[ https://issues.apache.org/jira/browse/YARN-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523610#comment-14523610 ] Zhijie Shen commented on YARN-2202: --- YARN-1341 is resolved, we we have any plan for this

[jira] [Updated] (YARN-1052) Enforce submit application queue ACLs outside the scheduler

[ https://issues.apache.org/jira/browse/YARN-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-1052: Target Version/s: 2.8.0 > Enforce submit application queue ACLs outside the scheduler > -

[jira] [Resolved] (YARN-971) hadoop-yarn-api pom does not define a dependencies tag

[ https://issues.apache.org/jira/browse/YARN-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah resolved YARN-971. -- Resolution: Duplicate > hadoop-yarn-api pom does not define a dependencies tag > -

[jira] [Updated] (YARN-931) Overlapping classes across hadoop-yarn-api and hadoop-yarn-common

[ https://issues.apache.org/jira/browse/YARN-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-931: - Target Version/s: (was: 2.1.0-beta) > Overlapping classes across hadoop-yarn-api and hadoop-yarn-common >

  1   2   3   4   5   6   >