One last thing, I have collected a snippet of the network traffic
between Kafka instances using tcpdump. However, it contains some
customer data and less than a minutes worth was over 1 GB, so I can't
really post it here, but I could possibly share offline if it can help
debug the issue.
On Thu, F
Re:
> Could you also check if the on-disk data size/rate match the network
> traffic?
While I have not explicitly checked this, I would say that the answer
is no. The network is over 1Gbps and I have setup monitoring for disk
space and nothing out of the norm is happening there. The expected
data
Ok, sorry for the lock of concrete information to help debug this
issue. I am not really an ops guy, so I am trying to keep up.
First, I added boundary to our servers. Normal Kafka behavior should
be resulting in 500 kbps or less on our cluster. Here you can see that
it's peaking at over 1 Gbps:
Could you also check if the on-disk data size/rate match the network
traffic?
Thanks,
Jun
On Thu, Feb 6, 2014 at 7:48 PM, Carl Lerche wrote:
> So, the "good news" is that the problem came back again. The bad news
> is that I disabled debug logs as it was filling disk (and I had other
> fires
You can run bin/kafka-preferred-replica-election.sh
Thanks,
Jun
On Thu, Feb 6, 2014 at 5:48 PM, Calvin Lei wrote:
> Hi,
> My cluster has 5 topics and each has 1 partition. Each topic has 4
> replicas. For some reasons, the broker leaders of all topics are pointing
> the same box. Is there
Which version are you using? In 0.8, broker failure won't trigger consumer
rebalances. Only changes in #partitions and consumers will trigger
rebalances.
Thanks,
Jun
On Thu, Feb 6, 2014 at 10:46 AM, Yu, Libo wrote:
> While the broker is not available (caused by zookeeper issue), the
> rebalan
So, if you start from scratch (new environment and download of the Kafka
release), could you post the list of steps to reproduce this issue?
On Thu, Feb 6, 2014 at 7:48 PM, Carl Lerche wrote:
> So, the "good news" is that the problem came back again. The bad news
> is that I disabled debug logs
So, the "good news" is that the problem came back again. The bad news
is that I disabled debug logs as it was filling disk (and I had other
fires to put out). I will re-enable debug logs and wait for it to
happen again.
On Thu, Feb 6, 2014 at 4:05 AM, Neha Narkhede wrote:
> Carl,
>
> It will help
Hi,
My cluster has 5 topics and each has 1 partition. Each topic has 4
replicas. For some reasons, the broker leaders of all topics are pointing
the same box. Is there a way for me to shuffle the leaders a bit to avoid
all pointing to the same box?
thanks in advance,
Cal
No. Based on the docs this seemed unnecessary. However, we tried this and
it made no difference. We got the same error.
I'm just confused why a change in the java version would have an effect on
this...
> Did you set both the key and the message encoder to DefaultEncoder?
> Thanks,
> Jun
This is pretty hard to do with the architecture we've gone with as the
stored events are not objects, but tightly packed serialized bytes. This
approach is much better from a performance and memory management point of
view, though, so I'd be very hesitant to change it. So it is pretty hard to
provi
How about the following use case:
Just before the producer actually sends the payload to kakfa, could an
event be exposed that would allow one to loop through the messages and
potentially delete some of them?
Example:
Say you have 100 messages, but before you send these messages to kakfa, you
ca
"Restarted", do you mean restart the process/recreate a consumer from scratch
in order to consume again?
This is quite different from the answer I got previously from here. I have more
questions here.
Is "rebalance.backoff.ms" the time interval between any consecutive retries
before "rebalance
While the broker is not available (caused by zookeeper issue), the rebalance
will fail. Should
rebalance succeed in this case? Thanks.
Regards,
Libo
-Original Message-
From: Guozhang Wang [mailto:wangg...@gmail.com]
Sent: Thursday, February 06, 2014 12:49 PM
To: users@kafka.apache.o
Neha is right, though it is a little interesting that consumers did not
achieve a concensus after four retries have exhasuted, for just an event of
broker-failure.
Could you check your consumer log searching for "begin rebalance" and check
what caused these rebalances to fail?
Guozhang
On Thu,
The consumer only retries "rebalance.max.retries" times. Once it runs out
of the retries, it needs to be restarted to consume again.
On Thu, Feb 6, 2014 at 9:05 AM, Yu, Libo wrote:
> Hi folks,
>
> This is what we experienced recently:
> Some zookeeper's issue made broker unavailable for a sho
Hi folks,
This is what we experienced recently:
Some zookeeper's issue made broker unavailable for a short period of time.
On the consumer side, this triggered rebalance and rebalanced failed after
four tries.
So while should we expect while the broker is not up? Should consumer keep
trying to reb
Joel,
Ah, I actually don't think the internal usage is a problem for *us*. We
just use config in one place, whereas it gets set in 1000s of apps, so I am
implicitly optimizing for the application interface. I agree that we can
add getters and setters on the ProducerConfig if we like. Basically I w
This typically means the broker received a corrupted request. Did you write
the python producer yourself?
Thanks,
Jun
On Wed, Feb 5, 2014 at 11:31 PM, David Montgomery wrote:
> Hi,
>
> I am using the python brod library to write to kafka 8.0.
>
> I am on a 2 core server with 4 gigs of ram on
Carl,
It will help if you can list the steps to reproduce this issue starting
from a fresh installation. Your setup, the way it stands, seems to have
gone through some config and state changes.
Thanks,
Neha
On Wed, Feb 5, 2014 at 5:17 PM, Joel Koshy wrote:
> On Wed, Feb 05, 2014 at 04:51:16PM
After correcting the spelling, it is registered to correct public IP.
Thanks
Bala
-Original Message-
From: Jun Rao [mailto:jun...@gmail.com]
Sent: Thursday, 6 February, 2014 2:04 PM
To: users@kafka.apache.org
Subject: Re: Reg Exception in Kafka
I think you mis-spelled the property name.
21 matches
Mail list logo
