[
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-unassigned stale-minor (was:
auto-deprioritized-major auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> 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)
