Hi Jay, Hi Guozhang,
Thanks for your response. I was suspecting something like that but did not
found the documentation entry that explain that.
Thanks again!
2014-07-17 23:41 GMT+02:00 Jay Kreps :
> This makes sense if you think about it. If you want to start "now" you
> don't want the last m
First things first. I friggin' think Kafka rocks. It's a system that have given
me a lot of joy, and I've spent a lot of fun hours (and sometimes not so fun)
looking at consumer lag metrics. I'd like to give back, beyond spreading the
gospel about it architecturally and operationally.
My only
It might appear that the data is not balanced, but it could be as a result
of the imbalanced leaders setting.
Does this mean that we should set "auto.leader.rebalance.enable" to true?
Any other configuration we need to change as well? As I mentioned before,
we use pretty much use the default set
Connie,
After we freed up the
cluster disk space and adjusted the broker data retention policy, we
noticed that the cluster partition was not balanced based on topic describe
script came from Kafka 0.8.1.1 distribution.
When you say the cluster was not balanced, did you mean the leaders or the
da
Just a followup for completeness sake -- for testing purpose I have setup
fluentd and fluent-plugin-kafka plugin. Now my android APP now does POST to
this fluent instance which forwards the message on to Kafka and then
subsequent items in the processing pipeline.
Cheers,
-Subodh
On Wed, Jul 16,
Correct, I don't see any exceptions when i turn off security. Consumer is
able to consume the message.
I still see warning for topic property.
[2014-07-17 18:04:38,360] WARN Property topic is not valid
(kafka.utils.VerifiableProperties)
On Thu, Jul 17, 2014 at 5:49 PM, Rajasekar Elango
wrot
Can you try with turning off security to check if this error happens only
on secure mode?
Thanks,
Raja.
On Thu, Jul 17, 2014 at 3:51 PM, Pramod Deshmukh wrote:
> Thanks Raja, it was helpful
>
> Now I am able to start zookeeper and broker in secure mode ready for SSL
> handshake. I get *java.
This makes sense if you think about it. If you want to start "now" you
don't want the last message in the log, which could be seconds,
minutes, days, or weeks old, you actually want the next message that
comes in.
-Jay
On Thu, Jul 17, 2014 at 10:00 AM, Guozhang Wang wrote:
> Hello Tanguy,
>
> Wi
Hey All,
Wow, glad that there is so much interest.
As people mentioned a good place to get started to kind of learn the
basics of the code base are the newbie and newbie++ JIRAs:
http://bit.ly/1jR3lyJ
If you take on any of these and get stuck we are very happy to help
you get unstuck. Feel free
Thanks Raja, it was helpful
Now I am able to start zookeeper and broker in secure mode ready for SSL
handshake. I get *java.lang.OutOfMemoryError: Java heap space* on producer.
I using the default configuration and keystore. Is there anything missing
*Start broker:*
*bin/kafka-server-start.sh c
Hi All,
Our Kafka cluster ran out of disk space yesterday. After we freed up the
cluster disk space and adjusted the broker data retention policy, we
noticed that the cluster partition was not balanced based on topic describe
script came from Kafka 0.8.1.1 distribution. So, we tried to rebalance
Filed https://issues.apache.org/jira/browse/KAFKA-1546 to track the
improvement. It is also a good ticket for some one to jump on, to learn
more about the replication code base.
Thanks,
Neha
On Mon, Jul 14, 2014 at 7:54 AM, Jun Rao wrote:
> Yes, it is true that if all replicas fall out of isr,
Hi Josh,
What is the Kafka version you are using? And can you describe the steps to
re-produce this issue?
Guozhang
On Thu, Jul 17, 2014 at 9:01 AM, Josh J wrote:
> Hi,
>
> I'm running three kafka brokers. I receive the following when using the
> producer
>
> panic: kafka server: In the middl
Hello Tanguy,
With "latest" the returned offset is actually the "logEndOffset", which is
the offset of the next message that will be appended to the log.
Guozhang
On Thu, Jul 17, 2014 at 5:26 AM, Tanguy tlrx wrote:
> Hi all,
>
> I have a strange behavior with Kafka 0.8.1.1 where consumers do
Hi,
I'm running three kafka brokers. I receive the following when using the
producer
panic: kafka server: In the middle of a leadership election, there is
currently no leader for this partition and hence it is unavailable for
writes.
Though the describe topic shows a leader for each partition.
-- Forwarded message --
From: Tanguy tlrx
Date: 2013-10-10 11:19 GMT+02:00
Subject: Subscribe
To: users@kafka.apache.org
--
-- Tanguy
twitter @tlrx
https://github.com/tlrx
Thanks Jay for bringing this up. A couple things might help -
1. Be diligent in marking newbie/newbie++ labels. I've seen us do pretty
well here.
2. Pair up contributors to committers for a few initial patches to ensure a
smoother ramp up. I've recently done this and have seen it work pretty
well.
Hi all,
I have a strange behavior with Kafka 0.8.1.1 where consumers do not
retrieve the latest messages.
I created a topic called "my-topic" with 8 partitions. My application
creates a SimpleConsumer instance for each topic-partition pair and
executes an OffsetRequest to retrieve the earliest an
Hi all,
I have a strange behavior with Kafka 0.8.1.1 where consumers do not
retrieve the latest messages.
I created a topic called "my-topic" with 8 partitions. My application
creates a SimpleConsumer instance for each topic-partition pair and
executes an OffsetRequest to retrieve the earliest an
19 matches
Mail list logo
