[
https://issues.apache.org/jira/browse/FLINK-17546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17546:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Consider setting the number of TM CPU cores to the actual number of cores
> -------------------------------------------------------------------------
>
> Key: FLINK-17546
> URL: https://issues.apache.org/jira/browse/FLINK-17546
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Andrey Zagrebin
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> So far we do not use CPU cores resource in TaskExecutorResourceSpec. It was a
> preparation for dynamic slot/resource allocation (FLINK-14187). It is not
> fully clear how Flink or users would define the number of cores. We could
> consider setting the number of TM CPU cores to the actual number of cores by
> default, e.g. got somehow from OS in standalone or container configuration.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
