[
https://issues.apache.org/jira/browse/YARN-11815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17948636#comment-17948636
]
ASF GitHub Bot commented on YARN-11815:
---------------------------------------
nihal292 opened a new pull request, #7665:
URL: https://github.com/apache/hadoop/pull/7665
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
### How was this patch tested?
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> NodeQueueLoadMonitor scheduler running on standby RMs
> -----------------------------------------------------
>
> Key: YARN-11815
> URL: https://issues.apache.org/jira/browse/YARN-11815
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.4.1
> Reporter: Nihal Agarwal
> Priority: Minor
>
> NodeQueueLoadMonitor runs as an active service via
> OpportunisticContainerAllocatorAMService in Yarn Resource Manager.
> However, it's scheduler thread is started in the constructor itself. This
> would cause the scheduler to run on standby RM too which shouldn't be the
> case since it is an active service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
