Hi,
The problem is that most of the exceptions appear when my job has been
running for some hours.
The only way for me to reproduce some of those errors is by using the web UI
and hitting the cancel button of my job. So if I can find a way to generate
this action locally in a test, maybe I can
An additional question is that if the source is key partitioned ( kafka )
does a keyBy retain the order of a kafka partirion across a shuffle ?
On Fri, Dec 8, 2017 at 1:12 PM, Vishal Santoshi
wrote:
> I understand that. Let me elaborate. The sequence of events is
>
> 1. Round robin dispatch to
Hi there,
In recent, our production fink jobs observed some weird performance issue.
When job tailing kafka source failed and try to catch up, asyncIO after
event trigger get much higher load on task thread. Since each TM allocated
two virtual CPU in docker, my assumption was akka message between
