kafka 0.8.1.1 delay in replica data

i set a topic retention.ms as 36;and then i find the replica data is delay. What could cause this? as follows screenshot: master broker: replica broker: Thanks， Lax

RE: kafka 0.8.1.1 delay in replica data

topic: Topic_test_data_1-10 leader broker data info: -rw-rw-r-- 1 mqq mqq237728 Dec 23 19:51 000211076304.index -rw-rw-r-- 1 mqq mqq 536875106 Dec 23 19:51 000211076304.log -rw-rw-r-- 1 mqq mqq237632 Dec 23 19:45 000203797807.index -rw-rw-r-- 1 mqq mqq 536879703

Treating a specific topic as in-memory only

Hello, I have a specific use-case where I am not allowed to persist a certain kind of events. The events can be kept in memory, but not written to the disk. Is this even possible with Kafka? Ideally I am looking for a per topic configuration to disable the writing to disk. The durability of the

Re: Treating a specific topic as in-memory only

Hi, you could configure the topic to reside on a tmp-fs mount (i.e., in memory filesystem with no disk backing). /Magnus 2014-12-23 15:38 GMT+01:00 Olof Johansson : > Hello, > > I have a specific use-case where I am not allowed to persist a certain kind > of events. The events can be kept in m

Re: Kafka 0.8.2 release - before Santa Claus?

Hi, I see 16 open issues for 0.8.2 at https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20fixVersion%20%3D%200.8.2%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20updated%20DESC%2C%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC - some with patches, some blockers, som

Re: Kafka 0.8.1.1 Leadership changes are happening very often

I was already using 4GB heap memory. I even changed to 8 GB heap memory and could see leadership changing very often. In my 5 minute run, I saw leadership changed from 1,2,3 to 3,3,3, to 1,1,1. Also my message rate is just: 7k and total msg count is only 2,169,001. Does anyone has cline on lea

Kafka 0.8.2 new producer blocking on metadata

I was just fighting this same situation. I never expected the new producer send() method to block as it returns a Future and accepts a Callback. However, when I tried my unit test, just replacing the old producer with the new, I immediately started getting timeouts waiting for metadata. I struggled

Re: Better handling of exception in kafka.producer.async.DefaultEventHandler

handle() will throw the exception to the caller. In sync mode, client will receive the exception, but in async mode, there's an independent thread actually doing the sending. It's not easy to inform the caller except for blocking the queue. In practice, you can configure the retry times, and each t