[
https://issues.apache.org/jira/browse/FLINK-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197078#comment-17197078
]
Stephan Ewen commented on FLINK-17295:
--------------------------------------
Forwarding the pointer from FLINK-19264:
The ExecutionAttemptID needs to be unique across jobs:
- We can include the JobID in the execution attempt ID to make it
Job-specific and not have collisions between jobs with same vertex names. That
is similar to how Hadoop names execution attempts.
- We could go back to making them random again, but that might defeat some of
the purpose of making logs easier to read.
> 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
> Assignee: 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)
