You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2018/04/03 10:44:00 UTC
[jira] [Resolved] (FLINK-8973) End-to-end test: Run general purpose
job with failures in standalone mode
[ https://issues.apache.org/jira/browse/FLINK-8973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther resolved FLINK-8973.
---------------------------------
Resolution: Fixed
Fixed in 1.6.0: a666455c98c269c63373e991c6ca2751e132a7c8
Fixed in 1.5.0: dffbf41813f42bfa2638e36e6051e3add2c00e63
> End-to-end test: Run general purpose job with failures in standalone mode
> -------------------------------------------------------------------------
>
> Key: FLINK-8973
> URL: https://issues.apache.org/jira/browse/FLINK-8973
> Project: Flink
> Issue Type: Sub-task
> Components: Tests
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Assignee: Kostas Kloudas
> Priority: Blocker
> Fix For: 1.5.0
>
>
> We should set up an end-to-end test which runs the general purpose job (FLINK-8971) in a standalone setting with HA enabled (ZooKeeper). When running the job, the job failures should be activated.
> Additionally, we should randomly kill Flink processes (cluster entrypoint and TaskExecutors). When killing them, we should also spawn new processes to make up for the loss.
> This end-to-end test case should run with all different state backend settings: {{RocksDB}} (full/incremental, async/sync), {{FsStateBackend}} (sync/async)
> We should then verify that the general purpose job is successfully recovered without data loss or other failures.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)