kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joel Koshy <jjkosh...@gmail.com>
Subject Re: LinkedIn C++ Implementation
Date Tue, 06 Aug 2013 20:13:33 GMT
Hey Shone,

1) Failover: unfortunately it does not implement retries on failure.
However, it does prevent further loss on those partitions. If we hit
errors while sending to a partition, then we asynchronously fetch
metadata for that topic to determine if we should send to a new leader
for that partition. In the mean time, subsequent messages for that
topic will be partitioned to other (available) partitions.

2) No, but that should not be too difficult to add; at least not as
difficult as (1) I think.



On Tue, Aug 6, 2013 at 12:29 PM, Shone Sadler <shone.sadler@gmail.com> wrote:
> Thanks for the heads up Joel.  We would like to try if possible (we have
> ambitious timelines currently).  Couple of questions though:
> - how robust would you consider the failover support in the current version
> - is there support for compression (Snappy and Gzip)?
> Thanks in advance!
> Shone Sadler
> On Tue, Aug 6, 2013 at 1:10 PM, Joel Koshy <jjkoshy.w@gmail.com> wrote:
>> Hey Shone,
>> Yes this been on my plate for some time but have not had enough time
>> to do the open-sourcing process. We implemented a producer, and hope
>> to release that in a few weeks. I'll send out an email to this list
>> when that happens.
>> Joel
>> On Tue, Aug 6, 2013 at 9:44 AM, Shone Sadler <shone.sadler@gmail.com>
>> wrote:
>> > A few months ago there were discussions around a C/C++ client for Kafka
>> .80
>> > using non-blocking socket I/O that was being worked on by LinkedIn and
>> may
>> > possibly be open sourced.  Has there been any additional work towards the
>> > c++ client and open sourcing it that anyone is aware of?
>> >
>> >
>> > Thanks,
>> > Shone Sadler

View raw message