[
https://issues.apache.org/jira/browse/FLINK-15105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992425#comment-16992425
]
Till Rohrmann commented on FLINK-15105:
---------------------------------------
I'm not sure whether it is the problem of the {{FailureMapper}}. The failure
mapper is an operator which throws exceptions after processing a given amount
of records and having completed so and so many checkpoints. This sounds fine to
me. I believe the problem is more how the test is set up and maybe the
assumptions about the job behaviour are wrong. But then we should rather
correct the test or its setup instead of removing the {{FailureMapper}}.
> Resuming Externalized Checkpoint after terminal failure (rocks, incremental)
> end-to-end test stalls on travis
> -------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-15105
> URL: https://issues.apache.org/jira/browse/FLINK-15105
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
> Affects Versions: 1.10.0
> Reporter: Yu Li
> Priority: Critical
> Labels: test-stability
> Fix For: 1.10.0
>
>
> Resuming Externalized Checkpoint after terminal failure (rocks, incremental)
> end-to-end test fails on release-1.9 nightly build stalls with "The job
> exceeded the maximum log length, and has been terminated".
> https://api.travis-ci.org/v3/job/621090394/log.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
