[jira] [Commented] (YARN-2088) Fix code bug in GetApplicationsRequestPBImpl#mergeLocalToBuilder

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

[jira] [Commented] (YARN-2030) Use StateMachine to simplify handleStoreEvent() in RMStateStore

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

[jira] [Commented] (YARN-1962) Timeline server is enabled by default

[ https://issues.apache.org/jira/browse/YARN-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006871#comment-14006871 ] Hudson commented on YARN-1962: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1781 (See

[jira] [Commented] (YARN-2017) Merge some of the common lib code in schedulers

[ https://issues.apache.org/jira/browse/YARN-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006870#comment-14006870 ] Hudson commented on YARN-2017: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1781 (See

[jira] [Commented] (YARN-2081) TestDistributedShell fails after YARN-1962

[ https://issues.apache.org/jira/browse/YARN-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006866#comment-14006866 ] Hudson commented on YARN-2081: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1781 (See

[jira] [Commented] (YARN-1938) Kerberos authentication for the timeline server

[ https://issues.apache.org/jira/browse/YARN-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006874#comment-14006874 ] Hudson commented on YARN-1938: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1781 (See

[jira] [Commented] (YARN-2050) Fix LogCLIHelpers to create the correct FileContext

[ https://issues.apache.org/jira/browse/YARN-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006867#comment-14006867 ] Hudson commented on YARN-2050: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1781 (See

[jira] [Commented] (YARN-2089) FairScheduler: QueuePlacementPolicy and QueuePlacementRule are missing audience annotations

[ https://issues.apache.org/jira/browse/YARN-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006869#comment-14006869 ] Hudson commented on YARN-2089: -- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1781 (See

[jira] [Commented] (YARN-1962) Timeline server is enabled by default

[ https://issues.apache.org/jira/browse/YARN-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006893#comment-14006893 ] Hudson commented on YARN-1962: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1755 (See

[jira] [Commented] (YARN-2089) FairScheduler: QueuePlacementPolicy and QueuePlacementRule are missing audience annotations

[ https://issues.apache.org/jira/browse/YARN-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006891#comment-14006891 ] Hudson commented on YARN-2089: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1755 (See

[jira] [Commented] (YARN-2081) TestDistributedShell fails after YARN-1962

[ https://issues.apache.org/jira/browse/YARN-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006888#comment-14006888 ] Hudson commented on YARN-2081: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1755 (See

[jira] [Commented] (YARN-2050) Fix LogCLIHelpers to create the correct FileContext

[ https://issues.apache.org/jira/browse/YARN-2050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006889#comment-14006889 ] Hudson commented on YARN-2050: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1755 (See

[jira] [Commented] (YARN-1938) Kerberos authentication for the timeline server

[ https://issues.apache.org/jira/browse/YARN-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006896#comment-14006896 ] Hudson commented on YARN-1938: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1755 (See

[jira] [Commented] (YARN-2017) Merge some of the common lib code in schedulers

[ https://issues.apache.org/jira/browse/YARN-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006892#comment-14006892 ] Hudson commented on YARN-2017: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #1755 (See

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006908#comment-14006908 ] Sunil G commented on YARN-1408: --- bq. we may change it to decrement the resource request only

[jira] [Created] (YARN-2096) testQueueMetricsOnRMRestart has race condition

Anubhav Dhoot created YARN-2096: --- Summary: testQueueMetricsOnRMRestart has race condition Key: YARN-2096 URL: https://issues.apache.org/jira/browse/YARN-2096 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-2096) testQueueMetricsOnRMRestart has race condition

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot reassigned YARN-2096: --- Assignee: Anubhav Dhoot testQueueMetricsOnRMRestart has race condition

[jira] [Updated] (YARN-2096) testQueueMetricsOnRMRestart has race condition

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anubhav Dhoot updated YARN-2096: Attachment: YARN-2096.patch Fixed 2 race conditions by First one) waiting for appropriate

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

[ https://issues.apache.org/jira/browse/YARN-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14006938#comment-14006938 ] Zhijie Shen commented on YARN-1937: --- bq. A meta comment - may be this isn't a RESTy way

[jira] [Updated] (YARN-2059) Extend access control for admin acls

[ https://issues.apache.org/jira/browse/YARN-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2059: -- Summary: Extend access control for admin acls (was: Extend access control for admin and configured

[jira] [Updated] (YARN-2059) Extend access control for admin acls

[ https://issues.apache.org/jira/browse/YARN-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2059: -- Target Version/s: 2.5.0 Extend access control for admin acls

[jira] [Updated] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Tian updated YARN-2083: -- Attachment: YARN-2083.patch Add testcase for this issue In fair scheduler, Queue should not been assigned

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007024#comment-14007024 ] Rohith commented on YARN-1365: -- Hi Anubhav, One comment on the patch. * Notifying to

[jira] [Updated] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith updated YARN-1366: - Attachment: YARN-1366.3.patch I updated patch with below changes. bq. Pending releases - AM forgets about a

[jira] [Commented] (YARN-1408) Preemption caused Invalid State Event: ACQUIRED at KILLED and caused a task timeout for 30mins

[ https://issues.apache.org/jira/browse/YARN-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007148#comment-14007148 ] Wangda Tan commented on YARN-1408: -- I think container should be preempt-able when its in

[jira] [Commented] (YARN-2092) Incompatible org.codehaus.jackson* dependencies when moving from 2.4.0 to 2.5.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007269#comment-14007269 ] Steve Loughran commented on YARN-2092: -- I think this should be a wontfix, as the

[jira] [Commented] (YARN-2092) Incompatible org.codehaus.jackson* dependencies when moving from 2.4.0 to 2.5.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007281#comment-14007281 ] Sangjin Lee commented on YARN-2092: --- +1 on exploring the OSGi option. Until/unless it

[jira] [Commented] (YARN-2092) Incompatible org.codehaus.jackson* dependencies when moving from 2.4.0 to 2.5.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007284#comment-14007284 ] Sangjin Lee commented on YARN-2092: --- ... user code or any code that needs to run in

[jira] [Commented] (YARN-2092) Incompatible org.codehaus.jackson* dependencies when moving from 2.4.0 to 2.5.0-SNAPSHOT

[ https://issues.apache.org/jira/browse/YARN-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007291#comment-14007291 ] Hitesh Shah commented on YARN-2092: --- Isolating apps is just one aspect. The bigger issue

[jira] [Updated] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-2096: --- Summary: Race in TestRMRestart#testQueueMetricsOnRMRestart (was: testQueueMetricsOnRMRestart

[jira] [Updated] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-596: - Attachment: YARN-596.patch Update a new patch to fix Sandy's suggestions. In fair scheduler, intra-application

[jira] [Commented] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007319#comment-14007319 ] Tsuyoshi OZAWA commented on YARN-2096: -- Thank you for taking this JIRA, Anubhav. I

[jira] [Commented] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007338#comment-14007338 ] Karthik Kambatla commented on YARN-2096: Looks good to me. +1. Race in

[jira] [Comment Edited] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007338#comment-14007338 ] Karthik Kambatla edited comment on YARN-2096 at 5/23/14 4:41 PM:

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007358#comment-14007358 ] Tsuyoshi OZAWA commented on YARN-1365: -- Hi [~rohithsharma], can you clarify us the

[jira] [Commented] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

[ https://issues.apache.org/jira/browse/YARN-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007363#comment-14007363 ] Tsuyoshi OZAWA commented on YARN-2096: -- The change looks good to me too(non-binding).

[jira] [Commented] (YARN-2049) Delegation token stuff for the timeline sever

[ https://issues.apache.org/jira/browse/YARN-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007385#comment-14007385 ] Vinod Kumar Vavilapalli commented on YARN-2049: --- +1, looks good. Checking

[jira] [Commented] (YARN-2049) Delegation token stuff for the timeline sever

[ https://issues.apache.org/jira/browse/YARN-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007397#comment-14007397 ] Varun Vasudev commented on YARN-2049: - +1, patch look good. Delegation token stuff

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

[ https://issues.apache.org/jira/browse/YARN-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007414#comment-14007414 ] Varun Vasudev commented on YARN-1937: - +1 on the latest patch. Add entity-level

[jira] [Commented] (YARN-2096) Race in TestRMRestart#testQueueMetricsOnRMRestart

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

[jira] [Commented] (YARN-1936) Secured timeline client

[ https://issues.apache.org/jira/browse/YARN-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007426#comment-14007426 ] Vinod Kumar Vavilapalli commented on YARN-1936: --- +1, this looks good. Will

[jira] [Commented] (YARN-1936) Secured timeline client

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

[jira] [Commented] (YARN-1936) Secured timeline client

[ https://issues.apache.org/jira/browse/YARN-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007472#comment-14007472 ] Zhijie Shen commented on YARN-1936: --- Again, the test failure is not related. Secured

[jira] [Commented] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007485#comment-14007485 ] Ivan Mitic commented on YARN-1063: -- I have already reviewed a version of the initial patch

[jira] [Commented] (YARN-1063) Winutils needs ability to create task as domain user

[ https://issues.apache.org/jira/browse/YARN-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007490#comment-14007490 ] Ivan Mitic commented on YARN-1063: -- Thanks Remus for addressing all comments in the latest

[jira] [Commented] (YARN-1936) Secured timeline client

[ https://issues.apache.org/jira/browse/YARN-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007534#comment-14007534 ] Zhijie Shen commented on YARN-1936: --- Also did some validation for the new client patch on

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

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

[jira] [Commented] (YARN-2070) DistributedShell publishes unfriendly user information to the timeline server

[ https://issues.apache.org/jira/browse/YARN-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007558#comment-14007558 ] Vinod Kumar Vavilapalli commented on YARN-2070: --- Given that, should we

[jira] [Created] (YARN-2097) Documentation: health check return status

Allen Wittenauer created YARN-2097: -- Summary: Documentation: health check return status Key: YARN-2097 URL: https://issues.apache.org/jira/browse/YARN-2097 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2082) Support for alternative log aggregation mechanism

[ https://issues.apache.org/jira/browse/YARN-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007562#comment-14007562 ] Ming Ma commented on YARN-2082: --- Folks, thanks for the feedbacks and other jiras; quite

[jira] [Updated] (YARN-2097) Documentation: health check return status

[ https://issues.apache.org/jira/browse/YARN-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer updated YARN-2097: --- Component/s: nodemanager Documentation: health check return status

[jira] [Updated] (YARN-2075) TestRMAdminCLI consistently fail on trunk

[ https://issues.apache.org/jira/browse/YARN-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-2075: -- Affects Version/s: 2.5.0 3.0.0 TestRMAdminCLI consistently fail on trunk

[jira] [Updated] (YARN-1937) Add entity-level access control of the timeline data for owners only

[ https://issues.apache.org/jira/browse/YARN-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-1937: -- Attachment: YARN-1937.5.patch Fix the conflicts Add entity-level access control of the timeline data

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

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

[jira] [Commented] (YARN-2090) If Kerberos Authentication is enabled, MapReduce job is failing on reducer phase

[ https://issues.apache.org/jira/browse/YARN-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007603#comment-14007603 ] Victor Kim commented on YARN-2090: -- I figured out when\where it happens. If you use

[jira] [Commented] (YARN-2081) TestDistributedShell fails after YARN-1962

[ https://issues.apache.org/jira/browse/YARN-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007605#comment-14007605 ] Hudson commented on YARN-2081: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5608 (See

[jira] [Commented] (YARN-2089) FairScheduler: QueuePlacementPolicy and QueuePlacementRule are missing audience annotations

[ https://issues.apache.org/jira/browse/YARN-2089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007607#comment-14007607 ] Hudson commented on YARN-2089: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5608 (See

[jira] [Commented] (YARN-1936) Secured timeline client

[ https://issues.apache.org/jira/browse/YARN-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007612#comment-14007612 ] Hudson commented on YARN-1936: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5608 (See

[jira] [Commented] (YARN-1962) Timeline server is enabled by default

[ https://issues.apache.org/jira/browse/YARN-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007609#comment-14007609 ] Hudson commented on YARN-1962: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5608 (See

[jira] [Commented] (YARN-2049) Delegation token stuff for the timeline sever

[ https://issues.apache.org/jira/browse/YARN-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007610#comment-14007610 ] Hudson commented on YARN-2049: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5608 (See

[jira] [Commented] (YARN-2017) Merge some of the common lib code in schedulers

[ https://issues.apache.org/jira/browse/YARN-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007608#comment-14007608 ] Hudson commented on YARN-2017: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5608 (See

[jira] [Updated] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2026: - Attachment: YARN-2026-v1.txt Fair scheduler : Fair share for inactive queues causes unfair

[jira] [Commented] (YARN-1938) Kerberos authentication for the timeline server

[ https://issues.apache.org/jira/browse/YARN-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007613#comment-14007613 ] Hudson commented on YARN-1938: -- SUCCESS: Integrated in Hadoop-trunk-Commit #5608 (See

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

[ https://issues.apache.org/jira/browse/YARN-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007635#comment-14007635 ] Ashwin Shankar commented on YARN-2026: -- Attached patch addresses this issue by setting

[jira] [Commented] (YARN-2070) DistributedShell publishes unfriendly user information to the timeline server

[ https://issues.apache.org/jira/browse/YARN-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007640#comment-14007640 ] Zhijie Shen commented on YARN-2070: --- The situation here is that users are free to define

[jira] [Commented] (YARN-2059) Extend access control for admin acls

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

[jira] [Commented] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

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

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

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

[jira] [Commented] (YARN-2088) Fix code bug in GetApplicationsRequestPBImpl#mergeLocalToBuilder

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

[jira] [Commented] (YARN-1474) Make schedulers services

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

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

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

[jira] [Created] (YARN-2098) App priority support in Fair Scheduler

Ashwin Shankar created YARN-2098: Summary: App priority support in Fair Scheduler Key: YARN-2098 URL: https://issues.apache.org/jira/browse/YARN-2098 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

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

[jira] [Updated] (YARN-2098) App priority support in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2098: - Description: This jira is for supporting app priorities in fair schduler. AppSchedulable hard

[jira] [Updated] (YARN-2098) App priority support in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2098: - Description: This jira is created for supporting app priorities in fair scheduler.

[jira] [Updated] (YARN-2098) App priority support in Fair Scheduler

[ https://issues.apache.org/jira/browse/YARN-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2098: - Description: This jira is for supporting app priorities in fair scheduler. AppSchedulable hard

[jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests

[ https://issues.apache.org/jira/browse/YARN-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007698#comment-14007698 ] Jian Fang commented on YARN-796: I like to add a use case to this JIRA. In a cloud

[jira] [Created] (YARN-2099) Preemption in fair scheduler should consider app priorities

Ashwin Shankar created YARN-2099: Summary: Preemption in fair scheduler should consider app priorities Key: YARN-2099 URL: https://issues.apache.org/jira/browse/YARN-2099 Project: Hadoop YARN

[jira] [Commented] (YARN-1366) ApplicationMasterService should Resync with the AM upon allocate call after restart

[ https://issues.apache.org/jira/browse/YARN-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007703#comment-14007703 ] Anubhav Dhoot commented on YARN-1366: - Looks good overall, some minor comments below

[jira] [Updated] (YARN-2012) Fair Scheduler : Default rule in queue placement policy can take a queue as an optional attribute

[ https://issues.apache.org/jira/browse/YARN-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashwin Shankar updated YARN-2012: - Attachment: YARN-2012-v3.txt Fair Scheduler : Default rule in queue placement policy can take a

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

[ https://issues.apache.org/jira/browse/YARN-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007715#comment-14007715 ] Vinod Kumar Vavilapalli commented on YARN-1937: --- +1, looks good. Checking

[jira] [Commented] (YARN-2073) FairScheduler starts preempting resources even with free resources on the cluster

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

[jira] [Updated] (YARN-2097) Documentation: health check return status

[ https://issues.apache.org/jira/browse/YARN-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated YARN-2097: -- Attachment: YARN-2097.1.patch Attached patch doc as per NodeHealthMonitorExecutor.reportStatus().

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

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

[jira] [Updated] (YARN-1427) yarn-env.cmd should have the analog comments that are in yarn-env.sh

[ https://issues.apache.org/jira/browse/YARN-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rekha Joshi updated YARN-1427: -- Attachment: YARN-1427.1.patch Attached patch.Thanks yarn-env.cmd should have the analog comments that

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

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

[jira] [Commented] (YARN-1365) ApplicationMasterService to allow Register and Unregister of an app that was running before restart

[ https://issues.apache.org/jira/browse/YARN-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007768#comment-14007768 ] Anubhav Dhoot commented on YARN-1365: - The error is RMAppRecoveredTransition leaves it

[jira] [Commented] (YARN-1216) Deprecate/ mark private few methods from YarnConfiguration

[ https://issues.apache.org/jira/browse/YARN-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007766#comment-14007766 ] Rekha Joshi commented on YARN-1216: --- Needs to be closed.Existing

[jira] [Updated] (YARN-596) In fair scheduler, intra-application container priorities affect inter-application preemption decisions

[ https://issues.apache.org/jira/browse/YARN-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wei Yan updated YARN-596: - Attachment: YARN-596.patch In fair scheduler, intra-application container priorities affect inter-application

[jira] [Commented] (YARN-1474) Make schedulers services

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

[jira] [Commented] (YARN-2095) Large MapReduce Job stops responding

[ https://issues.apache.org/jira/browse/YARN-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007779#comment-14007779 ] Clay McDonald commented on YARN-2095: - Vinod, could you read Eric's email below. Would

[jira] [Commented] (YARN-2059) Extend access control for admin acls

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

[jira] [Created] (YARN-2100) Refactor the code of Kerberos + DT authentication

Zhijie Shen created YARN-2100: - Summary: Refactor the code of Kerberos + DT authentication Key: YARN-2100 URL: https://issues.apache.org/jira/browse/YARN-2100 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2083) In fair scheduler, Queue should not been assigned more containers when its usedResource had reach the maxResource limit

[ https://issues.apache.org/jira/browse/YARN-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007786#comment-14007786 ] Sandy Ryza commented on YARN-2083: -- I think it would be better to solve this by making

[jira] [Commented] (YARN-2026) Fair scheduler : Fair share for inactive queues causes unfair allocation in some scenarios

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

[jira] [Commented] (YARN-2099) Preemption in fair scheduler should consider app priorities

[ https://issues.apache.org/jira/browse/YARN-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007789#comment-14007789 ] Wei Yan commented on YARN-2099: --- Hi, Ashwin. We have discussed a little bit about the

[jira] [Created] (YARN-2101) Document the system filters of the timeline entity

Zhijie Shen created YARN-2101: - Summary: Document the system filters of the timeline entity Key: YARN-2101 URL: https://issues.apache.org/jira/browse/YARN-2101 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-2012) Fair Scheduler : Default rule in queue placement policy can take a queue as an optional attribute

[ https://issues.apache.org/jira/browse/YARN-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007797#comment-14007797 ] Sandy Ryza commented on YARN-2012: -- +1 Fair Scheduler : Default rule in queue placement

[jira] [Commented] (YARN-1937) Add entity-level access control of the timeline data for owners only

[ https://issues.apache.org/jira/browse/YARN-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14007800#comment-14007800 ] Zhijie Shen commented on YARN-1937: --- Tested the timeline security stack so far end-to-end

[jira] [Updated] (YARN-2012) Fair Scheduler: allow default queue placement rule to take an arbitrary queue

[ https://issues.apache.org/jira/browse/YARN-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandy Ryza updated YARN-2012: - Summary: Fair Scheduler: allow default queue placement rule to take an arbitrary queue (was: Fair

  1   2   >