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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14546554#comment-14546554 ] Hadoop QA commented on YARN-3565: - \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ ||

[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-tabpanelfocusedCommentId=14546575#comment-14546575 ] Xuan Gong commented on YARN-3526: - Committed into trunk/branch-2/branch-2.7. Thanks,

[jira] [Updated] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3667: Description: Fix findbugs warning Inconsistent synchronization of

[jira] [Updated] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3667: Attachment: YARN-3667.000.patch Fix findbugs warning Inconsistent synchronization of

[jira] [Commented] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

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

[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-tabpanelfocusedCommentId=14546560#comment-14546560 ] Rohith commented on YARN-3543: -- bq. ApplicationReport.newInstance() is Private, so you should

[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-tabpanelfocusedCommentId=14546562#comment-14546562 ] Rohith commented on YARN-3543: -- bq. But doesn't impact compatibility? I meant to say

[jira] [Created] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

zhihai xu created YARN-3667: --- Summary: Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS Key: YARN-3667 URL:

[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=14546568#comment-14546568 ] Lavkesh Lahngir commented on YARN-3591: --- [~vinodkv]: The concern here is, If a

[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-tabpanelfocusedCommentId=14546577#comment-14546577 ] Hudson commented on YARN-3526: -- FAILURE: Integrated in Hadoop-trunk-Commit #7845 (See

[jira] [Commented] (YARN-221) NM should provide a way for AM to tell it not to aggregate logs.

[ https://issues.apache.org/jira/browse/YARN-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546576#comment-14546576 ] Xuan Gong commented on YARN-221: Canceling the patch for discussion.. NM should provide a

[jira] [Updated] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3667: Description: Fix findbugs warning Inconsistent synchronization of

[jira] [Commented] (YARN-3667) Fix findbugs warning Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS

[ https://issues.apache.org/jira/browse/YARN-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546521#comment-14546521 ] zhihai xu commented on YARN-3667: - I uploaded a patch for review. The patch is to add

[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=14546525#comment-14546525 ] zhihai xu commented on YARN-3655: - findbugs warning is not related to the attached patch, I

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

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

[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-tabpanelfocusedCommentId=14545827#comment-14545827 ] Vinod Kumar Vavilapalli commented on YARN-2829: --- Right, I think we fixed it

[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=14545859#comment-14545859 ] Wangda Tan commented on YARN-3583: -- Hi [~sunilg], Thanks for updating, bq. 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-tabpanelfocusedCommentId=14545871#comment-14545871 ] Jian He commented on YARN-3651: --- [~bibinchundatt], http://host-10-19-92-117:13013; this

[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-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=14545916#comment-14545916 ] Rohith commented on YARN-3543: -- Need to kick off jenkins again to check test failure are

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

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

[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=14545821#comment-14545821 ] Wangda Tan commented on YARN-3547: --

[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-tabpanelfocusedCommentId=14545857#comment-14545857 ] Li Lu commented on YARN-3411: - Hi [~djp]! I totally agree with your concerns. However, for now

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

[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

[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-tabpanelfocusedCommentId=14546108#comment-14546108 ] Vinod Kumar Vavilapalli commented on YARN-3635: --- Okay, I didn't think you

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

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

[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-tabpanelfocusedCommentId=14545968#comment-14545968 ] Mit Desai commented on YARN-3624: - I can add that. Thanks for reviewing the patch.

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

[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-tabpanelfocusedCommentId=14545959#comment-14545959 ] Mit Desai commented on YARN-2900: - I am yet to verify that. Will try to get to this soon

[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

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

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

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

[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-tabpanelfocusedCommentId=14545770#comment-14545770 ] Lee Hounshell commented on YARN-3642: - Rohith, Thank you very much for your help! You

[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-tabpanelfocusedCommentId=14545778#comment-14545778 ] Xuan Gong commented on YARN-3526: - Thanks, [~cheersyang] +1 LGTM. Will commit it later

[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-tabpanelfocusedCommentId=14545788#comment-14545788 ] Junping Du commented on YARN-3411: -- Hi [~vrushalic] and all, there is one question I had

[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

[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

[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-tabpanelfocusedCommentId=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-tabpanelfocusedCommentId=14546176#comment-14546176 ] Vrushali C commented on YARN-3411: -- Hi [~jrottinghuis] Thanks for the review! My response

<    1   2