You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Zhu Zhu (Jira)" <ji...@apache.org> on 2022/05/10 09:53:00 UTC

[jira] [Commented] (FLINK-17295) Refactor the ExecutionAttemptID to consist of ExecutionVertexID and attemptNumber

    [ https://issues.apache.org/jira/browse/FLINK-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534269#comment-17534269 ] 

Zhu Zhu commented on FLINK-17295:
---------------------------------

I'd like to revive this ticket, because I think a meaningful ExecutionAttemptID can be really helpful.
For the safety purpose, I agree that it's better to keep the random AbstractID and just add an {{executionVertexID}} field.
[~guoyangze] do you want to work on it? I can also take it if you are busy with other things.

> Refactor the ExecutionAttemptID to consist of ExecutionVertexID and attemptNumber
> ---------------------------------------------------------------------------------
>
>                 Key: FLINK-17295
>                 URL: https://issues.apache.org/jira/browse/FLINK-17295
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Yangze Guo
>            Priority: Major
>              Labels: pull-request-available
>
> Make the ExecutionAttemptID being composed of (ExecutionVertexID, attemptNumber).



--
This message was sent by Atlassian Jira
(v8.20.7#820007)