[jira] [Updated] (YARN-10341) Yarn Service Container Completed event doesn't get processed

[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10341: - Attachment: YARN-10341.004.patch > Yarn Service Container Completed event doesn't get processed >

[jira] [Commented] (YARN-10344) Sync netty versions in hadoop-yarn-csi

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

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154189#comment-17154189 ] Masatake Iwasaki commented on YARN-10347: - Since this was brought by the backported patch of

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154183#comment-17154183 ] Brahma Reddy Battula commented on YARN-10347: - [~iwasakims], thanks for reporting this.. Same

[jira] [Commented] (YARN-10324) Fetch data from NodeManager may case read timeout when disk is busy

[ https://issues.apache.org/jira/browse/YARN-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154155#comment-17154155 ] Brahma Reddy Battula commented on YARN-10324: - Updated the target version to 3.3.1 as 3.3.0

[jira] [Updated] (YARN-10324) Fetch data from NodeManager may case read timeout when disk is busy

[ https://issues.apache.org/jira/browse/YARN-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula updated YARN-10324: Target Version/s: 2.7.8, 3.3.1 (was: 2.7.8, 3.3.0) > Fetch data from NodeManager

[jira] [Commented] (YARN-10348) Allow RM to always cancel tokens after app completes

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

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154081#comment-17154081 ] Masatake Iwasaki commented on YARN-10347: - committed to branch-3.1. > Fix double locking in

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154075#comment-17154075 ] Masatake Iwasaki commented on YARN-10347: - I got no relevant failure. {noformat} [INFO] Results:

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154071#comment-17154071 ] Masatake Iwasaki commented on YARN-10347: - Thanks, [~ayushtkn]. I'm running {{mvn test}} in

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154062#comment-17154062 ] Ayush Saxena commented on YARN-10347: - hmm, need to see what triggered this at jenkins. Anyway the

[jira] [Commented] (YARN-10348) Allow RM to always cancel tokens after app completes

[ https://issues.apache.org/jira/browse/YARN-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154048#comment-17154048 ] Jim Brennan commented on YARN-10348: I have verified that

[jira] [Updated] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated YARN-10347: Description: Double locking blocks another threads in ResourceManager waiting for the

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154034#comment-17154034 ] Masatake Iwasaki commented on YARN-10347: - Yes. The QA build failed on docker image creation

[jira] [Commented] (YARN-10348) Allow RM to always cancel tokens after app completes

[ https://issues.apache.org/jira/browse/YARN-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154011#comment-17154011 ] Jim Brennan commented on YARN-10348: patch 002 addresses the checkstyle issues and adds an entry to

[jira] [Comment Edited] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154009#comment-17154009 ] Ayush Saxena edited comment on YARN-10347 at 7/8/20, 8:59 PM: -- Thanx

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154009#comment-17154009 ] Ayush Saxena commented on YARN-10347: - Thanx [~iwasakims]  for the fix. Changes seems fair enough,

[jira] [Updated] (YARN-10348) Allow RM to always cancel tokens after app completes

[ https://issues.apache.org/jira/browse/YARN-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Brennan updated YARN-10348: --- Attachment: YARN-10348.002.patch > Allow RM to always cancel tokens after app completes >

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

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

[jira] [Commented] (YARN-10348) Allow RM to always cancel tokens after app completes

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

[jira] [Commented] (YARN-10348) Allow RM to always cancel tokens after app completes

[ https://issues.apache.org/jira/browse/YARN-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153754#comment-17153754 ] Jim Brennan commented on YARN-10348: patch 001 adds a new YARN configuration property: {noformat}

[jira] [Created] (YARN-10348) Allow RM to always cancel tokens after app completes

Jim Brennan created YARN-10348: -- Summary: Allow RM to always cancel tokens after app completes Key: YARN-10348 URL: https://issues.apache.org/jira/browse/YARN-10348 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

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

[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed

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

[jira] [Updated] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

[ https://issues.apache.org/jira/browse/YARN-10347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated YARN-10347: Attachment: YARN-10347-branch-3.1.001.patch > Fix double locking in

[jira] [Created] (YARN-10347) Fix double locking in CapacityScheduler#reinitialize in branch-3.1

Masatake Iwasaki created YARN-10347: --- Summary: Fix double locking in CapacityScheduler#reinitialize in branch-3.1 Key: YARN-10347 URL: https://issues.apache.org/jira/browse/YARN-10347 Project:

[jira] [Updated] (YARN-10341) Yarn Service Container Completed event doesn't get processed

[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10341: - Attachment: YARN-10341.003.patch > Yarn Service Container Completed event doesn't get processed >

[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed

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

[jira] [Commented] (YARN-10341) Yarn Service Container Completed event doesn't get processed

[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153525#comment-17153525 ] Bilwa S T commented on YARN-10341: -- Thanks [~brahmareddy] [~billie] for reviewing. I have added testcase

[jira] [Updated] (YARN-10341) Yarn Service Container Completed event doesn't get processed

[ https://issues.apache.org/jira/browse/YARN-10341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10341: - Attachment: YARN-10341.002.patch > Yarn Service Container Completed event doesn't get processed >

[jira] [Commented] (YARN-8047) RMWebApp make external class pluggable

[ https://issues.apache.org/jira/browse/YARN-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153466#comment-17153466 ] Bilwa S T commented on YARN-8047: - Thanks [~prabhujoseph] . Raised YARN-10346 for adding testcase. >

[jira] [Created] (YARN-10346) Add testcase for RMWebApp make external class pluggable

Bilwa S T created YARN-10346: Summary: Add testcase for RMWebApp make external class pluggable Key: YARN-10346 URL: https://issues.apache.org/jira/browse/YARN-10346 Project: Hadoop YARN Issue

[jira] [Commented] (YARN-10333) YarnClient obtain Delegation Token for Log Aggregation Path

[ https://issues.apache.org/jira/browse/YARN-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153405#comment-17153405 ] Zhankun Tang commented on YARN-10333: - It LGTM. +1. Thanks for your contribution! [~prabhujoseph],

[jira] [Commented] (YARN-10333) YarnClient obtain Delegation Token for Log Aggregation Path

[ https://issues.apache.org/jira/browse/YARN-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153326#comment-17153326 ] Sunil G commented on YARN-10333: This change looks fine to me. cc [~ztang] [~bibinchundatt]

[jira] [Updated] (YARN-10340) HsWebServices getContainerReport uses loginUser instead of remoteUser to access ApplicationClientProtocol

[ https://issues.apache.org/jira/browse/YARN-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10340: - Parent: YARN-10025 Issue Type: Sub-task (was: Bug) > HsWebServices getContainerReport

[jira] [Updated] (YARN-10345) HsWebServices containerlogs does not honor ACLs for completed jobs

[ https://issues.apache.org/jira/browse/YARN-10345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10345: - Parent: YARN-10025 Issue Type: Sub-task (was: Bug) > HsWebServices containerlogs does

[jira] [Updated] (YARN-10345) HsWebServices containerlogs does not honor ACLs for completed jobs

[ https://issues.apache.org/jira/browse/YARN-10345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10345: - Affects Version/s: (was: 3.2.0) 3.2.2 3.3.0 >

[jira] [Updated] (YARN-10345) HsWebServices containerlogs does not honor ACLs for completed jobs

[ https://issues.apache.org/jira/browse/YARN-10345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10345: - Description: HsWebServices containerlogs does not honor ACLs. User who does not have permission

[jira] [Updated] (YARN-10345) HsWebServices containerlogs does not honor ACLs for completed jobs

[ https://issues.apache.org/jira/browse/YARN-10345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10345: - Description: HsWebServices containerlogs does not honor ACLs. User who does not have permission

[jira] [Created] (YARN-10345) HsWebServices containerlogs does not honor ACLs for completed jobs

Prabhu Joseph created YARN-10345: Summary: HsWebServices containerlogs does not honor ACLs for completed jobs Key: YARN-10345 URL: https://issues.apache.org/jira/browse/YARN-10345 Project: Hadoop

[jira] [Updated] (YARN-10345) HsWebServices containerlogs does not honor ACLs for completed jobs

[ https://issues.apache.org/jira/browse/YARN-10345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated YARN-10345: - Attachment: Screen Shot 2020-07-08 at 12.54.21 PM.png > HsWebServices containerlogs does not

[jira] [Commented] (YARN-8047) RMWebApp make external class pluggable

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

[jira] [Commented] (YARN-8047) RMWebApp make external class pluggable

[ https://issues.apache.org/jira/browse/YARN-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17153309#comment-17153309 ] Prabhu Joseph commented on YARN-8047: - Thanks [~BilwaST] for the patch. Have committed the latest