[
https://issues.apache.org/jira/browse/FLINK-20503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20503:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned 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.
> Internal cpu configuration option is leaked in logs
> ---------------------------------------------------
>
> Key: FLINK-20503
> URL: https://issues.apache.org/jira/browse/FLINK-20503
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Configuration
> Affects Versions: 1.11.2, 1.12.0
> Reporter: Xintong Song
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> The configuration option `taskmanager.cpu.cores` is meant for internal usages
> only and should not be advertised to users atm.
> However, the following logs could be printed when Flink runs in local
> environment, which not only leaks the option to the users, but may also
> mislead them to explicitly set it.
> {quote}"The configuration option taskmanager.cpu.cores required for local
> execution is not set, setting it to xxx".
> {quote}
> The log comes from `TaskExecutorResourceUtils#adjustForLocalExecution`.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
