[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-tabpanel&focusedCommentId=14545097#comment-14545097 ] Akira AJISAKA commented on YARN-3069: - Thanks [~rchiang] for the update. Looked the pat

[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-tabpanel&focusedCommentId=14545101#comment-14545101 ] Hadoop QA commented on YARN-3583: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14545131#comment-14545131 ] Sunil G commented on YARN-3583: --- bq.Inconsistent synchronization of org.apache.hadoop.yarn.s

[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] [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 Ap

[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 Y

[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 {{SchedulerMe

[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-tabpanel&focusedCommentId=14545188#comment-14545188 ] Xianyin Xin commented on YARN-3630: --- Thanks, [~leftnoteasy] and [~kasha]. [~leftnoteasy],

[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-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-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-tabpanel&focusedCommentId=14545219#comment-14545219 ] Sunil G commented on YARN-3630: --- bq.Are we considering automatically slowing down the NM hear

[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-tabpanel&focusedCommentId=14545218#comment-14545218 ] Sunil G commented on YARN-3630: --- bq.Are we considering automatically slowing down the NM hear

[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-tabpanel&focusedCommentId=14545225#comment-14545225 ] Sunil G commented on YARN-3630: --- bq.Are we considering automatically slowing down the NM hear

[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-tabpanel&focusedCommentId=14545250#comment-14545250 ] Lavkesh Lahngir commented on YARN-3591: --- What about zombie files lying in the various

[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-tabpanel&focusedCommentId=14545260#comment-14545260 ] Sunil G commented on YARN-3652: --- Hi [~xinxianyin] This will be a very helpful feature and tha

[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-tabpanel&focusedCommentId=14545264#comment-14545264 ] Devaraj K commented on YARN-3646: - You can probably avoid this situation by setting a bigge

[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-tabpanel&focusedCommentId=14545353#comment-14545353 ] Bibin A Chundatt commented on YARN-3651: Also when configured as HTTPS_ONLY why htt

[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-tabpanel&focusedCommentId=14545387#comment-14545387 ] Hudson commented on YARN-3505: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #928 (See [https://b

[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-tabpanel&focusedCommentId=14545392#comment-14545392 ] Hudson commented on YARN-1519: -- SUCCESS: Integrated in Hadoop-Yarn-trunk #928 (See [https://b

[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-tabpanel&focusedCommentId=14545410#comment-14545410 ] Hudson commented on YARN-3505: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #197 (See [htt

[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-tabpanel&focusedCommentId=14545415#comment-14545415 ] Hudson commented on YARN-1519: -- FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #197 (See [htt

[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-tabpanel&focusedCommentId=14545471#comment-14545471 ] Hudson commented on YARN-3505: -- FAILURE: Integrated in Hadoop-trunk-Commit #7841 (See [https:

[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=14545548#comment-14545548 ] Srikanth Sundarrajan commented on YARN-3646: {quote} You can probably avoid thi

[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-tabpanel&focusedCommentId=14545572#comment-14545572 ] Hudson commented on YARN-1519: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2126 (See [https://

[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-tabpanel&focusedCommentId=14545567#comment-14545567 ] Hudson commented on YARN-3505: -- FAILURE: Integrated in Hadoop-Hdfs-trunk #2126 (See [https://

[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-tabpanel&focusedCommentId=14545597#comment-14545597 ] Hudson commented on YARN-3505: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #186 (See [htt

[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-tabpanel&focusedCommentId=14545607#comment-14545607 ] Xianyin Xin commented on YARN-3652: --- Thanks for comments, [~sunilg]. {quote} 1. *Throughp

[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-tabpanel&focusedCommentId=14545602#comment-14545602 ] Hudson commented on YARN-1519: -- FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #186 (See [htt

[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=14545715#comment-14545715 ] Hudson commented on YARN-1519: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk-Java8 #196 (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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=14545732#comment-14545732 ] Hudson commented on YARN-1519: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2144 (See [htt

[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-tabpanel&focusedCommentId=14545727#comment-14545727 ] Hudson commented on YARN-3505: -- SUCCESS: Integrated in Hadoop-Mapreduce-trunk #2144 (See [htt

[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-tabpanel&focusedCommentId=14545769#comment-14545769 ] Vinod Kumar Vavilapalli commented on YARN-3652: --- YARN-3293 added some key met

[jira] [Commented] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545770#comment-14545770 ] Lee Hounshell commented on YARN-3642: - Rohith, Thank you very much for your help! You

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

Xuan Gong created YARN-3654: --- Summary: ContainerLogsPage web UI should not have meta-refresh Key: YARN-3654 URL: https://issues.apache.org/jira/browse/YARN-3654 Project: Hadoop YARN Issue Type: Bug

[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-tabpanel&focusedCommentId=14545774#comment-14545774 ] Xuan Gong commented on YARN-3654: - My proposal: do similar things as YARN-2605, we need to

[jira] [Commented] (YARN-3526) ApplicationMaster tracking URL is incorrectly redirected on a QJM cluster

[ https://issues.apache.org/jira/browse/YARN-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545778#comment-14545778 ] Xuan Gong commented on YARN-3526: - Thanks, [~cheersyang] +1 LGTM. Will commit it later tod

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545788#comment-14545788 ] Junping Du commented on YARN-3411: -- Hi [~vrushalic] and all, there is one question I had f

[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-tabpanel&focusedCommentId=14545807#comment-14545807 ] Vinod Kumar Vavilapalli commented on YARN-3630: --- NodeManagers already get a t

[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-tabpanel&focusedCommentId=14545821#comment-14545821 ] Wangda Tan commented on YARN-3547: -- SchedulerApplicationAttempt.getAppAttemptResourceUsage

[jira] [Commented] (YARN-2829) After restart, RM should create running-attempt before AM register

[ https://issues.apache.org/jira/browse/YARN-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545827#comment-14545827 ] Vinod Kumar Vavilapalli commented on YARN-2829: --- Right, I think we fixed it a

[jira] [Resolved] (YARN-3642) Hadoop2 yarn.resourcemanager.scheduler.address not loaded by RMProxy.java

[ https://issues.apache.org/jira/browse/YARN-3642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohith resolved YARN-3642. -- Resolution: Invalid Closing as Invalid. If there is any queries or basic environment problems , I suggest to use

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545857#comment-14545857 ] Li Lu commented on YARN-3411: - Hi [~djp]! I totally agree with your concerns. However, for now

[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-tabpanel&focusedCommentId=14545859#comment-14545859 ] Wangda Tan commented on YARN-3583: -- Hi [~sunilg], Thanks for updating, bq. In yarn_servic

[jira] [Updated] (YARN-3541) Add version info on timeline service / generic history web UI and REST API

[ https://issues.apache.org/jira/browse/YARN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-3541: -- Summary: Add version info on timeline service / generic history web UI and REST API (was: Add version in

[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-tabpanel&focusedCommentId=14545871#comment-14545871 ] Jian He commented on YARN-3651: --- [~bibinchundatt], "http://host-10-19-92-117:13013"; this sho

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545909#comment-14545909 ] Wangda Tan commented on YARN-3635: -- [~kasha], Actually no, this patch doesn't do anything

[jira] [Commented] (YARN-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.

[ https://issues.apache.org/jira/browse/YARN-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545916#comment-14545916 ] Rohith commented on YARN-3543: -- Need to kick off jenkins again to check test failure are regul

[jira] [Commented] (YARN-2900) Application (Attempt and Container) Not Found in AHS results in Internal Server Error (500)

[ https://issues.apache.org/jira/browse/YARN-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545959#comment-14545959 ] Mit Desai commented on YARN-2900: - I am yet to verify that. Will try to get to this soon >

[jira] [Commented] (YARN-3624) ApplicationHistoryServer reverses the order of the filters it gets

[ https://issues.apache.org/jira/browse/YARN-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545968#comment-14545968 ] Mit Desai commented on YARN-3624: - I can add that. Thanks for reviewing the patch. [~zjshe

[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-tabpanel&focusedCommentId=14545979#comment-14545979 ] Bibin A Chundatt commented on YARN-3651: Hi [~jianhe] thnnk you for looking in to t

[jira] [Updated] (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:all-tabpanel ] Wangda Tan updated YARN-3609: - Attachment: YARN-3609.3.patch Attached ver.3 patch fixed test failures. > Move load labels from storage fr

[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-tabpanel&focusedCommentId=14546011#comment-14546011 ] Vinod Kumar Vavilapalli commented on YARN-3654: --- Makes sense. > ContainerLog

[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-tabpanel&focusedCommentId=14546014#comment-14546014 ] Jian He commented on YARN-3561: --- [~gsaha], I tried to look at this, but couldn't find the "c

[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-tabpanel&focusedCommentId=14546060#comment-14546060 ] Gour Saha commented on YARN-3561: - [~jianhe] The logs which were used to file the bug was n

[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.4.patch > Ordering policy should be allowed to reorder an application when demand

[jira] [Commented] (YARN-3635) Get-queue-mapping should be a common interface of YarnScheduler

[ https://issues.apache.org/jira/browse/YARN-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546108#comment-14546108 ] Vinod Kumar Vavilapalli commented on YARN-3635: --- Okay, I didn't think you wer

[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-tabpanel&focusedCommentId=14546110#comment-14546110 ] Craig Welch commented on YARN-3632: --- Uploaded patch to address checkstyle and whitespace

[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-tabpanel&focusedCommentId=14546132#comment-14546132 ] Hadoop QA commented on YARN-3609: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

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

zhihai xu created YARN-3655: --- Summary: FairScheduler: potential deadlock due to maxAMShare limitation and container reservation Key: YARN-3655 URL: https://issues.apache.org/jira/browse/YARN-3655 Project:

[jira] [Reopened] (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 ] Vinod Kumar Vavilapalli reopened YARN-3626: --- As I understand, the current patch doesn't do what you intend. The new configurati

[jira] [Updated] (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:all-tabpanel ] Xuan Gong updated YARN-3654: Attachment: YARN-3654.1.patch Create a patch based on my proposal. Tested the patch in a single node cluster.

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546166#comment-14546166 ] Vrushali C commented on YARN-3411: -- Hi [~djp] Thanks for the review! bq. In our case, the

[jira] [Commented] (YARN-3411) [Storage implementation] explore the native HBase write schema for storage

[ https://issues.apache.org/jira/browse/YARN-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546176#comment-14546176 ] Vrushali C commented on YARN-3411: -- Hi [~jrottinghuis] Thanks for the review! My response

[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-tabpanel&focusedCommentId=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-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-tabpanel&focusedCommentId=14546213#comment-14546213 ] Vinod Kumar Vavilapalli commented on YARN-3591: --- Essentially keeping the owne

[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-tabpanel&focusedCommentId=14546217#comment-14546217 ] Hadoop QA commented on YARN-3654: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14546254#comment-14546254 ] Jason Lowe commented on YARN-2421: -- +1 latest patch lgtm. Committing this. > CapacitySch

[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-tabpanel&focusedCommentId=14546257#comment-14546257 ] Hadoop QA commented on YARN-3632: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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 allo

[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-tabpanel&focusedCommentId=14546262#comment-14546262 ] Hadoop QA commented on YARN-3609: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14546268#comment-14546268 ] Hudson commented on YARN-2421: -- FAILURE: Integrated in Hadoop-trunk-Commit #7842 (See [https:

[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-tabpanel&focusedCommentId=14546271#comment-14546271 ] Craig Welch commented on YARN-3632: --- One line change to address missing whitespace issue.

[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-tabpanel&focusedCommentId=14546278#comment-14546278 ] Jian He commented on YARN-3561: --- [~gsaha], from the description, this is running against 2.6

[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-tabpanel&focusedCommentId=14546288#comment-14546288 ] Craig Welch commented on YARN-3626: --- [~cnauroth], [~vvasudev] - This patch goes back to t

[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=14546331#comment-14546331 ] Hadoop QA commented on YARN-3626: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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] [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-tabpanel&focusedCommentId=14546359#comment-14546359 ] Vinod Kumar Vavilapalli commented on YARN-3626: --- bq. We may have to depend on

[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-tabpanel&focusedCommentId=14546361#comment-14546361 ] Ishai Menache commented on YARN-3656: - LowCost judiciously “spreads” the demand of 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-tabpanel&focusedCommentId=14546365#comment-14546365 ] Chris Nauroth commented on YARN-3626: - I don't fully understand the objection to the fo

[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 o

[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-tabpanel&focusedCommentId=14546370#comment-14546370 ] Craig Welch commented on YARN-3626: --- bq. Can't we do the above? We definitely cannot inse

[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-tabpanel&focusedCommentId=14546374#comment-14546374 ] Craig Welch commented on YARN-3626: --- Right, going back to [~cnauroth], [~vinodkv], we cha

[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-tabpanel&focusedCommentId=14546377#comment-14546377 ] Bikas Saha commented on YARN-1902: -- The AMRMClient was not written to automatically remove

[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 reservati

[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-tabpanel&focusedCommentId=14546391#comment-14546391 ] Vinod Kumar Vavilapalli commented on YARN-1902: --- This was discussed multiple

[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-tabpanel&focusedCommentId=14546393#comment-14546393 ] Vinod Kumar Vavilapalli commented on YARN-3626: --- bq. I thought this implement

[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-tabpanel&focusedCommentId=14546396#comment-14546396 ] Hadoop QA commented on YARN-3632: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vo

[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-tabpanel&focusedCommentId=14546400#comment-14546400 ] Chris Nauroth commented on YARN-3626: - I see now. Thanks for the clarification. In th

[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-tabpanel&focusedCommentId=14546403#comment-14546403 ] Craig Welch commented on YARN-3632: --- findbugs and javac appear to be irrelevant... > Ord

[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 containe

[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] [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-tabpanel&focusedCommentId=14546418#comment-14546418 ] Vinod Kumar Vavilapalli commented on YARN-1902: --- bq. Wangda Tan mentioned off

  1   2   >