Any update on this? Do you want me to create a JIRA issue for this bug?
On 11 Oct 2017 17:14, "Ufuk Celebi" wrote:
@Chesnay: Recycling of network resources happens after the tasks go
into state FINISHED. Since we are submitting new jobs in a local loop
here it can easily happen that the new job
@Chesnay: Recycling of network resources happens after the tasks go
into state FINISHED. Since we are submitting new jobs in a local loop
here it can easily happen that the new job is submitted before enough
buffers are available again. At least, previously that was the case.
I'm CC'ing Nico who r
I can confirm that the issue is reproducible with the given test, from
the command-line and IDE.
While cutting down the test case, by replacing the outputformat with a
DiscardingOutputFormat and the JDBCInputFormat with a simple collection,
i stumbled onto a new Exception after ~200 iterations
Hi to all,
we wrote a small JUnit test to reproduce a memory issue we have in a Flink
job (that seems related to Netty) . At some point, usually around the 28th
loop, the job fails with the following exception (actually we never faced
that in production but maybe is related to the memory issue some
