But if sends are not done in blocking way (with .get()) how does acks matter ?
-Original Message-
From: Matthias J. Sax
Sent: Saturday, November 17, 2018 12:15 AM
To: users@kafka.apache.org
Subject: Re: Producer throughput with varying acks=0,1,-1
I you enable acks, it's not fire and
Hello Patrik,
Could you file a JIRA for your findings? Also what Kafka versions are you
using (could you add that to the ticket as well)?
Could you provide some more elaborations on what you did the JVM analysis,
so that I can try to re-produce the observations.
Guozhang
On Thu, Oct 25, 2018
Hi Patrik,
Thanks for explaining your use case to us. While we can still discuss how
KStream should interpret null-values in aggregations, one workaround atm:
if you deduplication logic can be written as a transformValues operation,
you can do the following:
Thanks for the reply.
It would be interesting who else is using IQ with or without GlobalKTables and
what problems and solutions they have come up with.
Best regards
Patrik
> Am 18.11.2018 um 20:21 schrieb Matthias J. Sax :
>
> Because each instance needs to consume all data, it's limited by
Because each instance needs to consume all data, it's limited by what a
single instance can consume -- a hard bound is the network. Note,
network is shared, so don't take the maximum network speed into account.
Also, it's not the number of unique messaged, but the number of updates
that is
+1 (non-binding)
- Ran testAll/releaseTarGzAll on 2.1.0 successfully without any failures.
- Ran through quickstart of core/streams on builds generated from tag
- Ran few internal apps targeting to topics on 3 node cluster.
Thanks,
Satish.
On Sun, Nov 18, 2018 at 4:58 AM Jakub Scholz wrote:
>
>
