Set up
--
Flink verson 1.8.3
Zookeeper HA cluster
1 ResourceManager/Dispatcher (Same Node)
1 TaskManager
4 pipelines running with various parallelism's
Issue
--
Occationally when the Job Manager gets restarted we noticed that all the
pipelines are not getting scheduled. The error that i
bernetes myself,
>> but my colleague Andrey (in CC) reworked Flink's memory configuration for
>> the last release to ease the configuration in container envs.
>> He might be able to help.
>>
>> Best, Fabian
>>
>> Am Do., 21. Mai 2020 um 18:43 Uhr schr
Hi Andrey,
To clarify the above email. I am using Heap Based State and not Rocks DB.
Thanks,
Josson
On Sat, May 23, 2020, 17:37 Josson Paul wrote:
> Hi Andrey,
> We don't use Rocks DB. As I said in the original email I am using File
> Based. Even though our cluster is on
regards,
> Piotrek
>
> [1] https://issues.apache.org/jira/browse/KAFKA-8546
>
> czw., 3 wrz 2020 o 04:47 Josson Paul napisał(a):
>
>> Hi All,
>>
>> *ISSUE*
>> --
>> Flink application runs for sometime and suddenly the CPU shoots up and
>> touches the
anks,
> Piotrek
>
> [1]
> https://ci.apache.org/projects/flink/flink-docs-release-1.5/release-notes/flink-1.5.html
> [2]
> https://ci.apache.org/projects/flink/flink-docs-release-1.8/release-notes/flink-1.8.html
>
> czw., 3 wrz 2020 o 18:50 Josson Paul napisał(a):
>
&g
edMemorySegments, maxNumberOfMemorySegments);
>
> entry logged by
> `org.apache.flink.runtime.io.network.buffer.LocalBufferPool`.
>
> Piotrek
>
> [1] https://en.wikipedia.org/wiki/Java_version_history#Java_8_updates
> [2]
> https://ci.apache.org/projects/flink/flink-docs-rel
We are using Flink version 1.11.2.
At times if task managers are restarted for some reason, the job managers
throw the exception that I attached here. It is an illegal state exception.
We never had this issue with Flink 1.8. It started happening after
upgrading to Flink 1.11.2.
Why are the slots n
