[jira] [Commented] (YARN-3028) Better syntax for replaceLabelsOnNode in RMAdmin CLI

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

[jira] [Commented] (YARN-3011) NM dies because of the failure of resource localization

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

[jira] [Commented] (YARN-3086) Make NodeManager memory configurable in MiniYARNCluster

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

[jira] [Commented] (YARN-2932) Add entry for preemptable status (enabled/disabled) to scheduler web UI and queue initialize/refresh logging

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

[jira] [Commented] (YARN-2897) CrossOriginFilter needs more log statements

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

[jira] [Commented] (YARN-2897) CrossOriginFilter needs more log statements

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

[jira] [Commented] (YARN-3011) NM dies because of the failure of resource localization

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

[jira] [Commented] (YARN-2005) Blacklisting support for scheduling AMs

[ https://issues.apache.org/jira/browse/YARN-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295171#comment-14295171 ] Jason Lowe commented on YARN-2005: -- bq. App name is the first point came in to my

[jira] [Commented] (YARN-3028) Better syntax for replaceLabelsOnNode in RMAdmin CLI

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

[jira] [Commented] (YARN-3086) Make NodeManager memory configurable in MiniYARNCluster

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

[jira] [Commented] (YARN-3098) Create common QueueCapacities class in Capacity Scheduler to track capacities-by-labels of queues

[ https://issues.apache.org/jira/browse/YARN-3098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294961#comment-14294961 ] Sunil G commented on YARN-3098: --- Yes [~leftnoteasy] I understood you point. Sometimes we can

[jira] [Commented] (YARN-2875) Bump SLF4J to 1.7.7 from 1.7.5

[ https://issues.apache.org/jira/browse/YARN-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14294932#comment-14294932 ] Tim Robertson commented on YARN-2875: - Done - bumped to 1.7.10 which the release notes

[jira] [Commented] (YARN-3086) Make NodeManager memory configurable in MiniYARNCluster

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

[jira] [Commented] (YARN-2897) CrossOriginFilter needs more log statements

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

[jira] [Commented] (YARN-2932) Add entry for preemptable status (enabled/disabled) to scheduler web UI and queue initialize/refresh logging

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

[jira] [Commented] (YARN-3086) Make NodeManager memory configurable in MiniYARNCluster

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

[jira] [Commented] (YARN-3028) Better syntax for replaceLabelsOnNode in RMAdmin CLI

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

[jira] [Commented] (YARN-3011) NM dies because of the failure of resource localization

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

[jira] [Commented] (YARN-2932) Add entry for preemptable status (enabled/disabled) to scheduler web UI and queue initialize/refresh logging

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

[jira] [Commented] (YARN-3103) AMRMClientImpl does not update AMRM token properly

[ https://issues.apache.org/jira/browse/YARN-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295216#comment-14295216 ] Jason Lowe commented on YARN-3103: -- On second thought, maybe the client doesn't need to

[jira] [Commented] (YARN-2932) Add entry for preemptable status (enabled/disabled) to scheduler web UI and queue initialize/refresh logging

[ https://issues.apache.org/jira/browse/YARN-2932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295218#comment-14295218 ] Eric Payne commented on YARN-2932: -- Thank you for your input and review, [~leftnoteasy]

[jira] [Commented] (YARN-3086) Make NodeManager memory configurable in MiniYARNCluster

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

[jira] [Commented] (YARN-3028) Better syntax for replaceLabelsOnNode in RMAdmin CLI

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

[jira] [Commented] (YARN-3011) NM dies because of the failure of resource localization

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

[jira] [Updated] (YARN-2922) ConcurrentModificationException in CapacityScheduler's LeafQueue

[ https://issues.apache.org/jira/browse/YARN-2922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-2922: - Fix Version/s: 2.7.0 ConcurrentModificationException in CapacityScheduler's LeafQueue

[jira] [Commented] (YARN-3094) reset timer for liveness monitors after RM recovery

[ https://issues.apache.org/jira/browse/YARN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295291#comment-14295291 ] Jun Gong commented on YARN-3094: Hi [~jianhe], could you please help review it? Thank you.

[jira] [Commented] (YARN-3047) set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295453#comment-14295453 ] Varun Saxena commented on YARN-3047: [~zjshen], kindly have a look at the initial patch

[jira] [Updated] (YARN-3047) set up ATS reader with basic request serving structure and lifecycle

[ https://issues.apache.org/jira/browse/YARN-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3047: --- Attachment: YARN-3047.001.patch set up ATS reader with basic request serving structure and lifecycle

[jira] [Commented] (YARN-3094) reset timer for liveness monitors after RM recovery

[ https://issues.apache.org/jira/browse/YARN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295814#comment-14295814 ] Anubhav Dhoot commented on YARN-3094: - Hi [~Jun Gong] Can you please use the

[jira] [Updated] (YARN-3104) RM continues to send new AMRM tokens every heartbeat between rolling and activation

[ https://issues.apache.org/jira/browse/YARN-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe updated YARN-3104: - Attachment: YARN-3104.001.patch As discussed in YARN-2314 the IPC layer makes it near impossible to close

[jira] [Commented] (YARN-3103) AMRMClientImpl does not update AMRM token properly

[ https://issues.apache.org/jira/browse/YARN-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295929#comment-14295929 ] Jian He commented on YARN-3103: --- patch looks good to me. bq. In addition the AMRMClientImpl

[jira] [Commented] (YARN-3099) Capacity Scheduler LeafQueue/ParentQueue should use ResourceUsage to track used-resources-by-label.

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

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295924#comment-14295924 ] Siqi Li commented on YARN-3101: --- It looks like you are right. The if condition somehow got

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296046#comment-14296046 ] Siqi Li commented on YARN-3101: --- But I am not quite sure about that if

[jira] [Created] (YARN-3108) ApplicationHistoryServer doesn't process -D arguments

chang li created YARN-3108: -- Summary: ApplicationHistoryServer doesn't process -D arguments Key: YARN-3108 URL: https://issues.apache.org/jira/browse/YARN-3108 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-3108) ApplicationHistoryServer doesn't process -D arguments

[ https://issues.apache.org/jira/browse/YARN-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-3108: --- Attachment: yarn3108.patch have provided a solution for this ApplicationHistoryServer doesn't process -D

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296066#comment-14296066 ] Yongjun Zhang commented on YARN-3021: - Hi [~rkanter] and [~adhoot], Thanks for your

[jira] [Updated] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3079: Attachment: YARN-3079.004.patch Scheduler should also update maximumAllocation when updateNodeResource.

[jira] [Commented] (YARN-3100) Make YARN authorization pluggable

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

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3101: -- Attachment: (was: YARN-3101-Siqi.v1.patch) FairScheduler#fitInMaxShare was added to validate reservations

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3101: -- Attachment: YARN-3101-Siqi.v1.patch FairScheduler#fitInMaxShare was added to validate reservations but it does

[jira] [Assigned] (YARN-3104) RM continues to send new AMRM tokens every heartbeat between rolling and activation

[ https://issues.apache.org/jira/browse/YARN-3104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Lowe reassigned YARN-3104: Assignee: Jason Lowe RM continues to send new AMRM tokens every heartbeat between rolling and

[jira] [Commented] (YARN-3100) Make YARN authorization pluggable

[ https://issues.apache.org/jira/browse/YARN-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295919#comment-14295919 ] Jian He commented on YARN-3100: --- bq. I hope you recognize that from an outside perspective

[jira] [Commented] (YARN-3022) Expose Container resource information from NodeManager for monitoring

[ https://issues.apache.org/jira/browse/YARN-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296030#comment-14296030 ] Robert Kanter commented on YARN-3022: - +1 Expose Container resource information from

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296041#comment-14296041 ] Robert Kanter commented on YARN-3021: - {quote}I don't see any security holes. This

[jira] [Updated] (YARN-3100) Make YARN authorization pluggable

[ https://issues.apache.org/jira/browse/YARN-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian He updated YARN-3100: -- Attachment: YARN-3100.2.patch Make YARN authorization pluggable -

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296077#comment-14296077 ] zhihai xu commented on YARN-3079: - Hi [~rkanter], thanks for the review. I found out since

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296113#comment-14296113 ] Robert Kanter commented on YARN-3021: - Ok, then I think it should probably fine; though

[jira] [Commented] (YARN-3108) ApplicationHistoryServer doesn't process -D arguments

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

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296147#comment-14296147 ] Yongjun Zhang commented on YARN-3021: - Hi [~rkanter], the reason I moved

[jira] [Commented] (YARN-3099) Capacity Scheduler LeafQueue/ParentQueue should use ResourceUsage to track used-resources-by-label.

[ https://issues.apache.org/jira/browse/YARN-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296153#comment-14296153 ] Jian He commented on YARN-3099: --- - usage.getUsed() should be usage.getUsed(label) {code}

[jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

[ https://issues.apache.org/jira/browse/YARN-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siqi Li updated YARN-3101: -- Attachment: YARN-3101-Siqi.v1.patch I feel like adding reserved memory into consideration is not necessary.

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

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

[jira] [Updated] (YARN-3099) Capacity Scheduler LeafQueue/ParentQueue should use ResourceUsage to track used-resources-by-label.

[ https://issues.apache.org/jira/browse/YARN-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-3099: - Attachment: YARN-3099.4.patch Thanks for your comment, [~jianhe]. Updated patch addressed your comments.

[jira] [Commented] (YARN-3103) AMRMClientImpl does not update AMRM token properly

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

[jira] [Commented] (YARN-3021) YARN's delegation-token handling disallows certain trust setups to operate properly

[ https://issues.apache.org/jira/browse/YARN-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296059#comment-14296059 ] Anubhav Dhoot commented on YARN-3021: - We are talking about turning off renewal of

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296108#comment-14296108 ] Robert Kanter commented on YARN-3079: - Sounds good. +1 Scheduler should also update

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

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

[jira] [Commented] (YARN-3011) NM dies because of the failure of resource localization

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

[jira] [Commented] (YARN-2897) CrossOriginFilter needs more log statements

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

[jira] [Commented] (YARN-2932) Add entry for preemptable status (enabled/disabled) to scheduler web UI and queue initialize/refresh logging

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

[jira] [Commented] (YARN-2932) Add entry for preemptable status (enabled/disabled) to scheduler web UI and queue initialize/refresh logging

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

[jira] [Commented] (YARN-2897) CrossOriginFilter needs more log statements

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

[jira] [Commented] (YARN-3028) Better syntax for replaceLabelsOnNode in RMAdmin CLI

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

[jira] [Commented] (YARN-3103) AMRMClientImpl does not update AMRM token properly

[ https://issues.apache.org/jira/browse/YARN-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295952#comment-14295952 ] Jason Lowe commented on YARN-3103: -- bq. Jason, does the patch work on secure cluster too?

[jira] [Commented] (YARN-3029) FSDownload.unpack() uses local locale for FS case conversion, may not work everywhere

[ https://issues.apache.org/jira/browse/YARN-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14295974#comment-14295974 ] Varun Saxena commented on YARN-3029: [~ozawa], added a test case. Kindly review.

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296005#comment-14296005 ] Wangda Tan commented on YARN-3079: -- [~rkanter], wanna take a look? I plan to commit this

[jira] [Commented] (YARN-3103) AMRMClientImpl does not update AMRM token properly

[ https://issues.apache.org/jira/browse/YARN-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296003#comment-14296003 ] Jian He commented on YARN-3103: --- bq. That patch did not work if I let it update the login

[jira] [Commented] (YARN-3103) AMRMClientImpl does not update AMRM token properly

[ https://issues.apache.org/jira/browse/YARN-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296004#comment-14296004 ] Jian He commented on YARN-3103: --- bq. The previous version patch in YARN-3103 sorry, I meant

[jira] [Commented] (YARN-3103) AMRMClientImpl does not update AMRM token properly

[ https://issues.apache.org/jira/browse/YARN-3103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296008#comment-14296008 ] Xuan Gong commented on YARN-3103: - I do not have any other comments. +1 for the patch. bq.

[jira] [Created] (YARN-3107) Update TestYarnConfigurationFields to flag missing properties in yarn-default.xml with an error

Ray Chiang created YARN-3107: Summary: Update TestYarnConfigurationFields to flag missing properties in yarn-default.xml with an error Key: YARN-3107 URL: https://issues.apache.org/jira/browse/YARN-3107

[jira] [Commented] (YARN-3104) RM continues to send new AMRM tokens every heartbeat between rolling and activation

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

[jira] [Updated] (YARN-3029) FSDownload.unpack() uses local locale for FS case conversion, may not work everywhere

[ https://issues.apache.org/jira/browse/YARN-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Saxena updated YARN-3029: --- Attachment: YARN-3029.002.patch FSDownload.unpack() uses local locale for FS case conversion, may not

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296006#comment-14296006 ] Robert Kanter commented on YARN-3079: - I'm actually looking at it right now :)

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296018#comment-14296018 ] Robert Kanter commented on YARN-3079: - I think we should acquire {{maxAllocWriteLock}}

[jira] [Commented] (YARN-3029) FSDownload.unpack() uses local locale for FS case conversion, may not work everywhere

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

[jira] [Commented] (YARN-41) The RM should handle the graceful shutdown of the NM.

[ https://issues.apache.org/jira/browse/YARN-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296222#comment-14296222 ] Junping Du commented on YARN-41: [~devaraj.k], thanks for updating the patch! [~vinodkv] is

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296228#comment-14296228 ] zhihai xu commented on YARN-3079: - Hi [~leftnoteasy], All these tests(TestFSRMStateStore,

[jira] [Commented] (YARN-3099) Capacity Scheduler LeafQueue/ParentQueue should use ResourceUsage to track used-resources-by-label.

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

[jira] [Commented] (YARN-3077) RM should create yarn.resourcemanager.zk-state-store.parent-path recursively

[ https://issues.apache.org/jira/browse/YARN-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296263#comment-14296263 ] Chun Chen commented on YARN-3077: - [~ozawa], OK, upload a new patch to update the patch and

[jira] [Commented] (YARN-3077) RM should create yarn.resourcemanager.zk-state-store.parent-path recursively

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

[jira] [Commented] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

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

[jira] [Updated] (YARN-3109) Broken link in cluster apps for application when queue full and failed

[ https://issues.apache.org/jira/browse/YARN-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3109: --- Description: Application link in cluster/apps broken when queue full and failed Configure

[jira] [Updated] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3079: Attachment: (was: YARN-3079.004.patch) Scheduler should also update maximumAllocation when

[jira] [Updated] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhihai xu updated YARN-3079: Attachment: YARN-3079.004.patch Scheduler should also update maximumAllocation when updateNodeResource.

[jira] [Created] (YARN-3109) Broken link in cluster apps for application when queue full an rejected

Bibin A Chundatt created YARN-3109: -- Summary: Broken link in cluster apps for application when queue full an rejected Key: YARN-3109 URL: https://issues.apache.org/jira/browse/YARN-3109 Project:

[jira] [Updated] (YARN-3109) Broken link in cluster apps for application when queue full and failed

[ https://issues.apache.org/jira/browse/YARN-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3109: --- Summary: Broken link in cluster apps for application when queue full and failed (was: Broken

[jira] [Created] (YARN-3110) Faulty link and state in ApplicationHistory when aplication is in unassigned state

Bibin A Chundatt created YARN-3110: -- Summary: Faulty link and state in ApplicationHistory when aplication is in unassigned state Key: YARN-3110 URL: https://issues.apache.org/jira/browse/YARN-3110

[jira] [Assigned] (YARN-3110) Faulty link and state in ApplicationHistory when aplication is in unassigned state

[ https://issues.apache.org/jira/browse/YARN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Naganarasimha G R reassigned YARN-3110: --- Assignee: Naganarasimha G R Faulty link and state in ApplicationHistory when

[jira] [Updated] (YARN-3110) Faulty link and state in ApplicationHistory when aplication is in unassigned state

[ https://issues.apache.org/jira/browse/YARN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3110: --- Description: Application state and History link wrong when Application is in unassigned state

[jira] [Updated] (YARN-3110) Faulty link and state in ApplicationHistory when aplication is in unassigned state

[ https://issues.apache.org/jira/browse/YARN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3110: --- Description: Application state and History link wrong when Application is in unassigned state

[jira] [Resolved] (YARN-2680) Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is disabled.

[ https://issues.apache.org/jira/browse/YARN-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du resolved YARN-2680. -- Resolution: Duplicate Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery

[jira] [Updated] (YARN-2680) Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is disabled.

[ https://issues.apache.org/jira/browse/YARN-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Junping Du updated YARN-2680: - Summary: Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is disabled.

[jira] [Updated] (YARN-3077) RM should create yarn.resourcemanager.zk-state-store.parent-path recursively

[ https://issues.apache.org/jira/browse/YARN-3077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chun Chen updated YARN-3077: Attachment: YARN-3077.3.patch RM should create yarn.resourcemanager.zk-state-store.parent-path recursively

[jira] [Commented] (YARN-2680) Node shouldn't be listed as RUNNING when NM daemon is stop even when recovery work is enabled.

[ https://issues.apache.org/jira/browse/YARN-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296209#comment-14296209 ] Junping Du commented on YARN-2680: -- Hi [~jlowe], I think I meant that Node shouldn't be

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

[ https://issues.apache.org/jira/browse/YARN-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14296214#comment-14296214 ] Wangda Tan commented on YARN-3079: -- [~zxu], could you verify if failed tests are not

[jira] [Updated] (YARN-3110) Faulty link and state in ApplicationHistory when aplication is in unassigned state

[ https://issues.apache.org/jira/browse/YARN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3110: --- Description: Application state and History link wrong when Application is in unassigned state

[jira] [Updated] (YARN-3110) Faulty link and state in ApplicationHistory when aplication is in unassigned state

[ https://issues.apache.org/jira/browse/YARN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bibin A Chundatt updated YARN-3110: --- Description: Application state and History link wrong when Application is in unassigned state

[jira] [Commented] (YARN-3079) Scheduler should also update maximumAllocation when updateNodeResource.

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

[jira] [Updated] (YARN-3094) reset timer for liveness monitors after RM recovery

[ https://issues.apache.org/jira/browse/YARN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Gong updated YARN-3094: --- Attachment: YARN-3094.3.patch reset timer for liveness monitors after RM recovery

  1   2   >