Re: session.timeout.ms limit - Kafka Consumer

This topic is currently being discussed at https://issues.apache.org/jira/browse/KAFKA-2986 and https://cwiki.apache.org/confluence/display/KAFKA/KIP-41%3A+KafkaConsumer+Max+Records On 3/2/16, 8:11 AM, "Vanessa Gligor" wrote: >Hello, > >I am using Kafka higher

Re: Turn off retention.ms

A very high retention time (e.g. 50 years in milliseconds) would effectively accomplish this. On 3/1/16, 8:39 AM, "Roshan Punnoose" wrote: >Hi, > >Is it possible to set up a topic with only a size limit (retention.bytes) >and not a time limit (retention.ms)? > >Roshan

Re: Questions about unclean leader election and "Halting because log truncation is not allowed"

unclean.leader.election.enable is actually a valid topic-level configuration, I opened https://issues.apache.org/jira/browse/KAFKA-3298 to get the documentation updated. That code comment doesn’t tell the complete story and could probably be updated for clarity as we’ve learned a lot since

Re: Kafka log compression change in 0.8.2.1?

compressed message. Are you using mirror maker to copy data from the 0.8.1 cluster to the 0.8.2 cluster? If so, this may have to do with the batching in the producer in mirror maker. Did you enable the new java producer in mirror maker? Thanks, Jun On Mon, May 11, 2015 at 12:53 PM, Olson

Kafka log compression change in 0.8.2.1?

After a recent 0.8.2.1 upgrade we noticed a significant increase in used filesystem space for our Kafka log data. We have another Kafka cluster still on 0.8.1.1 whose Kafka data is being copied over to the upgraded cluster, and it is clear that the disk consumption is higher on 0.8.2.1 for the

Re: [DISCUSS] Release 0.8.2-beta before 0.8.2?

https://issues.apache.org/jira/browse/KAFKA-1647 sounds serious enough to include in 0.8.2-beta if possible. CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is

Re: Kafka Mock

You might take a look at the KafkaServerTestHarness [1] if you’re not already familiar with it. It’s not exactly “mock”, but it makes it easy to test Kafka functionality without needing to connect to any external broker or ZK processes. We ported this test harness to Java for our junit and