[
https://issues.apache.org/jira/browse/FLINK-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann resolved FLINK-15145.
-----------------------------------
Resolution: Done
Done via
master:
6ec4b5684d60007fe4570107aaa61c808e4fd5f9
e3f2cadef1c1c19582927c1bf24633c1c7056e9b
d5272ec65d6f5224a67ca0f35be2e512ab061f08
1.10.0:
64cbeb78cf3c012bea21da2aa0b7093dbf354d44
de43479d6e9452ede107387872e744d02de492ea
6dfa0a750a4a37cdb4b94a8cec0f4e4ad8de15f3
> Tune default values for FLIP-49 TM memory configurations with real production
> jobs.
> -----------------------------------------------------------------------------------
>
> Key: FLINK-15145
> URL: https://issues.apache.org/jira/browse/FLINK-15145
> Project: Flink
> Issue Type: Task
> Components: Runtime / Configuration
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In release 1.10, with FLIP-49, we introduced significant changes to the
> TaskExecutor memory model and it's related configuration options / logics.
> Since the model and configuration logics are changed, it is reasonable that
> we also change the default configuration values. Currently, the default
> values are set with the gut feelings and experiences from e2e tests. It would
> be good that we try and tune the configurations with some real production
> jobs, of various scales if possible, before exposing the configurations in
> the release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
