[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW may make some application level resource be not cleaned

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: YARN-7563.txt > Invalid event: FINISH_APPLICATION at NEW may make some application level > resource be

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW may make some application level resource be not cleaned

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: (was: YARN-7563.txt) > Invalid event: FINISH_APPLICATION at NEW may make some application level >

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW may make some application level resource be not cleaned

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: YARN-7563.txt > Invalid event: FINISH_APPLICATION at NEW may make some application level > resource be

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW may make some application level resource be not cleaned

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Summary: Invalid event: FINISH_APPLICATION at NEW may make some application level resource be not cleaned (was:

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW may

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Summary: Invalid event: FINISH_APPLICATION at NEW may (was: Invalid event: FINISH_APPLICATION at NEW) > Invalid

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Affects Version/s: 2.6.0 > Invalid event: FINISH_APPLICATION at NEW > > >

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268199#comment-16268199 ] Wilfred Spiegelenburg commented on YARN-7562: - The behaviour you are seeing is the correct

[jira] [Created] (YARN-7572) Make the service status output more readable

Jian He created YARN-7572: - Summary: Make the service status output more readable Key: YARN-7572 URL: https://issues.apache.org/jira/browse/YARN-7572 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-7564) Fix checkstyle issues of YARN-5881 branch

[ https://issues.apache.org/jira/browse/YARN-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268150#comment-16268150 ] Wangda Tan commented on YARN-7564: -- +1 to latest patch, thanks [~sunilg] > Fix checkstyle issues of

[jira] [Commented] (YARN-7562) queuePlacementPolicy should not match parent queue

[ https://issues.apache.org/jira/browse/YARN-7562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268118#comment-16268118 ] genericqa commented on YARN-7562: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-7491) Make sure AM is not scheduled on an opportunistic container

[ https://issues.apache.org/jira/browse/YARN-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268065#comment-16268065 ] Haibo Chen commented on YARN-7491: -- That's because of this {code} @@ -491,7 +491,7 @@ private RMAppImpl

[jira] [Commented] (YARN-6124) Make SchedulingEditPolicy can be enabled / disabled / updated with RMAdmin -refreshQueues

[ https://issues.apache.org/jira/browse/YARN-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16268040#comment-16268040 ] genericqa commented on YARN-6124: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6669) Support security for YARN service framework

[ https://issues.apache.org/jira/browse/YARN-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267999#comment-16267999 ] genericqa commented on YARN-6669: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Comment Edited] (YARN-7229) Add a metric for the size of event queue in AsyncDispatcher

[ https://issues.apache.org/jira/browse/YARN-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267978#comment-16267978 ] sandflee edited comment on YARN-7229 at 11/28/17 2:30 AM: -- yes, planed to add this

[jira] [Commented] (YARN-7229) Add a metric for the size of event queue in AsyncDispatcher

[ https://issues.apache.org/jira/browse/YARN-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267978#comment-16267978 ] sandflee commented on YARN-7229: yes, planed to add this to our cluster, assign this to myself > Add a

[jira] [Issue Comment Deleted] (YARN-7535) We should display origin value of demand in fair scheduler page

[ https://issues.apache.org/jira/browse/YARN-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuekang updated YARN-7535: -- Comment: was deleted (was: I understand that a queue cannot use more resource than its max resources, but

[jira] [Commented] (YARN-6669) Support security for YARN service framework

[ https://issues.apache.org/jira/browse/YARN-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267972#comment-16267972 ] genericqa commented on YARN-6669: - | (/) *{color:green}+1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-6124) Make SchedulingEditPolicy can be enabled / disabled / updated with RMAdmin -refreshQueues

[ https://issues.apache.org/jira/browse/YARN-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267950#comment-16267950 ] Zian Chen commented on YARN-6124: - Hi [~leftnoteasy] , thanks for the comments, I fixed the failed test

[jira] [Commented] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267945#comment-16267945 ] genericqa commented on YARN-7558: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-6124) Make SchedulingEditPolicy can be enabled / disabled / updated with RMAdmin -refreshQueues

[ https://issues.apache.org/jira/browse/YARN-6124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zian Chen updated YARN-6124: Attachment: YARN-6124.4.patch > Make SchedulingEditPolicy can be enabled / disabled / updated with RMAdmin

[jira] [Updated] (YARN-6669) Support security for YARN service framework

[ https://issues.apache.org/jira/browse/YARN-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-6669: -- Attachment: YARN-6669.07.patch fixed some check style issues, and made client to throw explicit exception if it

[jira] [Commented] (YARN-7541) Node updates don't update the maximum cluster capability for resources other than CPU and memory

[ https://issues.apache.org/jira/browse/YARN-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267925#comment-16267925 ] Yufei Gu commented on YARN-7541: +1 for patch v5. Please fix the style issue before commit. > Node

[jira] [Commented] (YARN-7491) Make sure AM is not scheduled on an opportunistic container

[ https://issues.apache.org/jira/browse/YARN-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267920#comment-16267920 ] Miklos Szegedi commented on YARN-7491: -- I reverted the AM request line in the patch to the following:

[jira] [Created] (YARN-7571) YARN has multiple Queue Configuration Providers

Xuan Gong created YARN-7571: --- Summary: YARN has multiple Queue Configuration Providers Key: YARN-7571 URL: https://issues.apache.org/jira/browse/YARN-7571 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-6669) Support security for YARN service framework

[ https://issues.apache.org/jira/browse/YARN-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-6669: -- Attachment: (was: YARN-6669.07.patch) > Support security for YARN service framework >

[jira] [Updated] (YARN-6669) Support security for YARN service framework

[ https://issues.apache.org/jira/browse/YARN-6669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-6669: -- Attachment: YARN-6669.07.patch > Support security for YARN service framework >

[jira] [Commented] (YARN-6731) Add ability to export scheduler configuration XML

[ https://issues.apache.org/jira/browse/YARN-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267876#comment-16267876 ] genericqa commented on YARN-6731: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Created] (YARN-7570) Merge Scheduler configuration Store and ZK RM State Store

Xuan Gong created YARN-7570: --- Summary: Merge Scheduler configuration Store and ZK RM State Store Key: YARN-7570 URL: https://issues.apache.org/jira/browse/YARN-7570 Project: Hadoop YARN Issue

[jira] [Created] (YARN-7569) Add ability to dump and upload scheduler configuration XML

Xuan Gong created YARN-7569: --- Summary: Add ability to dump and upload scheduler configuration XML Key: YARN-7569 URL: https://issues.apache.org/jira/browse/YARN-7569 Project: Hadoop YARN Issue

[jira] [Created] (YARN-7568) Add audit log for add/remove queues

Xuan Gong created YARN-7568: --- Summary: Add audit log for add/remove queues Key: YARN-7568 URL: https://issues.apache.org/jira/browse/YARN-7568 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-7567) Make sure that OrgQueue works in secure ZK environment

[ https://issues.apache.org/jira/browse/YARN-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-7567: Description: In YARN-5734, we introduced OrgQueue for easy CapacityScheduler queue management. And we are

[jira] [Updated] (YARN-7567) Make sure that OrgQueue works in secure ZK environment

[ https://issues.apache.org/jira/browse/YARN-7567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-7567: Description: In YARN-5734, we introduced > Make sure that OrgQueue works in secure ZK environment >

[jira] [Created] (YARN-7567) Make sure that OrgQueue works in secure ZK environment

Xuan Gong created YARN-7567: --- Summary: Make sure that OrgQueue works in secure ZK environment Key: YARN-7567 URL: https://issues.apache.org/jira/browse/YARN-7567 Project: Hadoop YARN Issue Type:

[jira] [Created] (YARN-7566) [Umbrella] More improvements on YARN Queue Management

Xuan Gong created YARN-7566: --- Summary: [Umbrella] More improvements on YARN Queue Management Key: YARN-7566 URL: https://issues.apache.org/jira/browse/YARN-7566 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267837#comment-16267837 ] Xuan Gong commented on YARN-7558: - Fix the checkstyle issue. The testcase failure is not related > "yarn

[jira] [Updated] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-7558: Attachment: YARN-7558.2.patch > "yarn logs" command fails to get logs for running containers if UI >

[jira] [Commented] (YARN-7491) Make sure AM is not scheduled on an opportunistic container

[ https://issues.apache.org/jira/browse/YARN-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267819#comment-16267819 ] Haibo Chen commented on YARN-7491: -- Thanks for the review [~miklos.szeg...@cloudera.com]! I think it is

[jira] [Comment Edited] (YARN-7363) ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267740#comment-16267740 ] Yufei Gu edited comment on YARN-7363 at 11/27/17 10:56 PM: --- Uploaded the branch-2

[jira] [Updated] (YARN-7363) ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-7363: --- Fix Version/s: 2.10.0 > ContainerLocalizer doesn't have a valid log4j config when using >

[jira] [Updated] (YARN-7363) ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-7363: --- Attachment: YARN-7363.branch-2.001.patch Uploaded the branch-2 version. There is a minor conflict. >

[jira] [Commented] (YARN-7363) ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267737#comment-16267737 ] Hudson commented on YARN-7363: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13280 (See

[jira] [Commented] (YARN-7363) ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267717#comment-16267717 ] Yufei Gu commented on YARN-7363: Committed to trunk and branch-3.0. Thanks for the review,

[jira] [Updated] (YARN-7363) ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Chiang updated YARN-7363: - Summary: ContainerLocalizer doesn't have a valid log4j config when using LinuxContainerExecutor (was:

[jira] [Comment Edited] (YARN-7561) Why hasContainerForNode() return false directly when there is no request of ANY locality without considering NODE_LOCAL and RACK_LOCAL?

[ https://issues.apache.org/jira/browse/YARN-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266564#comment-16266564 ] Yufei Gu edited comment on YARN-7561 at 11/27/17 10:30 PM: --- You might need to

[jira] [Commented] (YARN-7491) Make sure AM is not scheduled on an opportunistic container

[ https://issues.apache.org/jira/browse/YARN-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267702#comment-16267702 ] Miklos Szegedi commented on YARN-7491: -- Thank you for the patch [~haibochen]. Even though there are

[jira] [Commented] (YARN-7363) ContainerLocalizer don't have a valid log4j config in case of Linux container executor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267618#comment-16267618 ] Ray Chiang commented on YARN-7363: -- Looks good to me [~yufeigu]. +1 (binding) pending Jenkins. I'll

[jira] [Commented] (YARN-7363) ContainerLocalizer don't have a valid log4j config in case of Linux container executor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267597#comment-16267597 ] genericqa commented on YARN-7363: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267518#comment-16267518 ] genericqa commented on YARN-7558: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-7564) Fix checkstyle issues of YARN-5881 branch

[ https://issues.apache.org/jira/browse/YARN-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267440#comment-16267440 ] genericqa commented on YARN-7564: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-7509) AsyncScheduleThread and ResourceCommitterService are still running after RM is transitioned to standby

[ https://issues.apache.org/jira/browse/YARN-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267425#comment-16267425 ] Subru Krishnan commented on YARN-7509: -- [~leftnoteasy], the fix version says 2.9.1 but it has not been

[jira] [Commented] (YARN-7541) Node updates don't update the maximum cluster capability for resources other than CPU and memory

[ https://issues.apache.org/jira/browse/YARN-7541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267397#comment-16267397 ] genericqa commented on YARN-7541: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-7558: Reporter: Namit Maheshwari (was: Xuan Gong) > "yarn logs" command fails to get logs for running containers

[jira] [Commented] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267364#comment-16267364 ] Xuan Gong commented on YARN-7558: - Test the patch in secure/un-secure environment, and it fixes the issue

[jira] [Updated] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuan Gong updated YARN-7558: Attachment: YARN-7558.1.patch > "yarn logs" command fails to get logs for running containers if UI >

[jira] [Updated] (YARN-7363) ContainerLocalizer don't have a valid log4j config in case of Linux container executor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yufei Gu updated YARN-7363: --- Attachment: YARN-7363.005.patch Thanks for the review, [~rchiang]. Uploaded patch v5 for your comments. >

[jira] [Commented] (YARN-7473) Implement Framework and policy for capacity management of auto created queues

[ https://issues.apache.org/jira/browse/YARN-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267317#comment-16267317 ] Wangda Tan commented on YARN-7473: -- Thanks [~suma.shivaprasad], majorly reviewed configs and

[jira] [Commented] (YARN-6483) Add nodes transitioning to DECOMMISSIONING state to the list of updated nodes returned to the AM

[ https://issues.apache.org/jira/browse/YARN-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267314#comment-16267314 ] ASF GitHub Bot commented on YARN-6483: -- Github user juanrh commented on the issue:

[jira] [Commented] (YARN-6483) Add nodes transitioning to DECOMMISSIONING state to the list of updated nodes returned to the AM

[ https://issues.apache.org/jira/browse/YARN-6483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267316#comment-16267316 ] ASF GitHub Bot commented on YARN-6483: -- Github user juanrh closed the pull request at:

[jira] [Comment Edited] (YARN-7363) ContainerLocalizer don't have a valid log4j config in case of Linux container executor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267274#comment-16267274 ] Ray Chiang edited comment on YARN-7363 at 11/27/17 7:08 PM: Minor nit: * The

[jira] [Commented] (YARN-7473) Implement Framework and policy for capacity management of auto created queues

[ https://issues.apache.org/jira/browse/YARN-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267277#comment-16267277 ] genericqa commented on YARN-7473: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Commented] (YARN-7363) ContainerLocalizer don't have a valid log4j config in case of Linux container executor

[ https://issues.apache.org/jira/browse/YARN-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267274#comment-16267274 ] Ray Chiang commented on YARN-7363: -- Minor nit: The yarn.nodemanager.container-localizer.log.level property

[jira] [Commented] (YARN-7495) Improve robustness of the AggregatedLogDeletionService

[ https://issues.apache.org/jira/browse/YARN-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267235#comment-16267235 ] Jason Lowe commented on YARN-7495: -- Thanks for updating the patch! It would be good to address the

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267224#comment-16267224 ] Hudson commented on YARN-6168: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13279 (See

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267191#comment-16267191 ] Chandni Singh commented on YARN-6168: - Thanks [~jianhe] > Restarted RM may not inform AM about all

[jira] [Created] (YARN-7565) Yarn service pre-maturely releases the container after AM restart

Chandni Singh created YARN-7565: --- Summary: Yarn service pre-maturely releases the container after AM restart Key: YARN-7565 URL: https://issues.apache.org/jira/browse/YARN-7565 Project: Hadoop YARN

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267181#comment-16267181 ] Jian He commented on YARN-6168: --- I committed this into trunk. Thanks [~csingh] ! > Restarted RM may not

[jira] [Commented] (YARN-6168) Restarted RM may not inform AM about all existing containers

[ https://issues.apache.org/jira/browse/YARN-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267173#comment-16267173 ] Chandni Singh commented on YARN-6168: - Test and findbug failure are not related to the change >

[jira] [Updated] (YARN-7558) "yarn logs" command fails to get logs for running containers if UI authentication is enabled.

[ https://issues.apache.org/jira/browse/YARN-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-7558: -- Priority: Critical (was: Major) Summary: "yarn logs" command fails to get

[jira] [Updated] (YARN-7564) Fix checkstyle issues of YARN-5881 branch

[ https://issues.apache.org/jira/browse/YARN-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sunil G updated YARN-7564: -- Attachment: YARN-7564-YARN-5881.001.patch Attaching patch addressing this issue. cc/[~leftnoteasy] > Fix

[jira] [Created] (YARN-7564) Fix checkstyle issues of YARN-5881 branch

Sunil G created YARN-7564: - Summary: Fix checkstyle issues of YARN-5881 branch Key: YARN-7564 URL: https://issues.apache.org/jira/browse/YARN-7564 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-7473) Implement Framework and policy for capacity management of auto created queues

[ https://issues.apache.org/jira/browse/YARN-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-7473: --- Attachment: YARN-7473.9.patch > Implement Framework and policy for capacity management of auto

[jira] [Updated] (YARN-7473) Implement Framework and policy for capacity management of auto created queues

[ https://issues.apache.org/jira/browse/YARN-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-7473: --- Attachment: (was: YARN-7394.9.patch) > Implement Framework and policy for capacity

[jira] [Updated] (YARN-7473) Implement Framework and policy for capacity management of auto created queues

[ https://issues.apache.org/jira/browse/YARN-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-7473: --- Attachment: YARN-7394.9.patch Fixed signature for

[jira] [Commented] (YARN-7213) [Umbrella] Test and validate HBase-2.0.x with Atsv2

[ https://issues.apache.org/jira/browse/YARN-7213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16267009#comment-16267009 ] Rohith Sharma K S commented on YARN-7213: - thanks [~haibo.chen] and other HBase folks for detailed

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:10 PM: --- I have find the reason by

[jira] [Issue Comment Deleted] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Comment: was deleted (was: !YARN-7563.png!) > Invalid event: FINISH_APPLICATION at NEW >

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:09 PM: --- I have find the reason by

[jira] [Commented] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266994#comment-16266994 ] lujie commented on YARN-7563: - !YARN-7563.png! > Invalid event: FINISH_APPLICATION at NEW >

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:08 PM: --- I have find the reason by

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:07 PM: --- I have find the reason by

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: YARN-7563.png > Invalid event: FINISH_APPLICATION at NEW > > >

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: (was: YARN-7536.png) > Invalid event: FINISH_APPLICATION at NEW >

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:06 PM: --- I have find the reason by

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: YARN-7536.png > Invalid event: FINISH_APPLICATION at NEW > > >

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:05 PM: --- I have find the reason by

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:04 PM: --- I have find the reason by

[jira] [Comment Edited] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie edited comment on YARN-7563 at 11/27/17 4:03 PM: --- I have find the reason by

[jira] [Commented] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266987#comment-16266987 ] lujie commented on YARN-7563: - I have find the reason by analysis code and logs !YARN-7536.png! above figure

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: (was: YARN-7536.png) > Invalid event: FINISH_APPLICATION at NEW >

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: (was: YARN-7563.png) > Invalid event: FINISH_APPLICATION at NEW >

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: YARN-7536.png > Invalid event: FINISH_APPLICATION at NEW > > >

[jira] [Commented] (YARN-7473) Implement Framework and policy for capacity management of auto created queues

[ https://issues.apache.org/jira/browse/YARN-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266974#comment-16266974 ] genericqa commented on YARN-7473: - | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem ||

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: screenshot-1.png > Invalid event: FINISH_APPLICATION at NEW > >

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: (was: screenshot-1.png) > Invalid event: FINISH_APPLICATION at NEW >

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Attachment: YARN-7563.png > Invalid event: FINISH_APPLICATION at NEW > > >

[jira] [Commented] (YARN-7497) Add HDFSSchedulerConfigurationStore for RM HA

[ https://issues.apache.org/jira/browse/YARN-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266947#comment-16266947 ] Greg Phillips commented on YARN-7497: - [~yangjiandan] - Would it make sense to move the two

[jira] [Updated] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

[ https://issues.apache.org/jira/browse/YARN-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-7563: Description: I send kill command to application, nodemanager log shows: {code:java} 2017-11-25 19:18:48,126 WARN

[jira] [Updated] (YARN-7473) Implement Framework and policy for capacity management of auto created queues

[ https://issues.apache.org/jira/browse/YARN-7473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated YARN-7473: --- Attachment: YARN-7473.8.patch Fixed license, findbugs and javac issues > Implement Framework

[jira] [Created] (YARN-7563) Invalid event: FINISH_APPLICATION at NEW

lujie created YARN-7563: --- Summary: Invalid event: FINISH_APPLICATION at NEW Key: YARN-7563 URL: https://issues.apache.org/jira/browse/YARN-7563 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-7535) We should display origin value of demand in fair scheduler page

[ https://issues.apache.org/jira/browse/YARN-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266791#comment-16266791 ] Wilfred Spiegelenburg commented on YARN-7535: - The demand for an application is not limited and

  1   2   >