[
https://issues.apache.org/jira/browse/FLINK-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225077#comment-17225077
]
Yangze Guo edited comment on FLINK-17295 at 11/3/20, 2:38 AM:
--------------------------------------------------------------
Thanks for the pointer [~rmetzger]. From my understanding, the root cause is
that some components in Flink assume the ExecutionAttemptID to be different
across execution, jobs, and leader session. So, including a random element in
the ExecutionAttemptID is probably good enough and simple. We may add a short
random suffix. WDYT?
cc [~trohrmann]
was (Author: karmagyz):
Thanks for the pointer [~rmetzger]. From my perspective, including a random
element in the ExecutionAttemptID will be good enough and simple. We may add a
short random suffix. WDYT?
cc [~trohrmann]
> 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.12.0
>
>
> Make the ExecutionAttemptID being composed of (ExecutionVertexID,
> attemptNumber).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
