Hi Mathieu,
if you are happy to share your code privately it would help. At the moment
i'm struggling to see how we can get into this situation, so i think your
topology would be useful.
Thanks,
Damian
On Mon, 5 Dec 2016 at 16:34 Mathieu Fenniak
wrote:
> Hi Damian,
>
> Yes... I can see how mo
Hi Damian,
Yes... I can see how most of the stack trace is rather meaningless.
Unfortunately I don't have a minimal test case, and I don't want to burden
you by dumping the entire application. (I could share it privately, if
you'd like.)
Based upon the stack trace, the relevant pieces involved a
Hi Mathieu,
I'm trying to make sense of the rather long stack trace in the gist you
provided. Can you possibly share your streams topology with us?
Thanks,
Damian
On Mon, 5 Dec 2016 at 14:14 Mathieu Fenniak
wrote:
> Hi Eno,
>
> This exception occurred w/ trunk @ e43bbce (current as-of Saturday
Hi Eno,
This exception occurred w/ trunk @ e43bbce (current as-of Saturday). I was
bit by KAFKA-4311 (I believe) when trying to upgrade to 0.10.1.0, so with
that issue now resolved I thought I'd check trunk out to see if any other
issues remain.
Mathieu
On Sun, Dec 4, 2016 at 12:37 AM, Eno The
Hi Mathieu,
What version of Kafka are you using? There was recently a fix that went into
trunk, just checking if you're using an older version.
(to make forward progress you can turn the cache off, like this:
streamsConfiguration.put(StreamsConfig.CACHE_MAX_BYTES_BUFFERING_CONFIG, 0);
)
Thanks
E
Hey all,
I've just been running a quick test of my kafka-streams application on the
latest Kafka trunk (@e43bbce), and came across this error. I was wondering
if anyone has seen this error before, have any thoughts on what might cause
it, or can suggest a direction to investigate it further.
Ful
