[
https://issues.apache.org/jira/browse/YARN-11646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805176#comment-17805176
]
ASF GitHub Bot commented on YARN-11646:
---------------------------------------
tomicooler opened a new pull request, #6433:
URL: https://github.com/apache/hadoop/pull/6433
Change-Id: Id00a5382d982dcf33ec8a3769fc33419b660968b
<!--
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
There is no reason to ignore the configured capacity if the memory is 0 in
the configuration.
It makes it impossible to configure a zero absolute resource capacity.
Example:
```
root.default.capacity=[memory=0, vcores=0]
root.default.maximum-capacity=[memory=2048, vcores=2]
```
### How was this patch tested?
Ran the unit tests.
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'YARN-11646. 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?
> QueueCapacityConfigParser shouldn't ignore capacity config with 0 memory
> ------------------------------------------------------------------------
>
> Key: YARN-11646
> URL: https://issues.apache.org/jira/browse/YARN-11646
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 3.4.0
> Reporter: Tamas Domok
> Assignee: Tamas Domok
> Priority: Major
>
> There is no reason to ignore the configured capacity if the memory is 0 in
> the configuration.
> It makes it impossible to configure a zero absolute resource capacity.
> Example:
> {noformat}
> root.default.capacity=[memory=0, vcores=0]
> root.default.maximum-capacity=[memory=2048, vcores=2]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
