We have high-volume topics and low-volume topics. The problem occurs more
often for low-volume topics to be sure.
But if my hypothesis is correct about why it is happening, here is a case
where rolling is longer than an hour, even on a high volume topic:
- write to a topic for 20 minutes
- restar
That logic in 0.7.2 seems correct. Basically, firstAppendTime is set on
first append to a log segment. Then, later on, when a new message is
appended and the elapsed time since firstAppendTime is larger than the roll
time, a new segment is rolled. Is your data constantly being produced?
Thanks,
J
Thanks. Is anyone able to run the 0.8 quickstart without this issue on
Windows?
Jun
On Thu, Apr 25, 2013 at 10:27 AM, Yin Yin wrote:
> How to make sure the code is the latest? I ran these commands. Created the
> ticket KAFKA-876 for this issue. Thanks a lot
>
> PS C:\Projects\Kafka\kafka> git
Yes, like in KAFKA-876's producer log, I only get one
LeaderNotAvailableException. Thanks for fixing this issue, though could it
only be fixed in the 0.8 branch? A colleague is having the issue tonight
and I think he may be on the trunk.
Like KAFKA-876, I am now getting the
WARN [Kaf
Rob,
Are you saying that LeaderNotAvailableException happens only once and then
disappears? That is normal and is different from what happens in KAFKA-876.
Thanks,
Jun
On Thu, Apr 25, 2013 at 8:41 PM, Withers, Robert wrote:
> This LeaderNotAvailableException only occurs once now, running kafk
1. Take a look at #6 in http://kafka.apache.org/faq.html
2. Typically, you want each batch to have 10s-100s KB.
3. In the latest 0.8, we have 3 network threads and 8 io threads. These
should be good enough for typical users.
Thanks,
Jun
On Thu, Apr 25, 2013 at 2:30 PM, Yu, Libo wrote:
> Hi,
hi,
my name is subhankar. i want to subscribe the group
This LeaderNotAvailableException only occurs once now, running kafka 8 from a
dos shell. We are following KAFKA-876 closely which we also experience.
thanks!
rob
From: Withers, Robert
Sent: Friday, April 19, 2013 6:38 AM
To: users@kafka.apache.org
Subject
Hi,
I have a few questions about configuring kafka 0.8.
Assume I have 3 brokers, 10 consumers and 4 topics.
1 How many partitions should a topic have for best performance?
Each broker has one partition? Or each producer should have a partition?
2 Batch size has big impact on per
Thanks. Setting --request-num-acks to 0 disables acknowledgement. Otherwise,
enable the acknowledgement.
Regards,
Libo
We are running Kafka 0.7.2. We set log.roll.hours=1. I hoped that meant
logs would be rolled every hour, or more. Only, sometimes logs that are
many hours (sometimes days) old have more data added to them. This perturbs
our systems for reasons I won't get in to.
Have others observed this? Is it a
How to make sure the code is the latest? I ran these commands. Created the
ticket KAFKA-876 for this issue. Thanks a lot
PS C:\Projects\Kafka\kafka> git branch
* 0.8
trunk
PS C:\Projects\Kafka\kafka> git pull
Already up-to-date.
PS C:\Projects\Kafka\kafka>
=Broker Log===
Yes, there is an admin tool PreferredReplicaLeaderElectionCommand that you
can run.
Thanks,
Jun
On Thu, Apr 25, 2013 at 12:49 AM, Eureka wrote:
> Hi All,
>
> Here is my test scenario.
>
> There are two broker(A,B) and make one topic which has two partition.
>
> and then, A is leader of partit
Hmm, then it's weird. Could you try the latest code in 0.8? If the problem
persists, could you file a jira and attach the broker log?
Thanks,
Jun
On Wed, Apr 24, 2013 at 11:00 PM, Yin Yin wrote:
> With the option --unavailable-partitions --topic topic1, kafka-list-topic
> doesn't show anythin
Hi All,
Here is my test scenario.
There are two broker(A,B) and make one topic which has two partition.
and then, A is leader of partition #0 and B is leader of partition #1.
Producer and consumer work well.
If, B broker is down, A become leader of partition #0 and #1.
That is good. and work
15 matches
Mail list logo
