You can connect to the TaskManagers with a tool such as jvisualvm to observe
where the objects are created. It doesn't sound normal that there are millions
of these objects if only a couple thousand elements come in.
> On 25. Jan 2018, at 14:59, Fabian Hueske wrote:
>
> Aljoscha (in CC), do yo
Aljoscha (in CC), do you have an idea about this issue?
Thanks,
Fabian
2018-01-24 7:06 GMT+01:00 Navneeth Krishnan :
> Thanks Fabian but for 1.5k messages per second per TM there are several
> million Internal & TimerWindow objects created within a period of 5
> seconds. Is there a way to get de
Thanks Fabian but for 1.5k messages per second per TM there are several
million Internal & TimerWindow objects created within a period of 5
seconds. Is there a way to get debug this issue?
Regards,
Navneeth
On Tue, Jan 23, 2018 at 2:09 AM, Fabian Hueske wrote:
> Hi,
>
> TimeWindows and Timers a
Hi,
TimeWindows and Timers are created for each window, i.e., every 5 seconds
for every distinct key that a task is processing.
Event-time windows are completed and cleaned up when a watermark is
received that passes the window end timestamp.
Therefore, there might be more than one window per key
Hi,
I'm facing issues with frequent young generation garbage collections in my
task manager which happens approximately every few seconds. I have 3 task
managers with 12GB heap allocated on each and I have set the config to use
G1GC. My program ingests binary data from kafka source and the message
