You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matthias (Jira)" <ji...@apache.org> on 2020/12/10 09:05:00 UTC
[jira] [Commented] (FLINK-20259) Add explanation that "configured
values" for JM/TM memory sizes include automatically derived values
[ https://issues.apache.org/jira/browse/FLINK-20259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247104#comment-17247104 ]
Matthias commented on FLINK-20259:
----------------------------------
One proposal for the explanation:
{code:java}
These configuration values might differ from what the user set in the Flink configuration. Flink adjusts some of the values to make them fit to the actual setup. The values you see here are the values effectively used by Flink. {code}
[~xintongsong] What do you think about "Effective Configuration" (stealing the idea from Maven's effective POM) as a column header instead? We used it previously but were afraid that it might be confusing.
> Add explanation that "configured values" for JM/TM memory sizes include automatically derived values
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-20259
> URL: https://issues.apache.org/jira/browse/FLINK-20259
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Reporter: Xintong Song
> Assignee: Yadong Xie
> Priority: Critical
> Fix For: 1.13.0
>
>
> The column title `Configured Values` might be a bit confusing. Not all of the values are explicitly configured by users. There could be values that are automatically derived from users' configuration. I would suggest to add a bit explanation (e.g., a (i) with some hidden texts) for both JM and TM.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)