[
https://issues.apache.org/jira/browse/FLINK-20503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333650#comment-17333650
]
Flink Jira Bot commented on FLINK-20503:
----------------------------------------
This issue was marked "stale-assigned" and has not received an update in 7
days. It is now automatically unassigned. If you are still working on it, you
can assign it to yourself again. Please also give an update about the status of
the work.
> 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
> Assignee: Xintong Song
> Priority: Major
> Labels: stale-assigned
>
> 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.3.4#803005)
