You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2020/08/19 02:01:00 UTC
[jira] [Closed] (FLINK-15679) Improve Flink's ID system
[ https://issues.apache.org/jira/browse/FLINK-15679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xintong Song closed FLINK-15679.
--------------------------------
Resolution: Done
> Improve Flink's ID system
> -------------------------
>
> Key: FLINK-15679
> URL: https://issues.apache.org/jira/browse/FLINK-15679
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Yangze Guo
> Priority: Major
> Labels: usability
> Fix For: 1.12.0
>
>
> Flink uses a lot of IDs which are hard to decipher for the user:
> - The string literal of most Flink’s IDs are meaningless hashcode. It does not help the user to understand what happened.
> - The LOGs do not contain the lineage info of those IDs. Currently, it’s impossible to track the end to end lifecycle of an Execution or a Task.
> - Some redundancy exists in Flink’s ID system, we need to sort out the current ID system before introducing more complexity.
> To help the user to understand what Flink is doing, we target to add more meaning to Flink’s IDs and LOGs while cleaning up the redundancy and refactoring the ID system.
> This is an umbrella ticket to track all the relevant issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)