Are you seeing errors for metadata update?
If yes, I think I know why this might be happening.
Thanks,
Mayuresh
On Tue, Nov 10, 2015 at 6:35 PM, Mayuresh Gharat wrote:
> How many brokers are there in your test cluster?
>
>
> Thanks,
>
> Mayuresh
>
> On Tue, Nov 10, 2015 at 5:53 PM, Jason Gus
How many brokers are there in your test cluster?
Thanks,
Mayuresh
On Tue, Nov 10, 2015 at 5:53 PM, Jason Gustafson wrote:
> Hey Luke,
>
> I agree the null check seems questionable. I went ahead and created
> https://issues.apache.org/jira/browse/KAFKA-2805. At least we should have
> a
> comme
Hey Luke,
I agree the null check seems questionable. I went ahead and created
https://issues.apache.org/jira/browse/KAFKA-2805. At least we should have a
comment clarifying why the check is correct.
-Jason
On Tue, Nov 10, 2015 at 2:15 PM, Luke Steensen <
luke.steen...@braintreepayments.com> wrot
After some more investigation, I've been able to get the expected behavior
by removing the null check here:
https://github.com/apache/kafka/blob/ae5a5d7c08bb634576a414f6f2864c5b8a7e58a3/clients/src/main/java/org/apache/kafka/clients/producer/internals/RecordAccumulator.java#L220
Hopefully someone
Hello,
We've been testing recent versions of trunk and are seeing surprising
behavior when trying to use the new request timeout functionality. For
example, at revision ae5a5d7:
# in separate terminals
$ ./bin/zookeeper-server-start.sh config/zookeeper.properties
$ ./bin/kafka-server-start.sh con
