Hi Mohammad,
Leader elections are generally seldom and usually quick.
If a leader is unable to elected, this could point to a) replication being
set too low or b) inter-broker communication issues, plus a bunch of other
possible problems.
You'd have to look into your Kafka broker's logs to
Hi There,
we are facing following issue in kafka. We have gone through some of the
references and found it as a bug from kafka side. Please let us know if there
are any solutions.
│ 47] [PID:1] Producer send message failed, err:kafka server: In the middle of
a leadership election, there is
Hi,
I wish to address an issue.
Certificates of Kafka broker in Control plane expired which impacted Kafka
Mirror maker service in all dataplanes. As a result, we renewed Kafka broker
certificates manually in Control plane which restored kafka mirror maker
service.
Short Term actions include:
>
> Am 10.12.2019 um 06:36 schrieb Valentin :
>
> Hi Chao,
>
> I suppose, you would like to know:
> within a consumer group which message is coming from which partition, since
> partitions corresponds to broker and broker = ip, right?
>
> Well, if you really want to know this, then you have
Hi Chao,
I suppose, you would like to know:
within a consumer group which message is coming from which partition, since
partitions corresponds to broker and broker = ip, right?
Well, if you really want to know this, then you have to get the context. E.g
within a processor there is a method
hi:
I am a gteen hand of kafka，after installation of new kafka cluster，it
raises a question that how do I know which IP address a message come from?
Is there any special set about this?
Eagerly awaiting your reply.
chao@baozun.com
maybe I should highlight, I only publish 1 key. so only one broker is going
to handle it. and only 1 stream instance handle it too. what's the typical
throughput/latency I should expect in this case? assuming the processing
logic is very very simple, just get data(integer) and sum. I am more
I did several test. one is with 10 brokers (remote server),
one with 3 brokers. (local docker)
both exhibit the same behavior, I was thinking the same but from at least
the kafka log, I don't see a rebalance happening. and I am sure my cpu is
only used about half. and all broker still
How many brokers are there in your cluster? This error usually comes when
one of the brokers who is leader for a partition dies and you are trying to
access it.
On Fri, Aug 17, 2018 at 9:23 PM Harish K wrote:
> Hi,
>I have installed Kafka and created topic but while data ingestion i get
>
Hi,
I have installed Kafka and created topic but while data ingestion i get
some errors as follows.Any help would be really appreciated
[2018-08-17 06:12:49,838] WARN Error while fetching metadata with
correlation id 24 :
Hi team,
I am new to Kafka and I am trying to learn the basics. I have issued
command after
creating topic test in a single node cluster-
/opt/cloudera/parcels/KAFKA-2.1.1-1.2.1.1.p0.18/lib/kafka/bin/kafka-console-producer.sh
--broker-list :9092 --topic test
And then I pass message *This Is
Hi,
Seeing below exceptions on broker id 3 node, in my three node kafka
cluster.Also looks like this broker id is long under replicated and out of sync.
[2016-04-06 04:00:00,720] ERROR [Replica Manager on Broker 3]: Error processing
fetch operation on partition [subscribed_product_logs,2] offset
Hi,
Seeing below exceptions on broker id 3 node, in my three node kafka
cluster.Also looks like this broker id is long under replicated and out of sync.
[2016-04-06 04:00:00,720] ERROR [Replica Manager on Broker 3]: Error processing
fetch operation on partition [subscribed_product_logs,2]
Hi,
We recently ran into a scenario where we initiate a FetechRequest with a
fixed fetchSize (64k) shown below using Simple Consumer. When the broker
contains an unusually large sized message, this resulted in the broker
returns an empty message set *without any error code*. According to the
Opened a kafka issue for rebalance happening with auto.rebalance set to false.
https://issues.apache.org/jira/browse/KAFKA-2011
Logs for rebalance:
[2015-03-07 16:52:48,969] INFO [Controller 2]: Resuming preferred replica
election for partitions: (kafka.controller.KafkaController)
[2015-03
Hello,
We've an issue on our Kafka production. (Kafka 0.8.1.1 on 9 Debian Wheezy
servers).
We tried to move a topic from a server to another, but no data was created
on the target.
After some tries when decidec to stop Kafka on this server (kafka3),
removed all topic's data on /var/lib/kafka/*
Hi,
One of the broker seems to have got corrupted in my cluster of 7
brokers. All the topic partitions where this broker was leader are having
NoLeader or UnderReplicated partition exceptions.
All these partittions have no leader and even no replica in the isr(in-sync
replica) set.
Corrupt
It looks like broker 5 is in a bad state. You are likely going to have to
shut it down. From there you have a few options and depending on your
environment setup will dictate if you do shut it down and/or what you do
after that. Spinning up another server with broker.id == 5 and let
replication
Hi,
Thanks for your reply.
I can't see anything in the broker logs, , except this keeps coming up in
the zookeeper log (instance 1 out of 3):
WARN [SyncThread:1:FileTxnLog@321] - fsync-ing the write ahead log in
SyncThread:1 took 1298ms which will adversely effect operation latency. See
the
The reconnect is due to the socket connection to Kafka broker. Technically,
reconnect worked. So the tool still produces the output. The reconnection
is weird though. Do you see the same reconnection when you run console
consumer?
Thanks,
Jun
On Tue, Jul 9, 2013 at 11:06 AM, Dennis Haller
The consumer reconnects because the broker closed the socket. Any
error/exception on the broker side around the same time?
Thanks,
Jun
On Mon, Jul 8, 2013 at 10:25 AM, Dennis Haller dhal...@talemetry.comwrote:
I have a 4-broker Kafka system running in Amazon EC2, and we are using
Kafka 0.8
21 matches
Mail list logo
