[jira] [Comment Edited] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969940#comment-16969940 ] Xianghao Lu edited comment on YARN-9957 at 11/8/19 8:30 AM: IMO, the root

[jira] [Comment Edited] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969940#comment-16969940 ] Xianghao Lu edited comment on YARN-9957 at 11/8/19 8:29 AM: IMO, the root

[jira] [Updated] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9957: -- Attachment: YARN-9957-branch-2.9.1.002.patch > The first container we recover may not be the AM >

[jira] [Commented] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969940#comment-16969940 ] Xianghao Lu commented on YARN-9957: --- IMO, the root cause of the following case in YARN-7382 is

[jira] [Comment Edited] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969006#comment-16969006 ] Xianghao Lu edited comment on YARN-9957 at 11/7/19 7:47 AM: The failure above

[jira] [Commented] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16969006#comment-16969006 ] Xianghao Lu commented on YARN-9957: --- The failure above has nothing to do with the patch,

[jira] [Commented] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16968976#comment-16968976 ] Xianghao Lu commented on YARN-9957: --- The test sample is as described below # submit a MR job, am

[jira] [Updated] (YARN-9957) The first container we recover may not be the AM

[ https://issues.apache.org/jira/browse/YARN-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9957: -- Attachment: 2.jpg 1.jpg > The first container we recover may not be the AM >

[jira] [Created] (YARN-9957) The first container we recover may not be the AM

Xianghao Lu created YARN-9957: - Summary: The first container we recover may not be the AM Key: YARN-9957 URL: https://issues.apache.org/jira/browse/YARN-9957 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-4995) FairScheduler: Display per-queue demand on the scheduler page

[ https://issues.apache.org/jira/browse/YARN-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966586#comment-16966586 ] Xianghao Lu commented on YARN-4995: --- [~imstefanlee] IMO, you are right, however, the duplicate

[jira] [Comment Edited] (YARN-9944) Don't need to kill container which already released in FSPreemtion thread

[ https://issues.apache.org/jira/browse/YARN-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16963909#comment-16963909 ] Xianghao Lu edited comment on YARN-9944 at 10/31/19 11:55 AM: -- log before fix

[jira] [Comment Edited] (YARN-9944) Don't need to kill container which already released in FSPreemtion thread

[ https://issues.apache.org/jira/browse/YARN-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16963909#comment-16963909 ] Xianghao Lu edited comment on YARN-9944 at 10/31/19 11:52 AM: -- log before fix

[jira] [Comment Edited] (YARN-9944) Don't need to kill container which already released in FSPreemtion thread

[ https://issues.apache.org/jira/browse/YARN-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16963909#comment-16963909 ] Xianghao Lu edited comment on YARN-9944 at 10/31/19 11:51 AM: -- log before fix

[jira] [Commented] (YARN-9944) Don't need to kill container which already released in FSPreemtion thread

[ https://issues.apache.org/jira/browse/YARN-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16963909#comment-16963909 ] Xianghao Lu commented on YARN-9944: --- log before fix {code:java} 2019-10-31 16:50:28,103 INFO

[jira] [Updated] (YARN-9944) Don't need to kill container which already released in FSPreemtion thread

[ https://issues.apache.org/jira/browse/YARN-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9944: -- Attachment: (was: YARN-9944-branch-2.9.1.001.patch) > Don't need to kill container which already

[jira] [Updated] (YARN-9944) Don't need to kill container which already released in FSPreemtion thread

[ https://issues.apache.org/jira/browse/YARN-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9944: -- Attachment: YARN-9944-branch-2.9.1.001.patch > Don't need to kill container which already released in

[jira] [Created] (YARN-9944) Don't need to kill container which already released in FSPreemtion thread

Xianghao Lu created YARN-9944: - Summary: Don't need to kill container which already released in FSPreemtion thread Key: YARN-9944 URL: https://issues.apache.org/jira/browse/YARN-9944 Project: Hadoop YARN

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Attachment: YARN-9896.003.patch > allocDelay in FSPreemptionThread should not be 0 >

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Attachment: YARN-9896.002.patch > allocDelay in FSPreemptionThread should not be 0 >

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Attachment: YARN-9896-branch-2.9.1.001.patch > allocDelay in FSPreemptionThread should not be 0 >

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Attachment: (was: YARN-9896.001.patch) > allocDelay in FSPreemptionThread should not be 0 >

[jira] [Comment Edited] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949980#comment-16949980 ] Xianghao Lu edited comment on YARN-9896 at 10/12/19 9:36 AM: - I have print log

[jira] [Commented] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949980#comment-16949980 ] Xianghao Lu commented on YARN-9896: --- I have print log in my test cluster with patch as follows

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Description:

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Description:

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Description: [allocDelay|#L63] in FSPreemptionThread.java will be 0, because 

[jira] [Updated] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

[ https://issues.apache.org/jira/browse/YARN-9896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9896: -- Description: [allocDelay|#L63]] in FSPreemptionThread.java will be 0, because 

[jira] [Created] (YARN-9896) allocDelay in FSPreemptionThread should not be 0

Xianghao Lu created YARN-9896: - Summary: allocDelay in FSPreemptionThread should not be 0 Key: YARN-9896 URL: https://issues.apache.org/jira/browse/YARN-9896 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-6825) RM quit due to ApplicationStateData exceed the limit size of znode in zk

[ https://issues.apache.org/jira/browse/YARN-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16822960#comment-16822960 ] Xianghao Lu commented on YARN-6825: --- [~Feng Yuan] as what [~bibinchundatt] said， applicationUpdate can

[jira] [Updated] (YARN-9498) ZooKeeper data size limit make YARN cluster down

[ https://issues.apache.org/jira/browse/YARN-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-9498: -- Attachment: YARN-9498.001.patch > ZooKeeper data size limit make YARN cluster down >

[jira] [Created] (YARN-9498) ZooKeeper data size limit make YARN cluster down

Xianghao Lu created YARN-9498: - Summary: ZooKeeper data size limit make YARN cluster down Key: YARN-9498 URL: https://issues.apache.org/jira/browse/YARN-9498 Project: Hadoop YARN Issue Type: Bug

[jira] [Commented] (YARN-3934) Application with large ApplicationSubmissionContext can cause RM to exit when ZK store is used

[ https://issues.apache.org/jira/browse/YARN-3934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814309#comment-16814309 ] Xianghao Lu commented on YARN-3934: --- seem duplicate as YARN-5006 > Application with large

[jira] [Commented] (YARN-7964) Yarn Scheduler Load Simulator (SLS): MetricsLogRunnable stops working when there are too many jobs needed to load from sls

[ https://issues.apache.org/jira/browse/YARN-7964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591456#comment-16591456 ] Xianghao Lu commented on YARN-7964: --- [~cxcw] Seems duplicate with YARN-8632. > Yarn Scheduler Load

[jira] [Commented] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591435#comment-16591435 ] Xianghao Lu commented on YARN-8632: --- [~yufeigu] Thanks for your review! Patch for 2.7 is not necessary

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Attachment: YARN-8632.004.patch > No data in file realtimetrack.json after running

[jira] [Comment Edited] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589918#comment-16589918 ] Xianghao Lu edited comment on YARN-8632 at 8/23/18 8:49 AM: It seems that

[jira] [Commented] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589918#comment-16589918 ] Xianghao Lu commented on YARN-8632: --- It seems that "setUncaughtExceptionHandler" is not suitable in

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Attachment: YARN-8632.003.patch > No data in file realtimetrack.json after running

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Description: Recently, I have been using

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Attachment: YARN-8632.002.patch > No data in file realtimetrack.json after running

[jira] [Commented] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16583766#comment-16583766 ] Xianghao Lu commented on YARN-8632: --- Thanks for your review! {quote} It is not a good practice to catch

[jira] [Commented] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16578158#comment-16578158 ] Xianghao Lu commented on YARN-8632: --- Sorry for unclear information! I have updated the patch, the target

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Attachment: (was: YARN-8632.001.patch) > No data in file realtimetrack.json after running

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Attachment: YARN-8632.001.patch > No data in file realtimetrack.json after running

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Attachment: YARN-8632-branch-2.7.2.001.patch > No data in file realtimetrack.json after running

[jira] [Commented] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16576121#comment-16576121 ] Xianghao Lu commented on YARN-8632: --- [~ywskycn] or [~yufeigu]  Woud you like to review the patch?

[jira] [Resolved] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu resolved YARN-8609. --- Resolution: Duplicate > NM oom because of large container statuses >

[jira] [Commented] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572565#comment-16572565 ] Xianghao Lu commented on YARN-8609: --- {quote} Those looking for a JIRA and finding the summary matching

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Attachment: YARN-8632.001.patch > No data in file realtimetrack.json after running

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Description: Recently, I have beenning using

[jira] [Updated] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

[ https://issues.apache.org/jira/browse/YARN-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8632: -- Description: Recently, I have beenning using

[jira] [Created] (YARN-8632) No data in file realtimetrack.json after running SchedulerLoadSimulator

Xianghao Lu created YARN-8632: - Summary: No data in file realtimetrack.json after running SchedulerLoadSimulator Key: YARN-8632 URL: https://issues.apache.org/jira/browse/YARN-8632 Project: Hadoop YARN

[jira] [Comment Edited] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571033#comment-16571033 ] Xianghao Lu edited comment on YARN-8609 at 8/7/18 2:36 AM: --- Thank you for your

[jira] [Comment Edited] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571033#comment-16571033 ] Xianghao Lu edited comment on YARN-8609 at 8/7/18 2:21 AM: --- Thank you for your

[jira] [Commented] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16571033#comment-16571033 ] Xianghao Lu commented on YARN-8609: --- Thank you for your patience! I know what you say, and my hadoop

[jira] [Commented] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567706#comment-16567706 ] Xianghao Lu commented on YARN-8609: --- Thanks for your comment. I have updated my patch according to your

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Attachment: YARN-8609.001.patch > NM oom because of large container statuses >

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Attachment: (was: YARN-8609.001.patch) > NM oom because of large container statuses >

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Attachment: YARN-8609.001.patch > NM oom because of large container statuses >

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Attachment: (was: YARN-8609.001.patch) > NM oom because of large container statuses >

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Description: Sometimes, NodeManger will send large container statuses to ResourceManager when

[jira] [Commented] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565195#comment-16565195 ] Xianghao Lu commented on YARN-8609: --- Seems to be related to

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Attachment: oom.jpeg > NM oom because of large container statuses >

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Attachment: YARN-8609.001.patch > NM oom because of large container statuses >

[jira] [Updated] (YARN-8609) NM oom because of large container statuses

[ https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xianghao Lu updated YARN-8609: -- Attachment: contain_status.jpg > NM oom because of large container statuses >

[jira] [Created] (YARN-8609) NM oom because of large container statuses

Xianghao Lu created YARN-8609: - Summary: NM oom because of large container statuses Key: YARN-8609 URL: https://issues.apache.org/jira/browse/YARN-8609 Project: Hadoop YARN Issue Type: Bug