Hi all!
Right now I am working on reactive streams connector to kafka. I am using
new client and found strange behavior of commitAsync method which not
calling callbacks at all at some cases.
I found, that callback calling is a part of handling of incoming messages.
These messages are not fetchin
ons. So you could call commitAsync()
> with the commits you need to send, then pause the respective partitions.
> After the commit returns, you could resume() the partitions in the commit
> callback, which will reenable fetching.
>
> Hope that helps!
>
> -Jason
>
>
>
&g
ption". Is it another?
>
>
> Haha, this is actually the only option that came to mind for what you're
> trying to do, but I said "one option" in case someone cleverer than I
> thought of another way.
>
> -Jason
>
> On Sat, Feb 6, 2016 at 7:34 AM, Alexey Ro
Hi all!
I am using new client 0.9.0.1.
I found that when I call commitAsync multiple times before calling poll
most of commits failed with SendFailedException.
Here it is an example of code -
https://gist.github.com/13h3r/42633bcd64b80ddffe6b
Could you please explain commitAsync in more details
to open a JIRA if you
> think it would be helpful.
>
> For now, the easiest way to mitigate the problem is probably to batch the
> commits into a single call to commitAsync(). Would that work for you?
>
> -Jason
>
> On Mon, Mar 14, 2016 at 8:18 AM, Alexey Romanchuk <
>
mbers for each partition. I
> haven't
> > thought it all the way through, but you're welcome to open a JIRA if you
> > think it would be helpful.
> >
> > For now, the easiest way to mitigate the problem is probably to batch the
> > commits into a si
ad worked on a patch to fix this at one point. Let me see if I can dig it
> up.
>
> -Jason
>
> On Tue, Mar 15, 2016 at 1:06 AM, Alexey Romanchuk <
> alexey.romanc...@gmail.com> wrote:
>
> > Jay, I am completely agreed with you. From API level it is nothing I can
>
