Re: Keeping logs forever

Hi Graham, This sounds like it should work fine. LinkedIn keeps the majority of things for 7 days. Performance is linear in data size and we have validated performance up to many TB of data per machine. The registry you describe sounds like it could potentially be useful. You would probably have

Please clean your ZK and Kafka data if you check out 0.8 HEAD

Hi all, Today we checked in a patch that standardizes Zookeeper data to use JSON format (KAFKA-755). If you plan to rebase or clone to use the HEAD of 0.8 branch, your next build will have changes to the way Zk data is read and written. This data

Re: Detecting async producer failures (0.7.x)

Are you using your own event handler? If so, you can catch all the exceptions in handle(). Thanks, Jun On Fri, Feb 22, 2013 at 1:34 AM, Michal Haris wrote: > Hi I need to detect and handle exceptions that occur in the > ProducerSendThread of async producer but can't find any discussion or > exa

Re: Keeping logs forever

Apologies for asking another question as a newbie without having really tried stuff out, but actually one of our main reasons for wanting to use kafka (not the linkedin use case) is exactly the fact that the "buffer" is not just for buffering. We want to keep data for days to weeks, and be able to

Re: Advice about running 0.8 tests

Hi Matan, All tests pass successfully on 0.8 HEAD as of today. So that points to some environment issue on your end. Maybe you already have a zookeeper/kafka running on the same box ? Al though its a pain, we currently don't use any tool for viewing the test results, but maybe the new version of s

Advice about running 0.8 tests

Hi, I grabbed the 0.8 branch today and managed building it with SBT as well as in eclipse. I'm running the tests through *./sbt test - *which naturally yields one long output that is very hard to deal with. What's your favorite configuration or tool for viewing kafka 0.8's test results in a more i

Re: status of 0.8?

0.8 branch will be the 0.8 release grabbing HEAD would be 0.8.X or 0.9 changes that don't go in the 0.8 release you should be able to set replication factor = 0 On Fri, Feb 22, 2013 at 5:13 AM, Matan Safriel wrote: > As per 0.8, just a quick question about grabbing HEAD. What's the > difference

Re: status of 0.8?

As per 0.8, just a quick question about grabbing HEAD. What's the difference between the 0.8 branch and the trunk? Also should I take it from Neha's reply that replication is a must in using 0.8 even if you don't wish to use it? is there any design limitation (or operations aspect) that should make

Detecting async producer failures (0.7.x)

Hi I need to detect and handle exceptions that occur in the ProducerSendThread of async producer but can't find any discussion or example how to capture them. Anybody can point me to some resource ? Thanks