[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143079#comment-17143079 ] Bilwa S T commented on YARN-10229: -- [~elgoiri] Thanks for reviewing. Updated patch. Handled removing

[jira] [Updated] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10229: - Attachment: YARN-10229.002.patch > [Federation] Client should be able to submit application to RM

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143177#comment-17143177 ] Bilwa S T commented on YARN-10229: -- fixed checkstyle issues in .003 patch > [Federation] Client should

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143172#comment-17143172 ] Bilwa S T commented on YARN-10229: -- [~elgoiri] do i need to add  

[jira] [Updated] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10229: - Attachment: YARN-10229.003.patch > [Federation] Client should be able to submit application to RM

[jira] [Updated] (YARN-10328) Too many ZK Curator NodeExists exception logs in YARN Service AM logs

[ https://issues.apache.org/jira/browse/YARN-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10328: - Summary: Too many ZK Curator NodeExists exception logs in YARN Service AM logs (was: Too many ZK

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143948#comment-17143948 ] Bilwa S T commented on YARN-10229: -- Hi [~youchen] * AMRMProxyEnabled is true even if distributed

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17143985#comment-17143985 ] Bilwa S T commented on YARN-10229: -- handled review comments in patch .005 > [Federation] Client should

[jira] [Updated] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10229: - Attachment: YARN-10229.005.patch > [Federation] Client should be able to submit application to RM

[jira] [Updated] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10229: - Attachment: YARN-10229.006.patch > [Federation] Client should be able to submit application to RM

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146473#comment-17146473 ] Bilwa S T commented on YARN-10229: -- Hi [~youchen] I have attached a patch. Please take a look at it >

[jira] [Commented] (YARN-10328) Too many ZK Curator NodeExists exception logs in YARN Service AM logs

[ https://issues.apache.org/jira/browse/YARN-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146485#comment-17146485 ] Bilwa S T commented on YARN-10328: -- cc [~eyang] > Too many ZK Curator NodeExists exception logs in YARN

[jira] [Updated] (YARN-10328) Too many ZK Curator NodeExists exception logs in YARN Service AM logs

[ https://issues.apache.org/jira/browse/YARN-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10328: - Attachment: YARN-10328.001.patch > Too many ZK Curator NodeExists exception logs in YARN Service AM logs

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147015#comment-17147015 ] Bilwa S T commented on YARN-10229: -- Hi [~youchen] I moved all changes to AMRMProxyService. Please take

[jira] [Updated] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10229: - Attachment: YARN-10229.007.patch > [Federation] Client should be able to submit application to RM

[jira] [Updated] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10229: - Attachment: YARN-10229.008.patch > [Federation] Client should be able to submit application to RM

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148026#comment-17148026 ] Bilwa S T commented on YARN-10229: -- Thanks [~elgoiri] for reviewing. Fixed checkstyle issues in .008

[jira] [Commented] (YARN-10328) Too many ZK Curator NodeExists exception logs in YARN Service AM logs

[ https://issues.apache.org/jira/browse/YARN-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147947#comment-17147947 ] Bilwa S T commented on YARN-10328: -- Thanks [~eyang] > Too many ZK Curator NodeExists exception logs in

[jira] [Updated] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10311: - Attachment: YARN-10311.002.patch > Yarn Service should support obtaining tokens from multiple name

[jira] [Updated] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10311: - Attachment: YARN-10311.002.patch > Yarn Service should support obtaining tokens from multiple name

[jira] [Updated] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10311: - Attachment: (was: YARN-10311.002.patch) > Yarn Service should support obtaining tokens from multiple

[jira] [Commented] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136735#comment-17136735 ] Bilwa S T commented on YARN-10311: -- Hi [~eyang] I have updated patch. Please take a look > Yarn Service

[jira] [Commented] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136299#comment-17136299 ] Bilwa S T commented on YARN-10311: -- Hi [~eyang] Yes There is conf called "dfs.nameservices" which we

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136826#comment-17136826 ] Bilwa S T commented on YARN-10310: -- Hi [~eyang] I ran below command which calls ServiceClient directly.

[jira] [Commented] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17137831#comment-17137831 ] Bilwa S T commented on YARN-10311: -- [~eyang] We have similar conf in mapreduce

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140747#comment-17140747 ] Bilwa S T commented on YARN-10229: -- Hi [~elgoiri] Tested on CentOS Linux release 7.6.1810 Below are

[jira] [Commented] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144635#comment-17144635 ] Bilwa S T commented on YARN-10229: -- Hi [~youchen] Yes i didn't wanted to change behaviour if distr

[jira] [Updated] (YARN-10229) [Federation] Client should be able to submit application to RM directly using normal client conf

[ https://issues.apache.org/jira/browse/YARN-10229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10229: - Attachment: YARN-10229.004.patch > [Federation] Client should be able to submit application to RM

[jira] [Created] (YARN-10328) Too many ZK Curator NodeExists logs in YARN Service AM logs

Bilwa S T created YARN-10328: Summary: Too many ZK Curator NodeExists logs in YARN Service AM logs Key: YARN-10328 URL: https://issues.apache.org/jira/browse/YARN-10328 Project: Hadoop YARN

[jira] [Comment Edited] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17137965#comment-17137965 ] Bilwa S T edited comment on YARN-10310 at 6/16/20, 10:47 PM: - [~eyang] Thanks

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17137965#comment-17137965 ] Bilwa S T commented on YARN-10310: -- [~eyang] Thanks for explaination. Let me explain my testing steps. I

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130066#comment-17130066 ] Bilwa S T commented on YARN-10310: -- Testing done for this. > YARN Service - User is able to launch a

[jira] [Comment Edited] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130066#comment-17130066 ] Bilwa S T edited comment on YARN-10310 at 6/10/20, 4:50 AM: Testing done for

[jira] [Comment Edited] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130066#comment-17130066 ] Bilwa S T edited comment on YARN-10310 at 6/10/20, 4:51 AM: Hi [~eyang]

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130360#comment-17130360 ] Bilwa S T commented on YARN-10310: -- Hi [~eyang] i meant patch is working fine. its working as expected

[jira] [Assigned] (YARN-9641) ApplicationMasterService#AllocateResponseLock need to hold only ResponseID

[ https://issues.apache.org/jira/browse/YARN-9641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-9641: --- Assignee: (was: Bilwa S T) > ApplicationMasterService#AllocateResponseLock need to hold only

[jira] [Assigned] (YARN-8671) Container Launch failed stating "TaskAttempt killed because it ran on unusable node , Container released on a *lost* node"

[ https://issues.apache.org/jira/browse/YARN-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-8671: --- Assignee: (was: Bilwa S T) > Container Launch failed stating "TaskAttempt killed because it ran

[jira] [Assigned] (YARN-10266) Setting debug delay to a too high number will cause NM fail to start

[ https://issues.apache.org/jira/browse/YARN-10266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10266: Assignee: (was: Bilwa S T) > Setting debug delay to a too high number will cause NM fail to

[jira] [Assigned] (YARN-9618) NodeListManager event improvement

[ https://issues.apache.org/jira/browse/YARN-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-9618: --- Assignee: (was: Bilwa S T) > NodeListManager event improvement >

[jira] [Assigned] (YARN-9048) Add znode hierarchy in Federation ZK State Store

[ https://issues.apache.org/jira/browse/YARN-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-9048: --- Assignee: (was: Bilwa S T) > Add znode hierarchy in Federation ZK State Store >

[jira] [Assigned] (YARN-5604) Add versioning for FederationStateStore

[ https://issues.apache.org/jira/browse/YARN-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-5604: --- Assignee: (was: Bilwa S T) > Add versioning for FederationStateStore >

[jira] [Assigned] (YARN-10133) For yarn Federation, there is no routeradmin command to manage

[ https://issues.apache.org/jira/browse/YARN-10133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10133: Assignee: (was: Bilwa S T) > For yarn Federation, there is no routeradmin command to manage >

[jira] [Assigned] (YARN-10131) In Federation,few yarn application commands do not work

[ https://issues.apache.org/jira/browse/YARN-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10131: Assignee: (was: Bilwa S T) > In Federation,few yarn application commands do not work >

[jira] [Assigned] (YARN-10275) CapacityScheduler QueuePath object should be able to parse paths

[ https://issues.apache.org/jira/browse/YARN-10275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10275: Assignee: (was: Bilwa S T) > CapacityScheduler QueuePath object should be able to parse paths

[jira] [Assigned] (YARN-10121) In Federation executing yarn queue status command throws an exception

[ https://issues.apache.org/jira/browse/YARN-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10121: Assignee: (was: Bilwa S T) > In Federation executing yarn queue status command throws an

[jira] [Assigned] (YARN-10111) In Federation cluster Distributed Shell Application submission fails as YarnClient#getQueueInfo is not implemented

[ https://issues.apache.org/jira/browse/YARN-10111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10111: Assignee: (was: Bilwa S T) > In Federation cluster Distributed Shell Application submission

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130338#comment-17130338 ] Bilwa S T commented on YARN-10310: -- [~eyang] I tested after applying patch by launching with same name.

[jira] [Commented] (YARN-9460) QueueACLsManager and ReservationsACLManager should not use instanceof checks

[ https://issues.apache.org/jira/browse/YARN-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130456#comment-17130456 ] Bilwa S T commented on YARN-9460: - Hi [~pbacsko] # I will update 

[jira] [Updated] (YARN-10308) Update javadoc and variable names for keytab in yarn services as it supports filesystems other than hdfs and local file system

[ https://issues.apache.org/jira/browse/YARN-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10308: - Attachment: YARN-10308.002.patch > Update javadoc and variable names for keytab in yarn services as it

[jira] [Commented] (YARN-10308) Update javadoc and variable names for keytab in yarn services as it supports filesystems other than hdfs and local file system

[ https://issues.apache.org/jira/browse/YARN-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17130484#comment-17130484 ] Bilwa S T commented on YARN-10308: -- Hi [~eyang] i have tested patch YARN-9002 on viewfs file system. It

[jira] [Created] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

Bilwa S T created YARN-10311: Summary: Yarn Service should support obtaining tokens from multiple name services Key: YARN-10311 URL: https://issues.apache.org/jira/browse/YARN-10311 Project: Hadoop YARN

[jira] [Commented] (YARN-10279) Avoid unnecessary QueueMappingEntity creations

[ https://issues.apache.org/jira/browse/YARN-10279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124908#comment-17124908 ] Bilwa S T commented on YARN-10279: -- [~adam.antal] you can take it over > Avoid unnecessary

[jira] [Commented] (YARN-10181) Managing Centralized Node Attribute via RMWebServices.

[ https://issues.apache.org/jira/browse/YARN-10181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124773#comment-17124773 ] Bilwa S T commented on YARN-10181: -- [~prabhujoseph] ok will do it today. can i reassign that jira? >

[jira] [Commented] (YARN-9971) YARN Native Service HttpProbe logs THIS_HOST in error messages

[ https://issues.apache.org/jira/browse/YARN-9971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124817#comment-17124817 ] Bilwa S T commented on YARN-9971: - [~prabhujoseph] can i assign this jira as there is no update on this?

[jira] [Updated] (YARN-6857) Support REST for Node Attributes configurations

[ https://issues.apache.org/jira/browse/YARN-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6857: Attachment: YARN-6857.003.patch > Support REST for Node Attributes configurations >

[jira] [Commented] (YARN-6857) Support REST for Node Attributes configurations

[ https://issues.apache.org/jira/browse/YARN-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126080#comment-17126080 ] Bilwa S T commented on YARN-6857: - Fixed checkstyle and UT > Support REST for Node Attributes

[jira] [Commented] (YARN-6857) Support REST for Node Attributes configurations

[ https://issues.apache.org/jira/browse/YARN-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125940#comment-17125940 ] Bilwa S T commented on YARN-6857: - Thanks [~Naganarasimha]. [~prabhujoseph] I have attached patch.

[jira] [Updated] (YARN-6857) Support REST for Node Attributes configurations

[ https://issues.apache.org/jira/browse/YARN-6857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6857: Attachment: YARN-6857.002.patch > Support REST for Node Attributes configurations >

[jira] [Created] (YARN-10308) Update javadoc and variable names for keytab in yarn services as it supports schemes other than hdfs and local file system

Bilwa S T created YARN-10308: Summary: Update javadoc and variable names for keytab in yarn services as it supports schemes other than hdfs and local file system Key: YARN-10308 URL:

[jira] [Updated] (YARN-10308) Update javadoc and variable names for keytab in yarn services as it supports filesystems other than hdfs and local file system

[ https://issues.apache.org/jira/browse/YARN-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10308: - Summary: Update javadoc and variable names for keytab in yarn services as it supports filesystems other

[jira] [Created] (YARN-10310) YARN Service - User is able to launch a service with same name

Bilwa S T created YARN-10310: Summary: YARN Service - User is able to launch a service with same name Key: YARN-10310 URL: https://issues.apache.org/jira/browse/YARN-10310 Project: Hadoop YARN

[jira] [Updated] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10310: - Attachment: YARN-10310.001.patch > YARN Service - User is able to launch a service with same name >

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17128488#comment-17128488 ] Bilwa S T commented on YARN-10310: -- cc [~eyang] > YARN Service - User is able to launch a service with

[jira] [Updated] (YARN-10308) Update javadoc and variable names for keytab in yarn services as it supports filesystems other than hdfs and local file system

[ https://issues.apache.org/jira/browse/YARN-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10308: - Attachment: YARN-10308.001.patch > Update javadoc and variable names for keytab in yarn services as it

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129454#comment-17129454 ] Bilwa S T commented on YARN-10310: -- Thanks [~eyang] for reviewing. > YARN Service - User is able to

[jira] [Updated] (YARN-9460) QueueACLsManager and ReservationsACLManager should not use instanceof checks

[ https://issues.apache.org/jira/browse/YARN-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9460: Attachment: YARN-9460.004.patch > QueueACLsManager and ReservationsACLManager should not use instanceof

[jira] [Commented] (YARN-10308) Update javadoc and variable names for keytab in yarn services as it supports filesystems other than hdfs and local file system

[ https://issues.apache.org/jira/browse/YARN-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129497#comment-17129497 ] Bilwa S T commented on YARN-10308: -- cc [~eyang] > Update javadoc and variable names for keytab in yarn

[jira] [Commented] (YARN-10308) Update javadoc and variable names for keytab in yarn services as it supports filesystems other than hdfs and local file system

[ https://issues.apache.org/jira/browse/YARN-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17129655#comment-17129655 ] Bilwa S T commented on YARN-10308: -- Thanks [~eyang] for taking a look at patch. I will test with viewfs

[jira] [Commented] (YARN-9460) QueueACLsManager and ReservationsACLManager should not use instanceof checks

[ https://issues.apache.org/jira/browse/YARN-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126465#comment-17126465 ] Bilwa S T commented on YARN-9460: - cc [~inigoiri] > QueueACLsManager and ReservationsACLManager should

[jira] [Updated] (YARN-9460) QueueACLsManager and ReservationsACLManager should not use instanceof checks

[ https://issues.apache.org/jira/browse/YARN-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9460: Attachment: YARN-9460.005.patch > QueueACLsManager and ReservationsACLManager should not use instanceof

[jira] [Commented] (YARN-9460) QueueACLsManager and ReservationsACLManager should not use instanceof checks

[ https://issues.apache.org/jira/browse/YARN-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17133277#comment-17133277 ] Bilwa S T commented on YARN-9460: - added @SuppressWarnings("checkstyle:visibilitymodifier") to avoid

[jira] [Comment Edited] (YARN-6539) Create SecureLogin inside Router

[ https://issues.apache.org/jira/browse/YARN-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134121#comment-17134121 ] Bilwa S T edited comment on YARN-6539 at 6/12/20, 10:49 AM: Hi [~yifan.stan]

[jira] [Commented] (YARN-6539) Create SecureLogin inside Router

[ https://issues.apache.org/jira/browse/YARN-6539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134121#comment-17134121 ] Bilwa S T commented on YARN-6539: - Hi [~yifan.stan] > Create SecureLogin inside Router >

[jira] [Assigned] (YARN-9872) DecommissioningNodesWatcher#update blocks the heartbeat processing

[ https://issues.apache.org/jira/browse/YARN-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-9872: --- Assignee: (was: Bilwa S T) > DecommissioningNodesWatcher#update blocks the heartbeat processing

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134382#comment-17134382 ] Bilwa S T commented on YARN-10310: -- Hi [~eyang] please check this when you get free time. Thanks > YARN

[jira] [Commented] (YARN-10310) YARN Service - User is able to launch a service with same name

[ https://issues.apache.org/jira/browse/YARN-10310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134448#comment-17134448 ] Bilwa S T commented on YARN-10310: -- [~eyang] okay > YARN Service - User is able to launch a service

[jira] [Commented] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134446#comment-17134446 ] Bilwa S T commented on YARN-10311: -- cc [~eyang] > Yarn Service should support obtaining tokens from

[jira] [Updated] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10311: - Attachment: YARN-10311.001.patch > Yarn Service should support obtaining tokens from multiple name

[jira] [Commented] (YARN-6526) Refactoring SQLFederationStateStore by avoiding to recreate a connection at every call

[ https://issues.apache.org/jira/browse/YARN-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134376#comment-17134376 ] Bilwa S T commented on YARN-6526: - [~elgoiri] Can you please take a look at this when you are free? Thanks

[jira] [Commented] (YARN-10311) Yarn Service should support obtaining tokens from multiple name services

[ https://issues.apache.org/jira/browse/YARN-10311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17134651#comment-17134651 ] Bilwa S T commented on YARN-10311: -- [~eyang] Client is the one who gets DT from NN and sends it to RM

[jira] [Updated] (YARN-9460) QueueACLsManager and ReservationsACLManager should not use instanceof checks

[ https://issues.apache.org/jira/browse/YARN-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9460: Attachment: YARN-9460.003.patch > QueueACLsManager and ReservationsACLManager should not use instanceof

[jira] [Commented] (YARN-9460) QueueACLsManager and ReservationsACLManager should not use instanceof checks

[ https://issues.apache.org/jira/browse/YARN-9460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126919#comment-17126919 ] Bilwa S T commented on YARN-9460: - Hi [~pbacsko] Thanks for review. Yes you are correct. behaviour wont

[jira] [Updated] (YARN-10359) Log container report only if list is not empty

[ https://issues.apache.org/jira/browse/YARN-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10359: - Attachment: YARN-10359.002.patch > Log container report only if list is not empty >

[jira] [Commented] (YARN-10364) Absolute Resource [memory=0] is considered as Percentage config type

[ https://issues.apache.org/jira/browse/YARN-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17165056#comment-17165056 ] Bilwa S T commented on YARN-10364: -- Hi [~prabhujoseph] This is because

[jira] [Assigned] (YARN-10364) Absolute Resource [memory=0] is considered as Percentage config type

[ https://issues.apache.org/jira/browse/YARN-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10364: Assignee: Bilwa S T (was: Prabhu Joseph) > Absolute Resource [memory=0] is considered as

[jira] [Commented] (YARN-10369) Make NMTokenSecretManagerInRM sending NMToken for nodeId DEBUG

[ https://issues.apache.org/jira/browse/YARN-10369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166923#comment-17166923 ] Bilwa S T commented on YARN-10369: -- +1 (Non-binding) > Make NMTokenSecretManagerInRM sending NMToken

[jira] [Updated] (YARN-10364) Absolute Resource [memory=0] is considered as Percentage config type

[ https://issues.apache.org/jira/browse/YARN-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10364: - Attachment: YARN-10364.001.patch > Absolute Resource [memory=0] is considered as Percentage config type

[jira] [Updated] (YARN-10364) Absolute Resource [memory=0] is considered as Percentage config type

[ https://issues.apache.org/jira/browse/YARN-10364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10364: - Attachment: YARN-10364.002.patch > Absolute Resource [memory=0] is considered as Percentage config type

[jira] [Commented] (YARN-10359) Log container report only if list is not empty

[ https://issues.apache.org/jira/browse/YARN-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167264#comment-17167264 ] Bilwa S T commented on YARN-10359: -- cc [~prabhujoseph] > Log container report only if list is not empty

[jira] [Assigned] (YARN-10363) TestRMAdminCLI.testHelp is failing in branch-2.10

[ https://issues.apache.org/jira/browse/YARN-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10363: Assignee: Bilwa S T > TestRMAdminCLI.testHelp is failing in branch-2.10 >

[jira] [Updated] (YARN-10363) TestRMAdminCLI.testHelp is failing in branch-2.10

[ https://issues.apache.org/jira/browse/YARN-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10363: - Attachment: YARN-10363-branch-2.10.patch > TestRMAdminCLI.testHelp is failing in branch-2.10 >

[jira] [Assigned] (YARN-10363) TestRMAdminCLI.testHelp is failing in branch-2.10

[ https://issues.apache.org/jira/browse/YARN-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10363: Assignee: (was: Bilwa S T) > TestRMAdminCLI.testHelp is failing in branch-2.10 >

[jira] [Commented] (YARN-10369) Make NMTokenSecretManagerInRM sending NMToken for nodeId DEBUG

[ https://issues.apache.org/jira/browse/YARN-10369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166170#comment-17166170 ] Bilwa S T commented on YARN-10369: -- Thanks [~Jim_Brennan] for patch. one minor nit - there is no need

[jira] [Created] (YARN-10359) Log container report only if list is not empty

Bilwa S T created YARN-10359: Summary: Log container report only if list is not empty Key: YARN-10359 URL: https://issues.apache.org/jira/browse/YARN-10359 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-10359) Log container report only if list is not empty

[ https://issues.apache.org/jira/browse/YARN-10359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10359: - Attachment: YARN-10359.001.patch > Log container report only if list is not empty >

[jira] [Commented] (YARN-10320) Replace FSDataInputStream#read with readFully in Log Aggregation

[ https://issues.apache.org/jira/browse/YARN-10320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163817#comment-17163817 ] Bilwa S T commented on YARN-10320: -- Thanks for patch [~tanu.ajmera] I think you need to replace read

[jira] [Assigned] (YARN-10363) TestRMAdminCLI.testHelp is failing in branch-2.10

[ https://issues.apache.org/jira/browse/YARN-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10363: Assignee: Bilwa S T > TestRMAdminCLI.testHelp is failing in branch-2.10 >

[jira] [Commented] (YARN-10363) TestRMAdminCLI.testHelp is failing in branch-2.10

[ https://issues.apache.org/jira/browse/YARN-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17162947#comment-17162947 ] Bilwa S T commented on YARN-10363: -- Hi [~Jim_Brennan] I think we can backport YARN-9985 to branch-2.10. 

[jira] [Issue Comment Deleted] (YARN-10363) TestRMAdminCLI.testHelp is failing in branch-2.10

[ https://issues.apache.org/jira/browse/YARN-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10363: - Comment: was deleted (was: Hi [~Jim_Brennan] I think we can backport YARN-9985 to branch-2.10. ) >

[jira] [Assigned] (YARN-10361) Make custom DAO classes configurable into RMWebApp#JAXBContextResolver

[ https://issues.apache.org/jira/browse/YARN-10361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10361: Assignee: Bilwa S T (was: Prabhu Joseph) > Make custom DAO classes configurable into

<    3   4   5   6   7   8   9   10   >