[
https://issues.apache.org/jira/browse/FLINK-14371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhu Zhu updated FLINK-14371:
----------------------------
Description:
ClassLoaderITCase and now fails with scheduler NG.
There are 3 reasons for the failure:
1. state restore is not supported in scheduler NG yet
2. the cause of the expected exception is a bit different
3. there are multiples tasks in multiple regions, which will result in more
failovers than expected as scheduler NG is using region failover
We need to support the state restore in scheduler NG and them fix this case.
And then annotate it with AlsoRunWithSchedulerNG.
was:
ClassLoaderITCase now fails with scheduler NG.
There are 3 reasons for the failure:
1. state restore is not supported in scheduler NG yet
2. the cause of the expected exception is a bit different
3. there are multiples tasks in multiple regions, which will result in more
failovers than expected as scheduler NG is using region failover
We need to support the state restore in scheduler NG and them fix this case.
And then annotate it with AlsoRunWithSchedulerNG.
> Enable ClassLoaderITCase and EventTimeWindowCheckpointingITCase to pass with
> scheduler NG
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-14371
> URL: https://issues.apache.org/jira/browse/FLINK-14371
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination, Tests
> Affects Versions: 1.10.0
> Reporter: Zhu Zhu
> Priority: Major
> Fix For: 1.10.0
>
>
> ClassLoaderITCase and now fails with scheduler NG.
> There are 3 reasons for the failure:
> 1. state restore is not supported in scheduler NG yet
> 2. the cause of the expected exception is a bit different
> 3. there are multiples tasks in multiple regions, which will result in more
> failovers than expected as scheduler NG is using region failover
> We need to support the state restore in scheduler NG and them fix this case.
> And then annotate it with AlsoRunWithSchedulerNG.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
