We have a kafka cluster with 22 nodes, which host ~3700 topics and ~15000
partitions.
We ran fine for a long time but, one fine day a bunch of brokers (around half
of the cluster) started getting out of ISRs with the following messages in the
leaders:A)
[2016-01-12 19:01:19,363] INFO Partitio
Hi Rajiv,
This is expected. Newer broker versions support older client versions, but
newer client versions don't support older broker versions.
Ismael
On Wed, Jan 13, 2016 at 10:54 PM, Rajiv Kurian wrote:
> We just upgraded one of our Kafka client producers from 0.8.2 to 0.9. Our
> broker is s
We just upgraded one of our Kafka client producers from 0.8.2 to 0.9. Our
broker is still running 0.8.2. I knew that the new 0.9 consumer requires
the new broker and I was under the impression that the new producer would
still work with the old broker. However this doesn't seem to be the case.
I k
Oh, great, I get it. Thank you.
On Mon, Jan 4, 2016 at 6:26 PM, tao xiao wrote:
> You can bump the log level to warn for a particular class
>
> log4j.logger.kafka.network.Processor=WARN
>
> On Tue, 5 Jan 2016 at 08:33 Dillian Murphey
> wrote:
>
> > Constant spam of this INFO on my log.
> >
> >
Update: I have completely uninstall kafka v10 and v17 and reinstalled and all
is right with the world.
-Original Message-
From: Heath Ivie [mailto:hi...@autoanything.com]
Sent: Wednesday, January 13, 2016 11:59 AM
To: users@kafka.apache.org
Subject: RE: 409 Conflict
Hi Ewen,
When I fol
Hi Ewen,
When I follow the exact sequence with the curl commands below I get this error.
It seems to register fine, because I get the baseuri and the instance id.
This is the error that I get when I try to read from the topic:
{
"error_code": 40901,
"message": "Consumer cannot subscribe the
Hi All,
I am facing issues deleting config for a topic in Kafka 0.9. Anybody facing the
same issue?
./kafka-topics.sh —zookeeper XX.XX.XX.XXX:2181 --alter --topic testTopic
--deleteConfig retention.ms
Exception in thread "main" joptsimple.UnrecognizedOptionException:
'deleteConfig' is not a
Thanks!
On Wed, Jan 13, 2016 at 9:06 AM, Guozhang Wang wrote:
> Rajiv,
>
> 0.9.0 Java producers have a few minor bug fixes from 0.8.2, and add another
> API function "flush()": https://issues.apache.org/jira/browse/KAFKA-1865
>
> You can look through its changes by just searching "producer" in t
Rajiv,
0.9.0 Java producers have a few minor bug fixes from 0.8.2, and add another
API function "flush()": https://issues.apache.org/jira/browse/KAFKA-1865
You can look through its changes by just searching "producer" in the
release notes:
http://mirror.stjschools.org/public/apache/kafka/0.9.0.0
Yes, that was my intention and we have both of those configs turned on. For
some reason, however, the controlled shutdown wasn't transferring
leadership of all partitions, which caused the issues I described in my
initial email.
On Wed, Jan 13, 2016 at 12:05 AM, Ján Koščo <3k.stan...@gmail.com> w
Hi,
I found that the latest mirror maker with new consumer enabled was unable
to commit offset in time when mirroring a topic with very infrequent
messages.
I have a topic with a few of messages produced every half hour. I setup
mirror maker to mirror this topic with default config. I observed th
I can't really answer your question, but you don't mention your network
layout/hardware. May want to add that as a data point in your decision
(wouldn't want to overrun your network device(s) on the brokers).
On Wed, Jan 13, 2016 at 7:09 PM, Vladoiu Catalin
wrote:
> Hi guys,
>
> I've run into
Hi guys,
I've run into a long conversation with my colleagues when we discussed the
size of the Brokers for our new Kafka cluster and we still haven't reached
a final conclusion.
Our main concern is the size of the requests 10-20MB per request (producer
will send big requests), maybe more and we
13 matches
Mail list logo
