flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-2159) SimpleRecoveryITCase fails
Date Thu, 04 Jun 2015 12:56:38 GMT

     [ https://issues.apache.org/jira/browse/FLINK-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Stephan Ewen resolved FLINK-2159.
    Resolution: Cannot Reproduce

The cause for the failed test case is that one TaskManager disappeared at some point. It is
impossible to debug this without the proper logs, so we need to wait for this to occur on
a travis build on the apache account.

This is also not a problem inherent to the test, but a random TaskManager instability.

> SimpleRecoveryITCase fails
> --------------------------
>                 Key: FLINK-2159
>                 URL: https://issues.apache.org/jira/browse/FLINK-2159
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: master
>            Reporter: Ufuk Celebi
> https://s3.amazonaws.com/archive.travis-ci.org/jobs/65257722/log.txt
> {code}
> Caused by: org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException:
Not enough free slots available to run the job. You can decrease the operator parallelism
or increase the number of slots per TaskManager in the configuration. Task to schedule: <
Attempt #5 (DataSource (at testRestartMultipleTimes(SimpleRecoveryITCase.java:208) (org.apache.flink.api.java.io.ParallelIteratorInputFormat))
(3/4)) @ (unassigned) - [SCHEDULED] > with groupID < 20c83c1167381bfe663661879f72d07f
> in sharing group < SlotSharingGroup [e9782d396600feda909e1fe6b16d3aaf, 22ffd0dc2c2845bcb0a8d0ba53f68672,
61a229789b0edde1e0acc83e6d2a996b, 20c83c1167381bfe663661879f72d07f] >. Resources available
to scheduler: Number of instances=1, total number of slots=2, available slots=0
> {code}

This message was sent by Atlassian JIRA

View raw message