[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2556: --- Attachment: YARN-2556.8.patch Tool to measure the performance of the timeline server

[jira] [Updated] (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:all-tabpanel ] Chang Li updated YARN-2421: --- Attachment: YARN-2421.8.patch CapacityScheduler still allocates containers to an app in the FINISHING state

[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=14544390#comment-14544390 ] Chang Li commented on YARN-2421: Thanks [~jlowe] for valuable feedback! have updated my

[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=14542086#comment-14542086 ] Chang Li commented on YARN-2421: The check style is not related to my change. [~jlowe]

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2556: --- Attachment: YARN-2556.7.patch Tool to measure the performance of the timeline server

[jira] [Updated] (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:all-tabpanel ] Chang Li updated YARN-2421: --- Attachment: YARN-2421.6.patch CapacityScheduler still allocates containers to an app in the FINISHING state

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2556: --- Attachment: YARN-2556.6.patch Tool to measure the performance of the timeline server

[jira] [Updated] (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:all-tabpanel ] Chang Li updated YARN-2421: --- Attachment: YARN-2421.7.patch CapacityScheduler still allocates containers to an app in the FINISHING state

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2556: --- Attachment: YARN-2556.4.patch fix existing whitespace issue in MapredTestDrive Tool to measure the

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2556: --- Attachment: YARN-2556.5.patch Tool to measure the performance of the timeline server

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-2556: --- Attachment: YARN-2556.3.patch Tool to measure the performance of the timeline server

[jira] [Commented] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14539089#comment-14539089 ] Chang Li commented on YARN-2556: Thanks [~sjlee0] for thorough review! have updated patch

[jira] [Updated] (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:all-tabpanel ] Chang Li updated YARN-2421: --- Attachment: YARN-2421.5.patch CapacityScheduler still allocates containers to an app in the FINISHING state

[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=14533524#comment-14533524 ] Chang Li commented on YARN-2421: updated my patch, the current approach ignores allocate

[jira] [Updated] (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:all-tabpanel ] Chang Li updated YARN-2421: --- Affects Version/s: (was: 2.4.1) CapacityScheduler still allocates containers to an app in the FINISHING

[jira] [Updated] (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:all-tabpanel ] Chang Li updated YARN-2421: --- Attachment: YARN-2421.4.patch CapacityScheduler still allocates containers to an app in the FINISHING state

[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=14531549#comment-14531549 ] Chang Li commented on YARN-2421: Thanks for suggestions! I am planning to come back to work

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507245#comment-14507245 ] Chang Li commented on YARN-2308: Hi [~gu chi], this jira is intended to fix the NPE caused

[jira] [Commented] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505549#comment-14505549 ] Chang Li commented on YARN-3520: [~jlowe] could you please help do a final review of this

[jira] [Created] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

Chang Li created YARN-3520: -- Summary: get rid of excessive stacktrace caused by expired cookie in timeline log Key: YARN-3520 URL: https://issues.apache.org/jira/browse/YARN-3520 Project: Hadoop YARN

[jira] [Updated] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3520: --- Attachment: YARN-3520.patch get rid of excessive stacktrace caused by expired cookie in timeline log

[jira] [Commented] (YARN-3520) get rid of excessive stacktrace caused by expired cookie in timeline log

[ https://issues.apache.org/jira/browse/YARN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505223#comment-14505223 ] Chang Li commented on YARN-3520: [~mitdesai], [~jeagles], could you please help review this

[jira] [Updated] (YARN-3422) relatedentities always return empty list when primary filter is set

[ https://issues.apache.org/jira/browse/YARN-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3422: --- Attachment: YARN-3422.1.patch relatedentities always return empty list when primary filter is set

[jira] [Commented] (YARN-3422) relatedentities always return empty list when primary filter is set

[ https://issues.apache.org/jira/browse/YARN-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14387109#comment-14387109 ] Chang Li commented on YARN-3422: Hi [~zjshen], could you help me verify if this is a right

[jira] [Created] (YARN-3422) relatedentities always return empty list when primary filter is set

Chang Li created YARN-3422: -- Summary: relatedentities always return empty list when primary filter is set Key: YARN-3422 URL: https://issues.apache.org/jira/browse/YARN-3422 Project: Hadoop YARN

[jira] [Updated] (YARN-3335) Job In Error State Will Lost Jobhistory Of Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3335: --- Affects Version/s: (was: 2.8.0) 2.7.0 Job In Error State Will Lost Jobhistory Of

[jira] [Updated] (YARN-3335) Job In Error State Will Lost Jobhistory Of Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3335: --- Affects Version/s: 2.8.0 Job In Error State Will Lost Jobhistory Of Second and Later Attempts

[jira] [Updated] (YARN-3335) Job In Error State Will Lost Jobhistory Of Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3335: --- Attachment: YARN-3335.2.patch Job In Error State Will Lost Jobhistory Of Second and Later Attempts

[jira] [Created] (YARN-3335) Job In Error State Will Lost Jobhistory For Second and Later Attempts

Chang Li created YARN-3335: -- Summary: Job In Error State Will Lost Jobhistory For Second and Later Attempts Key: YARN-3335 URL: https://issues.apache.org/jira/browse/YARN-3335 Project: Hadoop YARN

[jira] [Updated] (YARN-3335) Job In Error State Will Lost Jobhistory Of Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3335: --- Description: Related to a fixed issue MAPREDUCE-6230 which cause a Job to get into error state. In that

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN-3267.4.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: (was: YARN-3267.4.patch) Timelineserver applies the ACL rules after applying the limit on the

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN-3267.4.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14358823#comment-14358823 ] Chang Li commented on YARN-3267: Thanks [~jeagles] for further review, updated patch

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN-3267.5.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-3335) Job In Error State Will Lost Jobhistory For Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357455#comment-14357455 ] Chang Li commented on YARN-3335: This patch provide a solution directly related to the

[jira] [Updated] (YARN-3335) Job In Error State Will Lost Jobhistory Of Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3335: --- Summary: Job In Error State Will Lost Jobhistory Of Second and Later Attempts (was: Job In Error State Will

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357292#comment-14357292 ] Chang Li commented on YARN-3267: [~jeagles] Thanks for review. Updated my patch according

[jira] [Updated] (YARN-3335) Job In Error State Will Lost Jobhistory For Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3335: --- Attachment: YARN-3335.1.patch Job In Error State Will Lost Jobhistory For Second and Later Attempts

[jira] [Commented] (YARN-3335) Job In Error State Will Lost Jobhistory For Second and Later Attempts

[ https://issues.apache.org/jira/browse/YARN-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14357464#comment-14357464 ] Chang Li commented on YARN-3335: Another plausible solution is to always let ERROR state to

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN-3267.3.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348877#comment-14348877 ] Chang Li commented on YARN-3267: [~pramachandran][~zjshen] Could you help review my patach.

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347320#comment-14347320 ] Chang Li commented on YARN-3267: Have implemented unit test for this patch Timelineserver

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_V1.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_V2.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_WIP2.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_WIP3.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345370#comment-14345370 ] Chang Li commented on YARN-3267: Hi [~pramachandran], could you please help test this

[jira] [Commented] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340837#comment-14340837 ] Chang Li commented on YARN-3267: [~pramachandran] Could you take a look at my solution in

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_WIP.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Attachment: YARN_3267_WIP1.patch Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14338665#comment-14338665 ] Chang Li commented on YARN-3131: [~jlowe] [~jianhe] [~leftnoteasy] Could any of you help

[jira] [Assigned] (YARN-3268) timelineserver rest api returns html page for 404 when a bad endpoint is used.

[ https://issues.apache.org/jira/browse/YARN-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li reassigned YARN-3268: -- Assignee: Chang Li timelineserver rest api returns html page for 404 when a bad endpoint is used.

[jira] [Assigned] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li reassigned YARN-3267: -- Assignee: Chang Li Timelineserver applies the ACL rules after applying the limit on the number of

[jira] [Updated] (YARN-3268) timelineserver rest api returns html page for 404 when a bad endpoint is used.

[ https://issues.apache.org/jira/browse/YARN-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3268: --- Assignee: (was: Chang Li) timelineserver rest api returns html page for 404 when a bad endpoint is used.

[jira] [Assigned] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li reassigned YARN-3267: -- Assignee: Chang Li Timelineserver applies the ACL rules after applying the limit on the number of

[jira] [Updated] (YARN-3267) Timelineserver applies the ACL rules after applying the limit on the number of records

[ https://issues.apache.org/jira/browse/YARN-3267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3267: --- Assignee: (was: Chang Li) Timelineserver applies the ACL rules after applying the limit on the number

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14337470#comment-14337470 ] Chang Li commented on YARN-3131: Thanks [~jlowe] for commenting. [~vinodkv] I have fixed

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v7.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v5.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v6.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14335578#comment-14335578 ] Chang Li commented on YARN-3131: [~jianhe] Thanks for review! I have updated my patch.

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v3.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v4.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333662#comment-14333662 ] Chang Li commented on YARN-3131: [~leftnoteasy] YarnClientImpl should check FAILED and

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14333658#comment-14333658 ] Chang Li commented on YARN-3131: [~wangda]Thanks for reviewing my work! I have updated my

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v2.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Commented] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14329380#comment-14329380 ] Chang Li commented on YARN-3131: Updated patch, fixed unit test and improved the code

[jira] [Updated] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

[ https://issues.apache.org/jira/browse/YARN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chang Li updated YARN-3131: --- Attachment: yarn_3131_v1.patch YarnClientImpl should check FAILED and KILLED state in submitApplication

[jira] [Created] (YARN-3131) YarnClientImpl should check FAILED and KILLED state in submitApplication

Chang Li created YARN-3131: -- Summary: YarnClientImpl should check FAILED and KILLED state in submitApplication Key: YARN-3131 URL: https://issues.apache.org/jira/browse/YARN-3131 Project: Hadoop YARN

[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 replace the hardcoded argument ApplicationHistoryServer doesn't process -D

[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 ApplicationHistoryServer doesn't process -D arguments

[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=14297498#comment-14297498 ] chang li commented on YARN-3108: have created tracking jira for this problem

[jira] [Created] (YARN-3113) some lately checked in changes in dt-1.9.4/images/Sorting icons.psd is causing release audit warning

chang li created YARN-3113: -- Summary: some lately checked in changes in dt-1.9.4/images/Sorting icons.psd is causing release audit warning Key: YARN-3113 URL: https://issues.apache.org/jira/browse/YARN-3113

[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=14297492#comment-14297492 ] chang li commented on YARN-3108: This -1 release audit is unrelated to my change, it's

[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] [Updated] (YARN-2847) Linux native container executor segfaults if default banned user detected

[ https://issues.apache.org/jira/browse/YARN-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2847: --- Attachment: yarn2847.patch Linux native container executor segfaults if default banned user detected

[jira] [Updated] (YARN-2847) Linux native container executor segfaults if default banned user detected

[ https://issues.apache.org/jira/browse/YARN-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2847: --- Attachment: yarn2847.patch latest patch, previous one has a minor comment error Linux native container

[jira] [Commented] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213006#comment-14213006 ] chang li commented on YARN-2556: I have run those failed tests on my local machine and they

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2556: --- Attachment: yarn2556.patch attempted modified patch according to build failure Tool to measure the

[jira] [Assigned] (YARN-2847) Linux native container executor segfaults if default banned user detected

[ https://issues.apache.org/jira/browse/YARN-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li reassigned YARN-2847: -- Assignee: chang li Linux native container executor segfaults if default banned user detected

[jira] [Updated] (YARN-2847) Linux native container executor segfaults if default banned user detected

[ https://issues.apache.org/jira/browse/YARN-2847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2847: --- Attachment: yarn2847notest.patch patch with no test Linux native container executor segfaults if default

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2556: --- Attachment: yarn2556.patch Cleaned up my patch, welcome to review. I have used this application to test the

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2556: --- Attachment: yarn2556_wip.patch current work in progress patch. implement the measure for iorate and

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2556: --- Attachment: (was: yarn2556_wip.patch) Tool to measure the performance of the timeline server

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2556: --- Attachment: YARN-2556-WIP.patch Tool to measure the performance of the timeline server

[jira] [Updated] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2556: --- Attachment: yarn2556_wip.patch Thanks [~airbots] for the substantial early work! I have moved the test job

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14137937#comment-14137937 ] chang li commented on YARN-2308: thanks for the collective thought about this and all

[jira] [Assigned] (YARN-2556) Tool to measure the performance of the timeline server

[ https://issues.apache.org/jira/browse/YARN-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li reassigned YARN-2556: -- Assignee: chang li Tool to measure the performance of the timeline server

[jira] [Updated] (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:all-tabpanel ] chang li updated YARN-2421: --- Attachment: yarn2421.patch CapacityScheduler still allocates containers to an app in the FINISHING state

[jira] [Updated] (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:all-tabpanel ] chang li updated YARN-2421: --- Attachment: yarn2421.patch updated patch CapacityScheduler still allocates containers to an app in the

[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=14105936#comment-14105936 ] chang li commented on YARN-2421: [~airbots], Have removed that, thanks for finding that out

[jira] [Updated] (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:all-tabpanel ] chang li updated YARN-2421: --- Attachment: yarn2421.patch updated patch with apache license header CapacityScheduler still allocates

[jira] [Assigned] (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:all-tabpanel ] chang li reassigned YARN-2421: -- Assignee: chang li CapacityScheduler still allocates containers to an app in the FINISHING state

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14094178#comment-14094178 ] chang li commented on YARN-2308: [~wangda] I don't think this conf set should be necessary

[jira] [Commented] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14093001#comment-14093001 ] chang li commented on YARN-2308: [~wangda] I have updated my patch according to your

[jira] [Updated] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2308: --- Attachment: jira2308.patch updated patch according to Wangda's advice NPE happened when RM restart after

[jira] [Updated] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2308: --- Attachment: jira2308.patch patch updated according to Wangda's suggestion NPE happened when RM restart

[jira] [Updated] (YARN-2308) NPE happened when RM restart after CapacityScheduler queue configuration changed

[ https://issues.apache.org/jira/browse/YARN-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chang li updated YARN-2308: --- Attachment: jira2308.patch NPE happened when RM restart after CapacityScheduler queue configuration

<    1   2   3   4   >