Do you see any WARN for the offset request on the broker?
Thanks,
Jun
On Fri, Oct 17, 2014 at 4:44 AM, Magnus Vojbacke
magnus.vojba...@digitalroute.com wrote:
Yes, I used TopicMetaDataRequest to determine the lead broker for the
partition.
I’ve also compared the broker selected by my code
Yes, your understanding is correct. For a long time, the implementation is
buggy though. We fixed it (KAFKA-1430) in trunk a few months ago and the
fix will be included in the 0.8.2 release.
Thanks,
Jun
On Fri, Oct 17, 2014 at 5:44 AM, Magnus Vojbacke
magnus.vojba...@digitalroute.com wrote:
Metrics-core's default jmx name has quotes. To add the tags, we are
specifying the jmx name explicitly. So, it's possible to get rid of the
quotes.
Thanks,
Jun
On Fri, Oct 17, 2014 at 1:52 PM, VERMEERBERGEN Alexandre
alexandre.vermeerber...@3ds.com wrote:
+1 as well for getting rid of the
Haven't seen this one before. Are you manually committing offsets yourself?
Thanks,
Jun
On Fri, Oct 17, 2014 at 11:10 PM, Yu Yang yuyan...@gmail.com wrote:
Hi,
I have a Kafka 0.8.1 cluster. I used the ConsumerOffsetChecker tool to
check the lag of consumer groups. I found that for some
Did you set the replication factor to be more than 1?
Thanks,
Jun
On Sat, Oct 18, 2014 at 2:32 AM, Yu Yang yuyan...@gmail.com wrote:
Hi all,
We have a kafka 0.8.1 cluster. We implemented a consumers for the topics on
the Kafka 0.8 cluster using high-level consumer api. We observed that if
Perhaps you can ask the storm mailing list about the storm-postgresql code?
Thanks,
Jun
On Sat, Oct 18, 2014 at 10:32 AM, Sa Li sal...@gmail.com wrote:
Hi, all
I've just made a 3-node kafka cluster (9 brokers, 3 for each node), the
performance test is OK. Now I am using tridentKafkaSpout,
You need to pass in the topic name as well. It's better to
use AdminUtils.createTopic() to create the topic.
Thanks,
Jun
On Fri, Oct 17, 2014 at 4:43 PM, Pradeep Badiger pradeepbadi...@fico.com
wrote:
Hi,
We have issues in getting the topic metadata created when we use the
Yes, our service do handle the consumer group offsets by itself. It seems
to be that the negative value happens because all replicas of a partition
are dead, and Kafka create a new replica for the partition, and the high
level consumer is not aware of the Kafka server side change.
On Sun, Oct 19,
Thanks, Jun! Yes, I set the topic replication factor to 3.
On Sun, Oct 19, 2014 at 8:09 PM, Jun Rao jun...@gmail.com wrote:
Did you set the replication factor to be more than 1?
Thanks,
Jun
On Sat, Oct 18, 2014 at 2:32 AM, Yu Yang yuyan...@gmail.com wrote:
Hi all,
We have a kafka
I'm pretty sure that the quotes are a side effect of using Metrics 2.x. When
part of an Mbean name has certain characters, then that part will be wrapped in
quotes. This is fixed in Metrics 3.
--
Daniel
On 18/10/2014, at 10:03 am, Rajasekar Elango rela...@salesforce.com wrote:
+1 on
10 matches
Mail list logo