Have you verified that the old leader of the partition is using the same
I'd as before? Check in zk /brokers/ids to get a list of available
brokers. I would use the reassignment tool to move partition 3 to brokers
in the list from zk (specifying only 3 brokers). Make sure to include
broker with
What about in dmesg? I have run into this issue and it was the OOM
killer. I also ran into a heap issue using too much of the direct memory
(JVM). Reducing the fetcher threads helped with that problem.
On Jun 2, 2016 12:19 PM, "allen chan" wrote:
> Hi Tom,
>
> That is one of the first things t
I am using JMX to gather kafka metrics. It states here
http://docs.confluent.io/1.0/kafka/monitoring.html that they should be
there. But when I run a jmx client and show beans kafka.consumer and
kafka.producer do not exist. Is there something special I have to do to
get these metrics?
Thanks
ey should eventually catch back up and rejoin the ISR. Did they not?
>
> Alex
>
> On Fri, May 13, 2016 at 6:33 PM, Russ Lavoie wrote:
>
> > Hello,
> >
> > I moved an entire topic from one set of brokers to another set of
> brokers.
> > The network throughput
Hello,
I moved an entire topic from one set of brokers to another set of brokers.
The network throughput was so high, that they fell behind the leaders and
dropped out of the ISR set. How can I recover from this?
Thanks!
Good Afternoon,
I am currently trying to do a rolling upgrade from Kafka 0.8.2.1 to 0.9.0.1
and am running into a problem when starting 0.9.0.1 with the protocol
version 0.8.2.1 set in the server.properties.
Here is my current Kafka topic setup, data retention and hardware used:
3 Zookeeper node
