[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14544988#comment-14544988 ] Rohith commented on YARN-3646: -- Setting RetryPolicies.RETRY_FOREVER for exceptionToPolicyMap

[jira] [Updated] (YARN-3653) Expose the scheduler's KPI in web UI

[ https://issues.apache.org/jira/browse/YARN-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3653: -- Component/s: webapp Expose the scheduler's KPI in web UI

[jira] [Commented] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

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

[jira] [Created] (YARN-3651) Tracking url in ApplicaitonCLI wrong for running application

Bibin A Chundatt created YARN-3651: -- Summary: Tracking url in ApplicaitonCLI wrong for running application Key: YARN-3651 URL: https://issues.apache.org/jira/browse/YARN-3651 Project: Hadoop YARN

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545188#comment-14545188 ] Xianyin Xin commented on YARN-3630: --- Thanks, [~leftnoteasy] and [~kasha]. [~leftnoteasy],

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

[ https://issues.apache.org/jira/browse/YARN-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545097#comment-14545097 ] Akira AJISAKA commented on YARN-3069: - Thanks [~rchiang] for the update. Looked the

[jira] [Updated] (YARN-3651) Tracking url in ApplicationCLI wrong for running application

[ https://issues.apache.org/jira/browse/YARN-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3651: --- Summary: Tracking url in ApplicationCLI wrong for running application (was: Tracking url in

[jira] [Updated] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3547: -- Attachment: YARN-3547.005.patch A patch using {{getDemand() - getResourceUsage()}}. FairScheduler:

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545218#comment-14545218 ] Sunil G commented on YARN-3630: --- bq.Are we considering automatically slowing down the NM

[jira] [Commented] (YARN-3583) Support of NodeLabel object instead of plain String in YarnClient side.

[ https://issues.apache.org/jira/browse/YARN-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545131#comment-14545131 ] Sunil G commented on YARN-3583: --- bq.Inconsistent synchronization of

[jira] [Commented] (YARN-3547) FairScheduler: Apps that have no resource demand should not participate scheduling

[ https://issues.apache.org/jira/browse/YARN-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14544995#comment-14544995 ] Xianyin Xin commented on YARN-3547: --- [~kasha], can you please have a look?

[jira] [Updated] (YARN-3652) A SchedulerMetrics may be need for evaluating the scheduler's performance

[ https://issues.apache.org/jira/browse/YARN-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianyin Xin updated YARN-3652: -- Summary: A SchedulerMetrics may be need for evaluating the scheduler's performance (was: A

[jira] [Created] (YARN-3652) A {{SchedulerMetrics}} may be need for evaluating the scheduler's performance

Xianyin Xin created YARN-3652: - Summary: A {{SchedulerMetrics}} may be need for evaluating the scheduler's performance Key: YARN-3652 URL: https://issues.apache.org/jira/browse/YARN-3652 Project: Hadoop

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545219#comment-14545219 ] Sunil G commented on YARN-3630: --- bq.Are we considering automatically slowing down the NM

[jira] [Created] (YARN-3653) Expose the scheduler's KPI in web UI

Xianyin Xin created YARN-3653: - Summary: Expose the scheduler's KPI in web UI Key: YARN-3653 URL: https://issues.apache.org/jira/browse/YARN-3653 Project: Hadoop YARN Issue Type: Improvement

[jira] [Updated] (YARN-3651) Tracking url in ApplicationCLI wrong for running application

[ https://issues.apache.org/jira/browse/YARN-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3651: --- Description: Application URL in Application CLI wrong Steps to reproduce

[jira] [Commented] (YARN-3630) YARN should suggest a heartbeat interval for applications

[ https://issues.apache.org/jira/browse/YARN-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545225#comment-14545225 ] Sunil G commented on YARN-3630: --- bq.Are we considering automatically slowing down the NM

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545264#comment-14545264 ] Devaraj K commented on YARN-3646: - You can probably avoid this situation by setting a

[jira] [Commented] (YARN-3651) Tracking url in ApplicationCLI wrong for running application

[ https://issues.apache.org/jira/browse/YARN-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545353#comment-14545353 ] Bibin A Chundatt commented on YARN-3651: Also when configured as HTTPS_ONLY why

[jira] [Commented] (YARN-3652) A SchedulerMetrics may be need for evaluating the scheduler's performance

[ https://issues.apache.org/jira/browse/YARN-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545260#comment-14545260 ] Sunil G commented on YARN-3652: --- Hi [~xinxianyin] This will be a very helpful feature and

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

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

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545410#comment-14545410 ] Hudson commented on YARN-3505: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #197 (See

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

[ https://issues.apache.org/jira/browse/YARN-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545415#comment-14545415 ] Hudson commented on YARN-1519: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #197 (See

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545250#comment-14545250 ] Lavkesh Lahngir commented on YARN-3591: --- What about zombie files lying in the various

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Updated] (YARN-3605) _ as method name may not be supported much longer

[ https://issues.apache.org/jira/browse/YARN-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated YARN-3605: -- Labels: newbie (was: ) _ as method name may not be supported much longer

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Commented] (YARN-624) Support gang scheduling in the AM RM protocol

[ https://issues.apache.org/jira/browse/YARN-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545486#comment-14545486 ] john lilley commented on YARN-624: -- I would like to +1 this feature, and illustrate our use

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545548#comment-14545548 ] Srikanth Sundarrajan commented on YARN-3646: {quote} You can probably avoid

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

[ https://issues.apache.org/jira/browse/YARN-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545710#comment-14545710 ] Hudson commented on YARN-3505: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #196 (See

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

[ https://issues.apache.org/jira/browse/YARN-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545715#comment-14545715 ] Hudson commented on YARN-1519: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #196 (See

[jira] [Commented] (YARN-3646) Applications are getting stuck some times in case of retry policy forever

[ https://issues.apache.org/jira/browse/YARN-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545702#comment-14545702 ] Devaraj K commented on YARN-3646: - bq. Would this not cause the client to wait for too long

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

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

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Updated] (YARN-2421) RM still allocates containers to an app in the FINISHING state

[ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2421: - Summary: RM still allocates containers to an app in the FINISHING state (was: CapacityScheduler still

[jira] [Commented] (YARN-3609) Move load labels from storage from serviceInit to serviceStart to make it works with RM HA case.

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

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546374#comment-14546374 ] Craig Welch commented on YARN-3626: --- Right, going back to [~cnauroth], [~vinodkv], we

[jira] [Updated] (YARN-3659) Federation Router (hiding multiple RMs for ApplicationClientProtocol)

[ https://issues.apache.org/jira/browse/YARN-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3659: - Description: This JIRA tracks the design/implementation of the layer for routing

[jira] [Created] (YARN-3661) Federation UI

Giovanni Matteo Fumarola created YARN-3661: -- Summary: Federation UI Key: YARN-3661 URL: https://issues.apache.org/jira/browse/YARN-3661 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-3561) Non-AM Containers continue to run even after AM is stopped

[ https://issues.apache.org/jira/browse/YARN-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546454#comment-14546454 ] Gour Saha commented on YARN-3561: - [~jianhe] it is consistently reproducible on debian 7.

[jira] [Assigned] (YARN-3659) Federation Router (hiding multiple RMs for ApplicationClientProtocol)

[ https://issues.apache.org/jira/browse/YARN-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola reassigned YARN-3659: -- Assignee: Giovanni Matteo Fumarola Federation Router (hiding multiple

[jira] [Commented] (YARN-3654) ContainerLogsPage web UI should not have meta-refresh

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

[jira] [Commented] (YARN-2421) CapacityScheduler still allocates containers to an app in the FINISHING state

[ https://issues.apache.org/jira/browse/YARN-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546254#comment-14546254 ] Jason Lowe commented on YARN-2421: -- +1 latest patch lgtm. Committing this.

[jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

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

[jira] [Commented] (YARN-2421) RM still allocates containers to an app in the FINISHING state

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

[jira] [Updated] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3632: -- Attachment: YARN-3632.5.patch Ordering policy should be allowed to reorder an application when demand

[jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546271#comment-14546271 ] Craig Welch commented on YARN-3632: --- One line change to address missing whitespace issue.

[jira] [Commented] (YARN-2268) Disallow formatting the RMStateStore when there is an RM running

[ https://issues.apache.org/jira/browse/YARN-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546296#comment-14546296 ] Jian He commented on YARN-2268: --- I think the lock file solution only suits zk-store, not for

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

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

[jira] [Created] (YARN-3656) LowCost: A Cost-Based Placement Agent for YARN Reservations

Ishai Menache created YARN-3656: --- Summary: LowCost: A Cost-Based Placement Agent for YARN Reservations Key: YARN-3656 URL: https://issues.apache.org/jira/browse/YARN-3656 Project: Hadoop YARN

[jira] [Updated] (YARN-3656) LowCost: A Cost-Based Placement Agent for YARN Reservations

[ https://issues.apache.org/jira/browse/YARN-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishai Menache updated YARN-3656: Attachment: LowCostRayonExternal.pdf This tech-report summarizes the details of LowCost, as well as

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546365#comment-14546365 ] Chris Nauroth commented on YARN-3626: - I don't fully understand the objection to the

[jira] [Commented] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546377#comment-14546377 ] Bikas Saha commented on YARN-1902: -- The AMRMClient was not written to automatically remove

[jira] [Commented] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546421#comment-14546421 ] Bikas Saha commented on YARN-1902: -- Yes. And then the RM may give a container on H1 which

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546420#comment-14546420 ] zhihai xu commented on YARN-3655: - I uploaded a patch YARN-3655.000.patch for review.

[jira] [Created] (YARN-3662) Federation StateStore APIs

Subru Krishnan created YARN-3662: Summary: Federation StateStore APIs Key: YARN-3662 URL: https://issues.apache.org/jira/browse/YARN-3662 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-3663) Federation State and Policy Store (DBMS implementation)

Giovanni Matteo Fumarola created YARN-3663: -- Summary: Federation State and Policy Store (DBMS implementation) Key: YARN-3663 URL: https://issues.apache.org/jira/browse/YARN-3663 Project:

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546461#comment-14546461 ] zhihai xu commented on YARN-3591: - [~vinodkv], yes, keeping the ownership of turning disks

[jira] [Updated] (YARN-3666) Federation Intercepting and propagating AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishore Chaliparambil updated YARN-3666: External issue ID: (was: YARN-2884) Federation Intercepting and propagating AM-RM

[jira] [Commented] (YARN-3591) Resource Localisation on a bad disk causes subsequent containers failure

[ https://issues.apache.org/jira/browse/YARN-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546213#comment-14546213 ] Vinod Kumar Vavilapalli commented on YARN-3591: --- Essentially keeping the

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546288#comment-14546288 ] Craig Welch commented on YARN-3626: --- [~cnauroth], [~vvasudev] - This patch goes back to

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546359#comment-14546359 ] Vinod Kumar Vavilapalli commented on YARN-3626: --- bq. We may have to depend on

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546370#comment-14546370 ] Craig Welch commented on YARN-3626: --- bq. Can't we do the above? We definitely cannot

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546393#comment-14546393 ] Vinod Kumar Vavilapalli commented on YARN-3626: --- bq. I thought this

[jira] [Commented] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546400#comment-14546400 ] Chris Nauroth commented on YARN-3626: - I see now. Thanks for the clarification. In

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Attachment: YARN-3655.000.patch FairScheduler: potential livelock due to maxAMShare limitation and

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3655: Description: FairScheduler: potential livelock due to maxAMShare limitation and container reservation. If a

[jira] [Updated] (YARN-3659) Federation Router (hiding multiple RMs for ApplicationClientProtocol)

[ https://issues.apache.org/jira/browse/YARN-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola updated YARN-3659: --- Description: This JIRA tracks the design/implementation of the layer for

[jira] [Created] (YARN-3660) Federation Global Policy Generator (load balancing)

Carlo Curino created YARN-3660: -- Summary: Federation Global Policy Generator (load balancing) Key: YARN-3660 URL: https://issues.apache.org/jira/browse/YARN-3660 Project: Hadoop YARN Issue

[jira] [Created] (YARN-3659) Federation Router (hiding multiple RMs for ApplicationSubmissionProtocol)

Giovanni Matteo Fumarola created YARN-3659: -- Summary: Federation Router (hiding multiple RMs for ApplicationSubmissionProtocol) Key: YARN-3659 URL: https://issues.apache.org/jira/browse/YARN-3659

[jira] [Updated] (YARN-3659) Federation Router (hiding multiple RMs for ApplicationClientProtocol)

[ https://issues.apache.org/jira/browse/YARN-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-3659: - Summary: Federation Router (hiding multiple RMs for ApplicationClientProtocol) (was: Federation

[jira] [Assigned] (YARN-3664) Federation PolicyStore APIs

[ https://issues.apache.org/jira/browse/YARN-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan reassigned YARN-3664: Assignee: Subru Krishnan Federation PolicyStore APIs ---

[jira] [Created] (YARN-3665) Federation subcluster membership mechanisms

Subru Krishnan created YARN-3665: Summary: Federation subcluster membership mechanisms Key: YARN-3665 URL: https://issues.apache.org/jira/browse/YARN-3665 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-3663) Federation State and Policy Store (DBMS implementation)

[ https://issues.apache.org/jira/browse/YARN-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola reassigned YARN-3663: -- Assignee: Giovanni Matteo Fumarola Federation State and Policy Store

[jira] [Assigned] (YARN-3661) Federation UI

[ https://issues.apache.org/jira/browse/YARN-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giovanni Matteo Fumarola reassigned YARN-3661: -- Assignee: Giovanni Matteo Fumarola Federation UI --

[jira] [Assigned] (YARN-3666) Federation Intercepting and propagating AM-RM communications

[ https://issues.apache.org/jira/browse/YARN-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishore Chaliparambil reassigned YARN-3666: --- Assignee: Kishore Chaliparambil Federation Intercepting and propagating

[jira] [Commented] (YARN-3561) Non-AM Containers continue to run even after AM is stopped

[ https://issues.apache.org/jira/browse/YARN-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546278#comment-14546278 ] Jian He commented on YARN-3561: --- [~gsaha], from the description, this is running against 2.6

[jira] [Updated] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

[ https://issues.apache.org/jira/browse/YARN-3655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karthik Kambatla updated YARN-3655: --- Summary: FairScheduler: potential livelock due to maxAMShare limitation and container

[jira] [Commented] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546391#comment-14546391 ] Vinod Kumar Vavilapalli commented on YARN-1902: --- This was discussed multiple

[jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

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

[jira] [Created] (YARN-3664) Federation PolicyStore APIs

Subru Krishnan created YARN-3664: Summary: Federation PolicyStore APIs Key: YARN-3664 URL: https://issues.apache.org/jira/browse/YARN-3664 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-3666) Federation Intercepting and propagating AM-RM communications

Kishore Chaliparambil created YARN-3666: --- Summary: Federation Intercepting and propagating AM-RM communications Key: YARN-3666 URL: https://issues.apache.org/jira/browse/YARN-3666 Project:

[jira] [Commented] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546209#comment-14546209 ] MENG DING commented on YARN-1902: - I was almost going to log the same issue when I saw this

[jira] [Updated] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3626: -- Attachment: YARN-3626.9.patch In that case, here's a patch which goes back to the original approach used

[jira] [Commented] (YARN-3656) LowCost: A Cost-Based Placement Agent for YARN Reservations

[ https://issues.apache.org/jira/browse/YARN-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546361#comment-14546361 ] Ishai Menache commented on YARN-3656: - LowCost judiciously “spreads” the demand of the

[jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes

[ https://issues.apache.org/jira/browse/YARN-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546403#comment-14546403 ] Craig Welch commented on YARN-3632: --- findbugs and javac appear to be irrelevant...

[jira] [Commented] (YARN-1902) Allocation of too many containers when a second request is done with the same resource capability

[ https://issues.apache.org/jira/browse/YARN-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546418#comment-14546418 ] Vinod Kumar Vavilapalli commented on YARN-1902: --- bq. Wangda Tan mentioned

[jira] [Created] (YARN-3657) Federation maintenance mechanisms (simple CLI and command propagation)

Carlo Curino created YARN-3657: -- Summary: Federation maintenance mechanisms (simple CLI and command propagation) Key: YARN-3657 URL: https://issues.apache.org/jira/browse/YARN-3657 Project: Hadoop YARN

[jira] [Created] (YARN-3658) Federation Capacity Allocation across sub-cluster

Carlo Curino created YARN-3658: -- Summary: Federation Capacity Allocation across sub-cluster Key: YARN-3658 URL: https://issues.apache.org/jira/browse/YARN-3658 Project: Hadoop YARN Issue Type:

[jira] [Assigned] (YARN-3665) Federation subcluster membership mechanisms

[ https://issues.apache.org/jira/browse/YARN-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan reassigned YARN-3665: Assignee: Subru Krishnan Federation subcluster membership mechanisms

[jira] [Commented] (YARN-3656) LowCost: A Cost-Based Placement Agent for YARN Reservations

[ https://issues.apache.org/jira/browse/YARN-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546467#comment-14546467 ] Carlo Curino commented on YARN-3656: I worked with Ishai and Jonathan closely on this,

[jira] [Commented] (YARN-3652) A SchedulerMetrics may be need for evaluating the scheduler's performance

[ https://issues.apache.org/jira/browse/YARN-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14545607#comment-14545607 ] Xianyin Xin commented on YARN-3652: --- Thanks for comments, [~sunilg]. {quote} 1.

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

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

[jira] [Commented] (YARN-3505) Node's Log Aggregation Report with SUCCEED should not cached in RMApps

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

[jira] [Commented] (YARN-1519) check if sysconf is implemented before using it

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

[jira] [Updated] (YARN-2915) Enable YARN RM scale out via federation using multiple RM's

[ https://issues.apache.org/jira/browse/YARN-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Subru Krishnan updated YARN-2915: - Attachment: Yarn_federation_design_v1.pdf Uploading a proposal of design based on offline design

[jira] [Commented] (YARN-3655) FairScheduler: potential livelock due to maxAMShare limitation and container reservation

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

[jira] [Updated] (YARN-3626) On Windows localized resources are not moved to the front of the classpath when they should be

[ https://issues.apache.org/jira/browse/YARN-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Craig Welch updated YARN-3626: -- Attachment: YARN-3626.11.patch Now using the environment to pass the configuration. On Windows

[jira] [Updated] (YARN-3565) NodeHeartbeatRequest/RegisterNodeManagerRequest should use NodeLabel object instead of String

[ https://issues.apache.org/jira/browse/YARN-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R updated YARN-3565: Attachment: YARN-3565.20150516-1.patch Hi [~wangda], Uploading a patch with fixing

  1   2   >