[jira] [Comment Edited] (YARN-9193) NullPointerException happens in RM while shutdown a NM

[ https://issues.apache.org/jira/browse/YARN-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742197#comment-16742197 ] lujie edited comment on YARN-9193 at 1/14/19 3:20 PM: -- it will be fixed in YARN-9194

[jira] [Comment Edited] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742132#comment-16742132 ] Dapeng Sun edited comment on YARN-9198 at 1/14/19 2:58 PM: --- Most of your

[jira] [Updated] (YARN-9194) Invalid event: REGISTERED at FAILED

[ https://issues.apache.org/jira/browse/YARN-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie updated YARN-9194: Attachment: YARN-9194_4.patch > Invalid event: REGISTERED at FAILED > --- > >

[jira] [Commented] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742132#comment-16742132 ] Dapeng Sun commented on YARN-9198: -- Most of your options are reasonable for me, it is better to find and

[jira] [Resolved] (YARN-9193) NullPointerException happens in RM while shutdown a NM

[ https://issues.apache.org/jira/browse/YARN-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lujie resolved YARN-9193. - Resolution: Duplicate it will be fixed in [YARN-9194link title|https://issues.apache.org/jira/browse/YARN-9194]

[jira] [Commented] (YARN-9194) Invalid event: REGISTERED at FAILED

[ https://issues.apache.org/jira/browse/YARN-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742175#comment-16742175 ] lujie commented on YARN-9194: - HI:[~wilfreds] Thanks for your kindly review! {code:java} That looks strange:

[jira] [Commented] (YARN-9074) Docker container rm command should be executed after stop

[ https://issues.apache.org/jira/browse/YARN-9074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742256#comment-16742256 ] Jim Brennan commented on YARN-9074: --- +1 (non-binding) this looks good to me.   > Docker container rm

[jira] [Commented] (YARN-9194) Invalid event: REGISTERED at FAILED

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

[jira] [Commented] (YARN-9191) Add cli option in DS to support enforceExecutionType in resource requests.

[ https://issues.apache.org/jira/browse/YARN-9191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742346#comment-16742346 ] Íñigo Goiri commented on YARN-9191: --- Yes, it looks like {{testDSShellWithOpportunisticContainers()}}

[jira] [Commented] (YARN-9150) Making TimelineSchemaCreator support different backends for Timeline Schema Creation in ATSv2

[ https://issues.apache.org/jira/browse/YARN-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742413#comment-16742413 ] Vrushali C commented on YARN-9150: -- thanks [~Sushil-K-S] ! + 1 on patch 002. One minor comment but we

[jira] [Commented] (YARN-9184) Docker run doesn't pull down latest image if the image exists locally

[ https://issues.apache.org/jira/browse/YARN-9184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742429#comment-16742429 ] Jim Brennan commented on YARN-9184: --- I also agree with [~ebadger] and [~eyang] that this should be a

[jira] [Updated] (YARN-6616) YARN AHS shows submitTime for jobs same as startTime

[ https://issues.apache.org/jira/browse/YARN-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-6616: Attachment: 0001-YARN-6616.patch > YARN AHS shows submitTime for jobs same as startTime >

[jira] [Assigned] (YARN-8625) Aggregate Resource Allocation for each job is not present in ATS

[ https://issues.apache.org/jira/browse/YARN-8625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph reassigned YARN-8625: --- Assignee: Prabhu Joseph > Aggregate Resource Allocation for each job is not present in ATS >

[jira] [Assigned] (YARN-8224) LogAggregation status TIME_OUT for absent container misleading

[ https://issues.apache.org/jira/browse/YARN-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph reassigned YARN-8224: --- Assignee: Prabhu Joseph > LogAggregation status TIME_OUT for absent container misleading >

[jira] [Commented] (YARN-6616) YARN AHS shows submitTime for jobs same as startTime

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

[jira] [Commented] (YARN-9188) Port YARN-7136 to branch-2

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

[jira] [Commented] (YARN-6616) YARN AHS shows submitTime for jobs same as startTime

[ https://issues.apache.org/jira/browse/YARN-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742520#comment-16742520 ] Kuhu Shukla commented on YARN-6616: --- I am currently reviewing this patch and the proposed change is a

[jira] [Commented] (YARN-9188) Port YARN-7136 to branch-2

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

[jira] [Updated] (YARN-9116) Capacity Scheduler: add the default maximum-allocation-mb and maximum-allocation-vcores for the queues

[ https://issues.apache.org/jira/browse/YARN-9116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated YARN-9116: --- Attachment: YARN-9116.2.patch > Capacity Scheduler: add the default maximum-allocation-mb and >

[jira] [Commented] (YARN-9200) Enable resource configuration of queue capacity for different resources independently

[ https://issues.apache.org/jira/browse/YARN-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742626#comment-16742626 ] Aihua Xu commented on YARN-9200: [~wangda], [~sunilg], [~cheersyang] Want to hear your thoughts. Would

[jira] [Commented] (YARN-9116) Capacity Scheduler: add the default maximum-allocation-mb and maximum-allocation-vcores for the queues

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

[jira] [Commented] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742711#comment-16742711 ] Jiandan Yang commented on YARN-9199: - Thanks [~bibinchundatt] for your comment, The new version of

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Affects Version/s: (was: 3.1.1) 3.1.3 > Compatible issue: AM throws

[jira] [Updated] (YARN-9195) RM Queue's pending container number might get decreased unexpectedly or even become negative once RM failover

[ https://issues.apache.org/jira/browse/YARN-9195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shengyang Sha updated YARN-9195: Description: Hi, all: Previously we have encountered a serious problem in ResourceManager, we

[jira] [Updated] (YARN-9200) Enable resource configuration of queue capacity for different resources independently

[ https://issues.apache.org/jira/browse/YARN-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated YARN-9200: --- Description: In capacity scheduler, currently two resource allocations are supported. 1. percentage

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.3 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Summary: Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.3 RM

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.3 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Description: *Background* Rolling upgrade Yarn from 2.7.2 to 3.1.3-SNAPSHOT; the version of RM is

[jira] [Updated] (YARN-9200) Enable resource configuration of queue capacity for different resources independently

[ https://issues.apache.org/jira/browse/YARN-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated YARN-9200: --- Description: In capacity scheduler, currently two resource allocations are supported. 1. percentage

[jira] [Assigned] (YARN-9200) Enable resource configuration of queue capacity for different resources independently

[ https://issues.apache.org/jira/browse/YARN-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu reassigned YARN-9200: -- Assignee: Aihua Xu > Enable resource configuration of queue capacity for different resources >

[jira] [Commented] (YARN-9190) [Submarine] Submarine job will fail to run as a first job on a new created Hadoop 3.2.0 RC1 cluster

[ https://issues.apache.org/jira/browse/YARN-9190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742654#comment-16742654 ] Zhankun Tang commented on YARN-9190: Yeah. And I did below steps to double-check: 3.2 submarine and

[jira] [Updated] (YARN-9179) Fix NPE in AbstractYarnScheduler#updateNewContainerInfo

[ https://issues.apache.org/jira/browse/YARN-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira Ajisaka updated YARN-9179: Summary: Fix NPE in AbstractYarnScheduler#updateNewContainerInfo (was: TestAMRMClient crashes) >

[jira] [Commented] (YARN-9179) Fix NPE in AbstractYarnScheduler#updateNewContainerInfo

[ https://issues.apache.org/jira/browse/YARN-9179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742731#comment-16742731 ] Hudson commented on YARN-9179: -- SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15773 (See

[jira] [Created] (YARN-9200) Enable resource configuration of queue capacity for different resources independently

Aihua Xu created YARN-9200: -- Summary: Enable resource configuration of queue capacity for different resources independently Key: YARN-9200 URL: https://issues.apache.org/jira/browse/YARN-9200 Project:

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Affects Version/s: 3.1.2 3.2.0 > Compatible issue: AM throws

[jira] [Updated] (YARN-9196) Attempt started time zone and Application started time zone is different when OS time zone is modified

[ https://issues.apache.org/jira/browse/YARN-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9196: Attachment: YARN-9196-001.patch > Attempt started time zone and Application started time zone is different

[jira] [Commented] (YARN-9196) Attempt started time zone and Application started time zone is different when OS time zone is modified

[ https://issues.apache.org/jira/browse/YARN-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742754#comment-16742754 ] Bilwa S T commented on YARN-9196: - Attempt start time format should also be formed at server side >

[jira] [Commented] (YARN-9196) Attempt started time zone and Application started time zone is different when OS time zone is modified

[ https://issues.apache.org/jira/browse/YARN-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742755#comment-16742755 ] Bilwa S T commented on YARN-9196: - cc [~bibinchundatt] > Attempt started time zone and Application

[jira] [Commented] (YARN-6616) YARN AHS shows submitTime for jobs same as startTime

[ https://issues.apache.org/jira/browse/YARN-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742782#comment-16742782 ] Prabhu Joseph commented on YARN-6616: - Thanks [~kshukla] for the review. Working on the review

[jira] [Assigned] (YARN-9196) Attempt started time zone and Application started time zone is different when OS time zone is modified

[ https://issues.apache.org/jira/browse/YARN-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-9196: --- Assignee: Bilwa S T > Attempt started time zone and Application started time zone is different when

[jira] [Created] (YARN-9196) Attempt started time zone and Application started time zone is different when OS time zone is modified

Bilwa S T created YARN-9196: --- Summary: Attempt started time zone and Application started time zone is different when OS time zone is modified Key: YARN-9196 URL: https://issues.apache.org/jira/browse/YARN-9196

[jira] [Created] (YARN-9197) NPE in service AM when failed to launch container

kyungwan nam created YARN-9197: -- Summary: NPE in service AM when failed to launch container Key: YARN-9197 URL: https://issues.apache.org/jira/browse/YARN-9197 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-9197) NPE in service AM when failed to launch container

[ https://issues.apache.org/jira/browse/YARN-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam updated YARN-9197: --- Attachment: YARN-9197.001.patch > NPE in service AM when failed to launch container >

[jira] [Created] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

Dapeng Sun created YARN-9198: Summary: Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler Key: YARN-9198 URL: https://issues.apache.org/jira/browse/YARN-9198

[jira] [Assigned] (YARN-9197) NPE in service AM when failed to launch container

[ https://issues.apache.org/jira/browse/YARN-9197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kyungwan nam reassigned YARN-9197: -- Assignee: kyungwan nam > NPE in service AM when failed to launch container >

[jira] [Updated] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dapeng Sun updated YARN-9198: - Attachment: YARN-9198.001.patch > Corrupted state from a previous version can still cause RM to fail with

[jira] [Commented] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741887#comment-16741887 ] Dapeng Sun commented on YARN-9198: -- Attach a simple patch to fix it. > Corrupted state from a previous

[jira] [Comment Edited] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741887#comment-16741887 ] Dapeng Sun edited comment on YARN-9198 at 1/14/19 9:38 AM: --- Attached a simple

[jira] [Created] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

Jiandan Yang created YARN-9199: --- Summary: Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM Key: YARN-9199 URL: https://issues.apache.org/jira/browse/YARN-9199

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Description: *Background* Rolling upgrade Yarn from 2.7.2 to 3.1.1; the version of RM is 3.1.1,

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Description: *Background* Rolling upgrade Yarn from 2.7.2 to 3.1.1; the version of RM is 3.1.1,

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Description: *Background* Rolling upgrade Yarn from 2.7.2 to 3.1.1; the version of RM and some NM

[jira] [Commented] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741893#comment-16741893 ] Jiandan Yang commented on YARN-9199: - this problem is introduced by YARN-7974, I think RM should

[jira] [Commented] (YARN-9148) AggregatedLogDeletion doesnt work with S3

[ https://issues.apache.org/jira/browse/YARN-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742057#comment-16742057 ] Steve Loughran commented on YARN-9148: -- If there's an existing one for real filesystems, stick with

[jira] [Commented] (YARN-9193) NullPointerException happens in RM while shutdown a NM

[ https://issues.apache.org/jira/browse/YARN-9193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742063#comment-16742063 ] Wilfred Spiegelenburg commented on YARN-9193: - [~xiaoheipangzi] if this is really the same

[jira] [Commented] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742077#comment-16742077 ] Wilfred Spiegelenburg commented on YARN-9198: - As I [commented in the previous

[jira] [Commented] (YARN-9197) NPE in service AM when failed to launch container

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

[jira] [Commented] (YARN-9148) AggregatedLogDeletion doesnt work with S3

[ https://issues.apache.org/jira/browse/YARN-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741951#comment-16741951 ] Steve Loughran commented on YARN-9148: -- General * newline betwee import java. and org.apache.

[jira] [Commented] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

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

[jira] [Assigned] (YARN-7913) Improve error handling when application recovery fails with exception

[ https://issues.apache.org/jira/browse/YARN-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YARN-7913: --- Assignee: Wilfred Spiegelenburg (was: Gergo Repas) > Improve error handling

[jira] [Commented] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742031#comment-16742031 ] Wilfred Spiegelenburg commented on YARN-9198: - [~dapengsun] can you explain a bit more about

[jira] [Commented] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742065#comment-16742065 ] Bibin A Chundatt commented on YARN-9199: [~yangjiandan] IIUC YARN-7974 is not part of 3.1.1 >

[jira] [Updated] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

[ https://issues.apache.org/jira/browse/YARN-9199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiandan Yang updated YARN-9199: Attachment: YARN-9199.001.patch > Compatible issue: AM throws NoSuchMethodError when 2.7.2 client

[jira] [Commented] (YARN-9199) Compatible issue: AM throws NoSuchMethodError when 2.7.2 client submits mr job to 3.1.1 RM

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

[jira] [Commented] (YARN-9194) Invalid event: REGISTERED at FAILED

[ https://issues.apache.org/jira/browse/YARN-9194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742061#comment-16742061 ] Wilfred Spiegelenburg commented on YARN-9194: - Thank you for logging this jira

[jira] [Commented] (YARN-9148) AggregatedLogDeletion doesnt work with S3

[ https://issues.apache.org/jira/browse/YARN-9148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16741974#comment-16741974 ] Bibin A Chundatt commented on YARN-9148: Thank you [~ste...@apache.org] for review {quote}There

[jira] [Commented] (YARN-9198) Corrupted state from a previous version can still cause RM to fail with NPE on FairScheduler

[ https://issues.apache.org/jira/browse/YARN-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742049#comment-16742049 ] Dapeng Sun commented on YARN-9198: -- Hi [~wilfreds], thank you for your comments :) The exception reported