;>>> discovered the source of the problem only running the program on a subset
>>>> of the data.
>>>>
>>>> Thnks for the support,
>>>> Flavio
>>>>
>>>> On Wed, Apr 15, 2015 at 2:56 PM, Stephan Ewen wrote:
>>>>
g ob the TaskManager
>>>> as failed.
>>>>
>>>> Have a look at the TaskManager log, it should describe why the
>>>> TaskManager failed.
>>>> Am 15.04.2015 14:
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
