[jira] [Updated] (YARN-10350) TestUserGroupMappingPlacementRule fails

[ https://issues.apache.org/jira/browse/YARN-10350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10350: - Attachment: YARN-10350.002.patch > TestUserGroupMappingPlacementRule fails >

[jira] [Updated] (YARN-10350) TestUserGroupMappingPlacementRule fails

[ https://issues.apache.org/jira/browse/YARN-10350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10350: - Attachment: YARN-10350.001.patch > TestUserGroupMappingPlacementRule fails >

[jira] [Assigned] (YARN-10350) TestUserGroupMappingPlacementRule fails

[ https://issues.apache.org/jira/browse/YARN-10350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10350: Assignee: Bilwa S T > TestUserGroupMappingPlacementRule fails >

[jira] [Commented] (YARN-10291) Yarn service commands doesn't work when https is enabled in RM

[ https://issues.apache.org/jira/browse/YARN-10291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155344#comment-17155344 ] Bilwa S T commented on YARN-10291: -- Hi [~eyang] It works with Java cacerts option. Thank you. We can

[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: - Description: If there 10 workers running and if containers get killed , after a while we see that there

[jira] [Updated] (YARN-10268) TestFederationInterceptor#testRecoverWithoutAMRMProxyHA fails intermittently.

[ https://issues.apache.org/jira/browse/YARN-10268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10268: - Attachment: YARN-10268.001.patch > TestFederationInterceptor#testRecoverWithoutAMRMProxyHA fails

[jira] [Assigned] (YARN-9371) Better logging for initialization of cgroups in CGroupsHandlerImpl

[ https://issues.apache.org/jira/browse/YARN-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-9371: --- Assignee: (was: Bilwa S T) > Better logging for initialization of cgroups in CGroupsHandlerImpl

[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=17154620#comment-17154620 ] Bilwa S T commented on YARN-10229: -- [~elgoiri] Please check this when you have free time. Thanks >

[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=17154282#comment-17154282 ] Bilwa S T commented on YARN-10341: -- Thanks [~brahmareddy] > Yarn Service Container Completed event

[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=17154242#comment-17154242 ] Bilwa S T commented on YARN-10341: -- Fixed Checkstyle issues > Yarn Service Container Completed event

[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] [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=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-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152719#comment-17152719 ] Bilwa S T commented on YARN-10337: -- Thanks [~prabhujoseph] > TestRMHATimelineCollectors fails on hadoop

[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=17152718#comment-17152718 ] Bilwa S T commented on YARN-8047: - Thanks [~prabhujoseph] for reviewing. I have handled all comments . Is

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

[ https://issues.apache.org/jira/browse/YARN-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-8047: Attachment: YARN-8047.006.patch > RMWebApp make external class pluggable >

[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=17152271#comment-17152271 ] Bilwa S T commented on YARN-10341: -- Okay i will take care from next time . Thanks [~eyang] > Yarn

[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.001.patch > Yarn Service Container Completed event doesn't get processed >

[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: (was: YARN-10341.001.patch) > Yarn Service Container Completed event doesn't get

[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=17152182#comment-17152182 ] Bilwa S T commented on YARN-10341: -- cc [~eyang] > Yarn Service Container Completed event doesn't get

[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.001.patch > Yarn Service Container Completed event doesn't get processed >

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

Bilwa S T created YARN-10341: Summary: Yarn Service Container Completed event doesn't get processed Key: YARN-10341 URL: https://issues.apache.org/jira/browse/YARN-10341 Project: Hadoop YARN

[jira] [Commented] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151587#comment-17151587 ] Bilwa S T commented on YARN-10337: -- cc [~prabhujoseph] > TestRMHATimelineCollectors fails on hadoop

[jira] [Commented] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151585#comment-17151585 ] Bilwa S T commented on YARN-10337: -- Thanks [~ahussein] for reporting this. > TestRMHATimelineCollectors

[jira] [Updated] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10337: - Attachment: (was: YARN-10337.001.patch) > TestRMHATimelineCollectors fails on hadoop trunk >

[jira] [Updated] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10337: - Attachment: YARN-10337.001.patch > TestRMHATimelineCollectors fails on hadoop trunk >

[jira] [Updated] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10337: - Attachment: YARN-10337.001.patch > TestRMHATimelineCollectors fails on hadoop trunk >

[jira] [Assigned] (YARN-10337) TestRMHATimelineCollectors fails on hadoop trunk

[ https://issues.apache.org/jira/browse/YARN-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10337: Assignee: Bilwa S T > TestRMHATimelineCollectors fails on hadoop trunk >

[jira] [Comment Edited] (YARN-10336) RM page should throw exception when command injected in RM REST API to get applications

[ https://issues.apache.org/jira/browse/YARN-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150315#comment-17150315 ] Bilwa S T edited comment on YARN-10336 at 7/2/20, 7:13 PM: --- cc [~brahmareddy]

[jira] [Comment Edited] (YARN-10336) RM page should throw exception when command injected in RM REST API to get applications

[ https://issues.apache.org/jira/browse/YARN-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150303#comment-17150303 ] Bilwa S T edited comment on YARN-10336 at 7/2/20, 4:37 PM: --- This should be

[jira] [Commented] (YARN-9459) ConfiguredYarnAuthorizer should not now any details about queues

[ https://issues.apache.org/jira/browse/YARN-9459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150388#comment-17150388 ] Bilwa S T commented on YARN-9459: - Hi [~snemeth] ConfiguredYarnAuthorizer#checkPermission is not just

[jira] [Comment Edited] (YARN-10336) RM page should throw exception when command injected in RM REST API to get applications

[ https://issues.apache.org/jira/browse/YARN-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150315#comment-17150315 ] Bilwa S T edited comment on YARN-10336 at 7/2/20, 2:01 PM: --- cc [~brahmareddy]

[jira] [Commented] (YARN-10336) RM page should throw exception when command injected in RM REST API to get applications

[ https://issues.apache.org/jira/browse/YARN-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150315#comment-17150315 ] Bilwa S T commented on YARN-10336: -- cc [~brahmareddy] > RM page should throw exception when command

[jira] [Commented] (YARN-10336) RM page should throw exception when command injected in RM REST API to get applications

[ https://issues.apache.org/jira/browse/YARN-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17150303#comment-17150303 ] Bilwa S T commented on YARN-10336: -- This should be handled same way as how NodesPage is handled if

[jira] [Assigned] (YARN-10336) RM page should throw exception when command injected in RM REST API to get applications

[ https://issues.apache.org/jira/browse/YARN-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10336: Assignee: Bilwa S T > RM page should throw exception when command injected in RM REST API to get

[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=17148835#comment-17148835 ] Bilwa S T commented on YARN-10311: -- Hi [~eyang] Is there any test class where ServiceClient is tested

[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=17148834#comment-17148834 ] Bilwa S T commented on YARN-10310: -- [~eyang] This issue can be closed then. Thanks > YARN Service -

[jira] [Assigned] (YARN-10230) TestSchedConfCLI#testFormatSchedulerConf fails

[ https://issues.apache.org/jira/browse/YARN-10230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10230: Assignee: (was: Bilwa S T) > TestSchedConfCLI#testFormatSchedulerConf fails >

[jira] [Assigned] (YARN-10005) Code improvements in MutableCSConfigurationProvider

[ https://issues.apache.org/jira/browse/YARN-10005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10005: Assignee: (was: Bilwa S T) > Code improvements in MutableCSConfigurationProvider >

[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] [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] [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=17146473#comment-17146473 ] Bilwa S T commented on YARN-10229: -- Hi [~youchen] I have attached a patch. Please take a look at it >

[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] [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] [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] [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] [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] [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] [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] [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] [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] [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] [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=17140747#comment-17140747 ] Bilwa S T commented on YARN-10229: -- Hi [~elgoiri] Tested on CentOS Linux release 7.6.1810 Below are

[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=17138637#comment-17138637 ] Bilwa S T edited comment on YARN-10310 at 6/17/20, 4:50 PM: Hi [~eyang] 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=17138637#comment-17138637 ] Bilwa S T commented on YARN-10310: -- Hi [~eyang] I could see that ServiceClient#submitapp adds

[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=17138630#comment-17138630 ] Bilwa S T commented on YARN-10308: -- Thanks [~eyang] > Update javadoc and variable names for keytab in

[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=17138170#comment-17138170 ] Bilwa S T commented on YARN-10311: -- Hi [~eyang] I had set "yarn.nodemanager.remote-app-log-dir" to

[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-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-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] [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] [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] [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=17136352#comment-17136352 ] Bilwa S T edited comment on YARN-10310 at 6/16/20, 6:37 AM: [~eyang] Actually

[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=17136352#comment-17136352 ] Bilwa S T commented on YARN-10310: -- [~eyang] Actually the verifyNoLiveAppInRM check happens before it

[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=17136269#comment-17136269 ] Bilwa S T commented on YARN-10310: -- Hi [~eyang] Maybe you can delete file from hdfs and launch an app

[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] [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-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-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] [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] [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] [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] [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] [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-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-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-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-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-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] [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

<    1   2   3   4   5   6   7   8   9   10   >