flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2829) Confusing error message when Flink cannot create enough task threads
Date Tue, 17 May 2016 12:38:12 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286519#comment-15286519

ASF GitHub Bot commented on FLINK-2829:

Github user gyfora commented on the pull request:

    This is Jira issue that I opened a qhile back and forgot about it :) The issue was not
really that the Slot name was not well formatted etc, it's more thatn this type of error was
very hard to debug as the exception message does not contain any info about the cause (out-of-memory
error during thread creation)

> Confusing error message when Flink cannot create enough task threads
> --------------------------------------------------------------------
>                 Key: FLINK-2829
>                 URL: https://issues.apache.org/jira/browse/FLINK-2829
>             Project: Flink
>          Issue Type: Improvement
>          Components: JobManager, TaskManager
>            Reporter: Gyula Fora
>            Priority: Trivial
> When Flink runs out of memory while creating too many task threads, the error message
received from the job manager is slightly confusing:
> java.lang.Exception: Failed to deploy the task to slot SimpleSlot (1)(63) - eea7250ab5b368693e3c4f14fb94f86d
@ localhost - 8 slots - URL: akka://flink/user/taskmanager_1 - ALLOCATED/ALIVE: Response was
not of type Acknowledge 
> at org.apache.flink.runtime.executiongraph.Execution$2.onComplete(Execution.java:392)

> at akka.dispatch.OnComplete.internal(Future.scala:247) 
> at akka.dispatch.OnComplete.internal(Future.scala:244) 
> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:174) 
> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:171) 
> at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32) 
> at scala.concurrent.impl.ExecutionContextImpl$anon$3.exec(ExecutionContextImpl.scala:107)

> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) 
> at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) 
> at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) 
> at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Although the error comes from the Taskmanager:
> java.lang.OutOfMemoryError: unable to create new native thread
> 	at java.lang.Thread.start0(Native Method)
> 	at java.lang.Thread.start(Thread.java:714)
> 	at org.apache.flink.runtime.taskmanager.Task.startTaskThread(Task.java:415)
> 	at org.apache.flink.runtime.taskmanager.TaskManager.submitTask(TaskManager.scala:904)

This message was sent by Atlassian JIRA

View raw message