[
https://issues.apache.org/jira/browse/FLINK-8835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mingleizhang updated FLINK-8835:
--------------------------------
Description:
Many new config keys in the TaskManager don't follow the proper naming scheme.
We need to clear those up before the release. I would also suggest to keep the
key names short, because that makes it easier for users.
When doing this cleanup pass over the config keys, I would suggest to also make
some of the existing keys more hierarchical harmonize them with the common
scheme in Flink.
h1. New Keys
* {{taskmanager.network.credit-based-flow-control.enabled}} to
{{taskmanager.network.credit-model}}.
h1. Existing Keys
* {{taskmanager.debug.memory.startLogThread}} =>
{{taskmanager.debug.memory.log}}
* {{taskmanager.debug.memory.logIntervalMs}} =>
{{taskmanager.debug.memory.log-interval}}
* {{taskmanager.initial-registration-pause}} =>
{{taskmanager.registration.initial-backoff}}
* {{taskmanager.max-registration-pause}} =>
{{taskmanager.registration.max-backoff}}
* {{taskmanager.refused-registration-pause}}
{{taskmanager.registration.refused-backoff}}
* {{taskmanager.maxRegistrationDuration}} ==> *
{{taskmanager.registration.timeout}}
was:
Many new config keys in the TaskManager don't follow the proper naming scheme.
We need to clear those up before the release. I would also suggest to keep the
key names short, because that makes it easier for users.
When doing this cleanup pass over the config keys, I would suggest to also make
some of the existing keys more hierarchical harmonize them with the common
scheme in Flink.
h1. New Keys
* {{taskmanager.network.credit-based-flow-control.enabled}} to
{{taskmanager.network.credit-model}}.
* {{taskmanager.exactly-once.blocking.data.enabled}} to
{{task.checkpoint.alignment.blocking}} (we already have
{{task.checkpoint.alignment.max-size}})
h1. Existing Keys
* {{taskmanager.debug.memory.startLogThread}} =>
{{taskmanager.debug.memory.log}}
* {{taskmanager.debug.memory.logIntervalMs}} =>
{{taskmanager.debug.memory.log-interval}}
* {{taskmanager.initial-registration-pause}} =>
{{taskmanager.registration.initial-backoff}}
* {{taskmanager.max-registration-pause}} =>
{{taskmanager.registration.max-backoff}}
* {{taskmanager.refused-registration-pause}}
{{taskmanager.registration.refused-backoff}}
* {{taskmanager.maxRegistrationDuration}} ==> *
{{taskmanager.registration.timeout}}
> Fix TaskManager config keys
> ---------------------------
>
> Key: FLINK-8835
> URL: https://issues.apache.org/jira/browse/FLINK-8835
> Project: Flink
> Issue Type: Bug
> Components: TaskManager
> Reporter: Stephan Ewen
> Assignee: mingleizhang
> Priority: Blocker
> Labels: easy-fix
> Fix For: 1.5.0
>
>
> Many new config keys in the TaskManager don't follow the proper naming
> scheme. We need to clear those up before the release. I would also suggest to
> keep the key names short, because that makes it easier for users.
> When doing this cleanup pass over the config keys, I would suggest to also
> make some of the existing keys more hierarchical harmonize them with the
> common scheme in Flink.
> h1. New Keys
> * {{taskmanager.network.credit-based-flow-control.enabled}} to
> {{taskmanager.network.credit-model}}.
> h1. Existing Keys
> * {{taskmanager.debug.memory.startLogThread}} =>
> {{taskmanager.debug.memory.log}}
> * {{taskmanager.debug.memory.logIntervalMs}} =>
> {{taskmanager.debug.memory.log-interval}}
> * {{taskmanager.initial-registration-pause}} =>
> {{taskmanager.registration.initial-backoff}}
> * {{taskmanager.max-registration-pause}} =>
> {{taskmanager.registration.max-backoff}}
> * {{taskmanager.refused-registration-pause}}
> {{taskmanager.registration.refused-backoff}}
> * {{taskmanager.maxRegistrationDuration}} ==> *
> {{taskmanager.registration.timeout}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
