ure latency at (e.g. 10
> > records/sec).
> > > > > >>
> > > > > >> -Jay
> > > > > >>
> > > > > >> On Thu, Aug 13, 2015 at 12:18 PM, Yuheng Du <
> > > yuheng.du.h...@gmail.com
> > > > >
> > &g
Which version of Kafka are you using?
> thanks.
>
> On Thu, Aug 13, 2015 at 3:01 PM, Alvaro Gareppe
> wrote:
>
> > Are you measuring latency as time between producer and consumer ?
> >
> > In that case, the ack shouldn't affect the latency, cause even tough yo
with sync producers, but the throughput
is much lower in that case.
About not flushing to disk I'm pretty sure that it's not an option in kafka
(correct me if I'm wrong)
Regards,
Alvaro Gareppe
On Thu, Aug 13, 2015 at 12:59 PM, Yuheng Du
wrote:
> Also, the latency results s
I'm starting to use kafka for a low latency application.
I need a topic that has over all process latency around 2 or 3 ms, (latency
from producer to consumer)
I want to use a async producer, but I'm not getting it to work that fast.
What are the key properties to configure in: producer, consumer
Is this discussion open ? Cause this is exactly what I’m looking for.
mber of
> > topics/partitions pairs but each one incurs a cost. Thus this route may
> not
> > be wise for the use case you are describing.
> >
> > B
> > > On 6 Aug 2015, at 16:38, Alvaro Gareppe wrote:
> > >
> > > Is not because of throughput is mor
would have to be a
> relatively simple use case. Kafka will support a large number of
> topics/partitions pairs but each one incurs a cost. Thus this route may not
> be wise for the use case you are describing.
>
> B
> > On 6 Aug 2015, at 16:38, Alvaro Gareppe wrote:
> >
&
nd starting simple and just dropping the messages you don't
> care about on the consumer side. If throughput becomes a problem, then
> consider alternatives.
>
>
> On Thu, Aug 6, 2015 at 9:47 AM, Alvaro Gareppe wrote:
>
> > Is this implemented ?
> > https://cwiki.apache
pluggable selector logic in the
> new consumer. I can't guarantee it will happen, there are infinite things
> that can be plugged into consumers and we need to draw the line somewhere,
> but worth a discussion.
>
> On Tue, Aug 4, 2015 at 2:05 PM, Alvaro Gareppe wrote:
>
The is way to implement a "selector" logic in kafka (similar to JMS
selectors)
So, allow to consume a message if only the message contains certain header
or content ?
I'm evaluating to migrate from ActiveMQ to kafka and I'm using the selector
logic widely in the applicat
!
--
Eng. Alvaro Gareppe
11 matches
Mail list logo