[
https://issues.apache.org/jira/browse/FLINK-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225965#comment-17225965
]
Chesnay Schepler commented on FLINK-17295:
------------------------------------------
I think that would be a bit overkill.
Here's the thing; so far we used random IDs, so from a users perspective it
doesn't matter if there still is a random ID in 1.12. Let's just replace the
JobID with a random one for the time being, and figure out a better solution
for 1.13 .
Possible options that [~rmetzger], [~trohrmann] and myself came up with are a
job-attempt counter (stored in ZK), or the leader session ID.
> 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)
