[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=17108380#comment-17108380 ] Bilwa S T commented on YARN-10181: -- Hi [~prabhujoseph] Looks like there is already Jira for this 

[jira] [Commented] (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:comment-tabpanel=17108043#comment-17108043 ] Bilwa S T commented on YARN-10266: -- Hi [~adam.antal]  Thanks for raising this issue. This makes sense

[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=17107552#comment-17107552 ] Bilwa S T commented on YARN-9460: - Hi [~snemeth] can you please review this? > QueueACLsManager and

[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: Bilwa S T > Setting debug delay to a too high number will cause NM fail to start >

[jira] [Comment Edited] (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=17107317#comment-17107317 ] Bilwa S T edited comment on YARN-6526 at 5/14/20, 2:06 PM: --- Hi [~brahmareddy] 

[jira] [Comment Edited] (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=17107317#comment-17107317 ] Bilwa S T edited comment on YARN-6526 at 5/14/20, 1:58 PM: --- Hi [~brahmareddy] 

[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=17107317#comment-17107317 ] Bilwa S T commented on YARN-6526: - Hi [~brahmareddy]  this is metrics is to check how many connections

[jira] [Commented] (YARN-9849) Leaf queues not inheriting parent queue status after adding status as “RUNNING” and thereafter, commenting the same in capacity-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106901#comment-17106901 ] Bilwa S T commented on YARN-9849: - cc [~inigoiri] > Leaf queues not inheriting parent queue status after

[jira] [Resolved] (YARN-8552) [DS] Container report fails for distributed containers

[ https://issues.apache.org/jira/browse/YARN-8552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T resolved YARN-8552. - Resolution: Cannot Reproduce > [DS] Container report fails for distributed containers >

[jira] [Resolved] (YARN-10128) [FederationSecurity] YARN RMAdmin commands fail when Authorization is enabled on router

[ https://issues.apache.org/jira/browse/YARN-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T resolved YARN-10128. -- Resolution: Duplicate > [FederationSecurity] YARN RMAdmin commands fail when Authorization is enabled

[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.001.patch > [Federation] Client should be able to submit application to RM

[jira] [Commented] (YARN-10209) DistributedShell should initialize TimelineClient conditionally

[ https://issues.apache.org/jira/browse/YARN-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106295#comment-17106295 ] Bilwa S T commented on YARN-10209: -- [~bteke] Okay > DistributedShell should initialize TimelineClient

[jira] [Commented] (YARN-10209) DistributedShell should initialize TimelineClient conditionally

[ https://issues.apache.org/jira/browse/YARN-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106291#comment-17106291 ] Bilwa S T commented on YARN-10209: -- [~bteke] Looks like this branch is not rebased. > DistributedShell

[jira] [Commented] (YARN-9606) Set sslfactory for AuthenticatedURL() while creating LogsCLI#webServiceClient

[ https://issues.apache.org/jira/browse/YARN-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106280#comment-17106280 ] Bilwa S T commented on YARN-9606: - [~prabhujoseph] ok thanks > Set sslfactory for AuthenticatedURL()

[jira] [Updated] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-8942: Fix Version/s: 3.4.0 > PriorityBasedRouterPolicy throws exception if all sub-cluster weights have >

[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=17105538#comment-17105538 ] Bilwa S T commented on YARN-6526: - Thanks [~elgoiri] for reviewing. I updated patch > Refactoring

[jira] [Commented] (YARN-9301) Too many InvalidStateTransitionException with SLS

[ https://issues.apache.org/jira/browse/YARN-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17105537#comment-17105537 ] Bilwa S T commented on YARN-9301: - Thanks [~elgoiri] for committing.  I will take care from next time. >

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Attachment: YARN-6526.007.patch > Refactoring SQLFederationStateStore by avoiding to recreate a connection

[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=17105439#comment-17105439 ] Bilwa S T commented on YARN-6539: - Thanks [~yifan.stan] for patch. * Can you please add a testcase for

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Attachment: YARN-6526.006.patch > Refactoring SQLFederationStateStore by avoiding to recreate a connection

[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=17103690#comment-17103690 ] Bilwa S T commented on YARN-6526: - Thanks [~elgoiri] for reviewing. I have updated patch * Before i was

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Attachment: YARN-6526.005.patch > Refactoring SQLFederationStateStore by avoiding to recreate a connection

[jira] [Commented] (YARN-9301) Too many InvalidStateTransitionException with SLS

[ https://issues.apache.org/jira/browse/YARN-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103654#comment-17103654 ] Bilwa S T commented on YARN-9301: - Thanks [~elgoiri] for reviewing this > Too many

[jira] [Commented] (YARN-10260) Allow transitioning queue from DRAINING to RUNNING state

[ https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17103159#comment-17103159 ] Bilwa S T commented on YARN-10260: -- Hi [~jhung] Thanks for raising this issue. I have uploaded patch.

[jira] [Updated] (YARN-10260) Allow transitioning queue from DRAINING to RUNNING state

[ https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10260: - Attachment: YARN-10260.001.patch > Allow transitioning queue from DRAINING to RUNNING state >

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Attachment: YARN-6526.004.patch > Refactoring SQLFederationStateStore by avoiding to recreate a connection

[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=17102846#comment-17102846 ] Bilwa S T commented on YARN-6526: - Hi [~elgoiri] I have attached patch by adding metrics and related

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Attachment: YARN-6526.003.patch > Refactoring SQLFederationStateStore by avoiding to recreate a connection

[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.002.patch > QueueACLsManager and ReservationsACLManager should not use instanceof

[jira] [Comment Edited] (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=17101920#comment-17101920 ] Bilwa S T edited comment on YARN-9460 at 5/7/20, 6:00 PM: -- Hi [~snemeth] Thanks

[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=17101920#comment-17101920 ] Bilwa S T commented on YARN-9460: - Hi [~snemeth] Thanks for clarification. I didn't add SchedulerType

[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.001.patch > QueueACLsManager and ReservationsACLManager should not use instanceof

[jira] [Issue Comment Deleted] (YARN-10260) Allow transitioning queue from DRAINING to RUNNING state

[ https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10260: - Comment: was deleted (was: [~jhung] Thanks for raising this issue  Instead of throwing exception when

[jira] [Comment Edited] (YARN-10260) Allow transitioning queue from DRAINING to RUNNING state

[ https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101746#comment-17101746 ] Bilwa S T edited comment on YARN-10260 at 5/7/20, 2:59 PM: --- [~jhung] Thanks for

[jira] [Commented] (YARN-10260) Allow transitioning queue from DRAINING to RUNNING state

[ https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101746#comment-17101746 ] Bilwa S T commented on YARN-10260: -- Hi [~jhung] Instead of throwing exception when configstate is

[jira] [Assigned] (YARN-10260) Allow transitioning queue from DRAINING to RUNNING state

[ https://issues.apache.org/jira/browse/YARN-10260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10260: Assignee: Bilwa S T > Allow transitioning queue from DRAINING to RUNNING state >

[jira] [Commented] (YARN-9301) Too many InvalidStateTransitionException with SLS

[ https://issues.apache.org/jira/browse/YARN-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101528#comment-17101528 ] Bilwa S T commented on YARN-9301: - cc [~inigoiri] > Too many InvalidStateTransitionException with SLS >

[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=17101520#comment-17101520 ] Bilwa S T commented on YARN-10229: -- Hi [~bibinchundatt] can we add same check ie homeapplications entry

[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=17101523#comment-17101523 ] Bilwa S T commented on YARN-10229: -- cc [~brahmareddy] > [Federation] Client should be able to submit

[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=17101508#comment-17101508 ] Bilwa S T commented on YARN-6526: - Hi [~elgoiri] We can add it in FederationStateStoreClientMetrics . But

[jira] [Commented] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101376#comment-17101376 ] Bilwa S T commented on YARN-9017: - Thanks [~elgoiri] for reviewing > PlacementRule order is not

[jira] [Updated] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9017: Affects Version/s: 3.4.0 > PlacementRule order is not maintained in CS >

[jira] [Issue Comment Deleted] (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: - Comment: was deleted (was: Hi [~bibinchundatt] I feel handling it in

[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=17099773#comment-17099773 ] Bilwa S T commented on YARN-9460: - Hi [~snemeth] Thanks for the clarification. This is clear from Jira

[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=17099662#comment-17099662 ] Bilwa S T commented on YARN-6526: - cc [~inigoiri] [~brahmareddy] > Refactoring SQLFederationStateStore by

[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=17098682#comment-17098682 ] Bilwa S T commented on YARN-10229: -- Hi [~bibinchundatt] I feel handling it in

[jira] [Assigned] (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 reassigned YARN-10229: Assignee: Bilwa S T > [Federation] Client should be able to submit application to RM directly

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Fix Version/s: 3.4.0 > Refactoring SQLFederationStateStore by avoiding to recreate a connection at > every

[jira] [Commented] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17097888#comment-17097888 ] Bilwa S T commented on YARN-9017: - [~elgoiri] can you please review this when you have free time? >

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Attachment: YARN-6526.002.patch > Refactoring SQLFederationStateStore by avoiding to recreate a connection

[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=17097600#comment-17097600 ] Bilwa S T commented on YARN-6526: - Thanks [~giovanni.fumarola] for clarification. I have attached patch.

[jira] [Updated] (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:all-tabpanel ] Bilwa S T updated YARN-6526: Attachment: YARN-6526.001.patch > Refactoring SQLFederationStateStore by avoiding to recreate a connection

[jira] [Updated] (YARN-10253) Remove unused resourcemanager test dependeny in hadoop-yarn-client

[ https://issues.apache.org/jira/browse/YARN-10253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10253: - Summary: Remove unused resourcemanager test dependeny in hadoop-yarn-client (was: Duplicate

[jira] [Assigned] (YARN-10243) Rack-only localization constraint for MR AM is broken for CapacityScheduler

[ https://issues.apache.org/jira/browse/YARN-10243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10243: Assignee: Bilwa S T > Rack-only localization constraint for MR AM is broken for CapacityScheduler

[jira] [Updated] (YARN-10253) Duplicate resourcemanager test dependeny in hadoop-yarn-client

[ https://issues.apache.org/jira/browse/YARN-10253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-10253: - Attachment: YARN-10253.001.patch > Duplicate resourcemanager test dependeny in hadoop-yarn-client >

[jira] [Updated] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9017: Attachment: YARN-9017.003.patch > PlacementRule order is not maintained in CS >

[jira] [Assigned] (YARN-10253) Duplicate resourcemanager test dependeny in hadoop-yarn-client

[ https://issues.apache.org/jira/browse/YARN-10253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-10253: Assignee: Bilwa S T > Duplicate resourcemanager test dependeny in hadoop-yarn-client >

[jira] [Created] (YARN-10253) Duplicate resourcemanager test dependeny in hadoop-yarn-client

Bilwa S T created YARN-10253: Summary: Duplicate resourcemanager test dependeny in hadoop-yarn-client Key: YARN-10253 URL: https://issues.apache.org/jira/browse/YARN-10253 Project: Hadoop YARN

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

[ https://issues.apache.org/jira/browse/YARN-6526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096570#comment-17096570 ] Bilwa S T commented on YARN-6526: - cc [~inigoiri] > Refactoring SQLFederationStateStore by avoiding to

[jira] [Commented] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096557#comment-17096557 ] Bilwa S T commented on YARN-9017: - Thanks [~elgoiri] for reviewing. I have updated testcase . Please take

[jira] [Updated] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9017: Attachment: YARN-9017.002.patch > PlacementRule order is not maintained in CS >

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Fix Version/s: 3.4.0 > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests >

[jira] [Commented] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095454#comment-17095454 ] Bilwa S T commented on YARN-6973: - Build is ok now [~elgoiri] > Adding RM Cluster Id in ApplicationReport

[jira] [Commented] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095280#comment-17095280 ] Bilwa S T commented on YARN-9017: - cc [~bibinchundatt] [~inigoiri] > PlacementRule order is not

[jira] [Commented] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095278#comment-17095278 ] Bilwa S T commented on YARN-8942: - Thanks [~elgoiri] for reviewing. I have handled comments given .

[jira] [Updated] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-8942: Attachment: YARN-8942.002.patch > PriorityBasedRouterPolicy throws exception if all sub-cluster weights

[jira] [Updated] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6973: Summary: Adding RM Cluster Id in ApplicationReport (was: Adding RM Cluster Id in ApplicationReport) >

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: YARN-6553.004.patch > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: (was: YARN-6553.004.patch) > Replace MockResourceManagerFacade with MockRM for

[jira] [Updated] (YARN-9017) PlacementRule order is not maintained in CS

[ https://issues.apache.org/jira/browse/YARN-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9017: Attachment: YARN-9017.001.patch > PlacementRule order is not maintained in CS >

[jira] [Commented] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094808#comment-17094808 ] Bilwa S T commented on YARN-8942: - cc [~elgoiri]  > PriorityBasedRouterPolicy throws exception if all

[jira] [Commented] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094806#comment-17094806 ] Bilwa S T commented on YARN-6553: - Hi [~elgoiri] I have fixed it in latest patch. Please check > Replace

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: YARN-6553.004.patch > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[jira] [Issue Comment Deleted] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-8942: Comment: was deleted (was: cc [~brahma] [~giovanni.fumarola]) > PriorityBasedRouterPolicy throws exception

[jira] [Commented] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094795#comment-17094795 ] Bilwa S T commented on YARN-6973: - Thanks [~elgoiri] for reviewing. I have fixed checkstyle issues and

[jira] [Updated] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6973: Attachment: YARN-6973.003.patch > Adding RM Cluster Id in ApplicationReport >

[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=17094724#comment-17094724 ] Bilwa S T commented on YARN-9460: - Hi [~snemeth]  I had one small doubt. So we make these as configurable

[jira] [Commented] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094584#comment-17094584 ] Bilwa S T commented on YARN-8942: - cc [~brahma] [~giovanni.fumarola] > PriorityBasedRouterPolicy throws

[jira] [Commented] (YARN-9606) Set sslfactory for AuthenticatedURL() while creating LogsCLI#webServiceClient

[ https://issues.apache.org/jira/browse/YARN-9606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094359#comment-17094359 ] Bilwa S T commented on YARN-9606: - [~prabhujoseph] can you please review this when you get time? > Set

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: YARN-6553.003.patch > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: (was: YARN-6553.003.patch) > Replace MockResourceManagerFacade with MockRM for

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: YARN-6553.003.patch > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[jira] [Commented] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094161#comment-17094161 ] Bilwa S T commented on YARN-6553: - Thanks [~elgoiri] for reviewing I have updated patch handling both

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: YARN-6553.002.patch > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[jira] [Updated] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-8942: Attachment: YARN-8942.001.patch > PriorityBasedRouterPolicy throws exception if all sub-cluster weights

[jira] [Commented] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093853#comment-17093853 ] Bilwa S T commented on YARN-6553: - cc [~inigoiri] > Replace MockResourceManagerFacade with MockRM for

[jira] [Assigned] (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 reassigned YARN-9460: --- Assignee: Bilwa S T > QueueACLsManager and ReservationsACLManager should not use instanceof checks >

[jira] [Commented] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17092518#comment-17092518 ] Bilwa S T commented on YARN-6553: - Hi [~giovanni.fumarola]/[~brahmareddy] can you please help me review

[jira] [Updated] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6553: Attachment: YARN-6553.001.patch > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[jira] [Assigned] (YARN-8942) PriorityBasedRouterPolicy throws exception if all sub-cluster weights have negative value

[ https://issues.apache.org/jira/browse/YARN-8942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-8942: --- Assignee: Bilwa S T > PriorityBasedRouterPolicy throws exception if all sub-cluster weights have >

[jira] [Commented] (YARN-10220) RM HA times out intermittently

[ https://issues.apache.org/jira/browse/YARN-10220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088995#comment-17088995 ] Bilwa S T commented on YARN-10220: -- Hi [~ahussein]  its always passing in my machine. Do you have logs

[jira] [Commented] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087818#comment-17087818 ] Bilwa S T commented on YARN-6973: - Thanks [~elgoiri] for reviewing. 1. There is no other document other

[jira] [Updated] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6973: Fix Version/s: 3.4.0 > Adding RM Cluster Id in ApplicationReport >

[jira] [Assigned] (YARN-6553) Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests

[ https://issues.apache.org/jira/browse/YARN-6553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T reassigned YARN-6553: --- Assignee: Bilwa S T > Replace MockResourceManagerFacade with MockRM for AMRMProxy/Router tests >

[jira] [Updated] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6973: Attachment: YARN-6973.002.patch > Adding RM Cluster Id in ApplicationReport >

[jira] [Commented] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17086908#comment-17086908 ] Bilwa S T commented on YARN-6973: - Hi [~giovanni.fumarola] Could you please help to review? > Adding RM

[jira] [Updated] (YARN-6973) Adding RM Cluster Id in ApplicationReport

[ https://issues.apache.org/jira/browse/YARN-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-6973: Attachment: YARN-6973.001.patch > Adding RM Cluster Id in ApplicationReport >

[jira] [Commented] (YARN-9849) Leaf queues not inheriting parent queue status after adding status as “RUNNING” and thereafter, commenting the same in capacity-scheduler.xml

[ https://issues.apache.org/jira/browse/YARN-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085991#comment-17085991 ] Bilwa S T commented on YARN-9849: - Hi [~jhung] can you please review this? > Leaf queues not inheriting

[jira] [Updated] (YARN-9954) Configurable max application tags and max tag length

[ https://issues.apache.org/jira/browse/YARN-9954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9954: Attachment: YARN-9954-branch-3.3.v3.patch > Configurable max application tags and max tag length >

[jira] [Updated] (YARN-9954) Configurable max application tags and max tag length

[ https://issues.apache.org/jira/browse/YARN-9954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bilwa S T updated YARN-9954: Attachment: YARN-9954.003.patch > Configurable max application tags and max tag length >

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