You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yangze Guo (Jira)" <ji...@apache.org> on 2020/12/22 11:46:00 UTC

[jira] [Comment Edited] (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=17253429#comment-17253429 ] 

Yangze Guo edited comment on FLINK-17295 at 12/22/20, 11:45 AM:
----------------------------------------------------------------

I compare the entire job runtime in the parallelism of 2000. After a cluster warm up, There is no difference in running time (29.4s vs 30s). Maybe this result can give us more confidence to introduce a random element.


was (Author: karmagyz):
I compare the entire job runtime in the parallelism of 2000. After a cluster warm up, There is no difference in running time (29.4s vs 30s). Maybe this result will give us more confidence to introduce a random element.

> 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
>             Fix For: 1.13.0
>
>
> Make the ExecutionAttemptID being composed of (ExecutionVertexID, attemptNumber).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)