You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/09/13 13:06:00 UTC
[jira] [Closed] (FLINK-5140) NoResourceAvailableException is thrown
while starting a new job
[ https://issues.apache.org/jira/browse/FLINK-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till Rohrmann closed FLINK-5140.
--------------------------------
Resolution: Abandoned
> NoResourceAvailableException is thrown while starting a new job
> ---------------------------------------------------------------
>
> Key: FLINK-5140
> URL: https://issues.apache.org/jira/browse/FLINK-5140
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Environment: FLIP-6 feature branch
> Reporter: Biao Liu
> Assignee: Stephan Ewen
> Priority: Minor
> Labels: flip-6
>
> Here is the stack trace:
> org.apache.flink.runtime.jobmanager.scheduler.NoResourceAvailableException: not connected to ResourceManager and no slot available
> at org.apache.flink.runtime.instance.SlotPool.internalAllocateSlot(SlotPool.java:281)
> at org.apache.flink.runtime.instance.SlotPool.allocateSlot(SlotPool.java:256)
> ...
> Currently I have to set RestartStrategy to handle this exception. But in some test cases, I want to test failure about the cluster. It will make this much more complicated. After discussing with [~tiemsn], maybe we can fix this problem by executing executionGraph after registered to resource manager.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)