[
https://issues.apache.org/jira/browse/FLINK-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622760#comment-16622760
]
Till Rohrmann commented on FLINK-10256:
---------------------------------------
At the moment the {{JobMaster}} failover is not super sophisticated and the new
leader needs to allocate new resources anyway. Therefore, it is at the moment
ok to try to release all resources belonging to the old leader. If we improve
the {{JobMaster}} failover, then we need to change this, most likely.
> Port legacy jobmanager test to FILP-6
> -------------------------------------
>
> Key: FLINK-10256
> URL: https://issues.apache.org/jira/browse/FLINK-10256
> Project: Flink
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 1.7.0
> Reporter: 陈梓立
> Assignee: 陈梓立
> Priority: Major
> Fix For: 1.7.0
>
>
> I am planning to rework JobManagerFailsITCase and JobManagerTest into
> JobMasterITCase and JobMasterHAITCase. That is, reorganize the legacy tests,
> make them neat and cover cases explicitly. The PR would follow before this
> weekend.
> While reworking, I'd like to add more jm failover test cases list below, for
> the further implement of jm failover with RECONCILING state. For "jm
> failover", I mean a real world failover(like low power or process exit),
> without calling Flink internal postStop logic or something like it.
> 1. Streaming task with jm failover.
> 2. Streaming task with jm failover concurrent to task fail.
> 3. Batch task with jm failover.
> 4. Batch task with jm failover concurrent to task fail.
> 5. Batch task with jm failover when some vertex has already been FINISHED.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
