ator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:401)
>> at
>> scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
>> at
>> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
>> at
>> scala.concur
in.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
> at
> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: java.lang.Exception: The slot in
scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: java.lang.Exception: The slot in which the task was executed has
been released. Probably loss of TaskManager
6d2c9d29eddb2a1497827217f4d9a6d1 @ parapluie-28 - 1 slots - URL: akka.tcp://
flink@172.16.99.28:60365/user
ed-coordination-via-akka
>
> Cheers,
> Till
>
>
> On Wed, Mar 16, 2016 at 4:25 PM, Ravinder Kaur wrote:
>>
>> Hello All,
>>
>> I have been facing the Loss of TaskManager issues again. But the
>> JobManager and TaskManager logs showed that eithe
gt; modes
>>>> >> and so I'm running WordCount example with number of iteration (max
>>>> 10) on
>>>> >> datasets of sizes ranging between 100MB and 50GB consisting of
>>>> r
at
>>> >>
>>> org.apache.flink.streaming.api.operators.StreamGroupedReduce.processElement(StreamGroupedReduce.java:59)
>>> >> at
>>> >>
>>> org.apache.flink.streaming.runtime.io.StreamInputProcessor.processInput(StreamInpu
nputStreamTask.java:63)
>> >> at
>> >>
>> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:218)
>> >> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:584)
>> >>
t; >> at
> >>
> org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:218)
> >> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:584)
> >> at java.lang.Thread.run(Thread.java:745)
> >>
> >>
at java.lang.Thread.run(Thread.java:745)
>>
>> I investigated found 2 solutions. (1) Increasing the taskmanager.heap.mb
>> and (2) Reducing the taskmanager.memory.fraction
>>
>> Therefore I set taskmanager.heap.mb: 1024 and
>> taskmanager.memory.fraction: 0
k.runtime.taskmanager.Task.run(Task.java:584)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> I investigated found 2 solutions. (1) Increasing the taskmanager.heap.mb
>> and (2) Reducing the taskmanager.memory.fraction
>>
>> Therefore I set taskmanager.heap.mb: 102
olutions. (1) Increasing the taskmanager.heap.mb
> and (2) Reducing the taskmanager.memory.fraction
>
> Therefore I set taskmanager.heap.mb: 1024 and taskmanager.memory.fraction:
> 0.5 (default 0.7)
>
> When I ran the example with this setting I loose taskmanagers one by one
> dur
kmanagers one by one
during the job execution with the following cause
Caused by: java.lang.Exception: The slot in which the task was executed has
been released. Probably loss of TaskManager
831a72dad6fbb533b193820f45bdc5bc @ vm-10-155-208-138 - 4 slots - URL:
akka.tcp://flink@10.155.208.138:42
InboundHandlerAdapter.userEventTriggered(ChannelInboundHandlerAdapter.java:108)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeUserEventTriggered(AbstractChannelHandlerContext.java:308)
> at
> io.netty.channel.AbstractChannelHandlerContext.access$500(AbstractChannelHandl
g, 25. Februar 2016 12:35
An: user@flink.apache.org
Betreff: Re: loss of TaskManager
Hey Chris!
I think that the full amount of memory to Flink leads to the TM
process being killed by the OS. Can you check the OS logs whether the
OOM killer shut it down? You should be able to see this in the s
ly) run into the
> following problem.
>
> After running for a while, the job fails with the following error:
>
> java.lang.Exception: The slot in which the task was executed has been
> released. Probably loss of TaskManager @ h
the job fails with the following error:
java.lang.Exception: The slot in which the task was executed has been released.
Probably loss of TaskManager @ host slots - URL: akka.tcp://flink@url
2/user/taskmanager
at
org.apache.flink.runtime.instance.SimpleSlot.releaseSlot(SimpleSlot.
;
>> Something similar in flink-0.10-SNAPSHOT:
>>
>> 06/29/2015 10:33:46 CHAIN Join(Join at main(TriangleCount.java:79))
>> -> Combine (Reduce at main(TriangleCount.java:79))(222/224) switched to
>> FAILED
>> java.lang.Exception: The slot in whi
(Reduce at main(TriangleCount.java:79))(222/224) switched to FAILED
> java.lang.Exception: The slot in which the task was executed has been
> released. Probably loss of TaskManager 57c67d938c9144bec5ba798bb8ebe636 @
> wally025 - 8 slots - URL: akka.tcp://
> flink@130.149.249.35:56135/us
vio Pompermaier" :
>>>
>>>> Hi to all,
>>>>
>>>> I have this strange error in my job and I don't know what's going on.
>>>> What can I do?
:
>>
>>> Hi to all,
>>>
>>> I have this strange error in my job and I don't know what's going on.
>>> What can I do?
>>>
>>> The full exception is:
>>>
>>> The slo
m 15.04.2015 14:45 schrieb "Flavio Pompermaier" :
>
>> Hi to all,
>>
>> I have this strange error in my job and I don't know what's going on.
>> What can I do?
>>
>> The full exception is:
>>
>>
t; :
> Hi to all,
>
> I have this strange error in my job and I don't know what's going on.
> What can I do?
>
> The full exception is:
>
> The slot in which the task was scheduled has been killed (probably loss of
> TaskManager).
> at org.apache.flink.run
Hi to all,
I have this strange error in my job and I don't know what's going on.
What can I do?
The full exception is:
The slot in which the task was scheduled has been killed (probably loss of
TaskManager).
at org.apache.flink.runtime.instance.SimpleSlot.cancel(SimpleSlot.j
23 matches
Mail list logo
