I have increased the partition for parallelism but my concern is , if
message are present in partition then why consumer thread are blocked at
below condition.
*KafkaConsumer-24" prio=10 tid=0x7f6da5726800 nid=0x3c8a waiting on
condition [0x7f6d4f8f7000] java.lang.Thread.State: WAITING (p
I have one more doubt.
The Kafka cluster retains all published messages—whether or not they have
been consumed—for a configurable period of time. For example if the log
retention is set to two days, *then for the two days after a message is
published it is available for consumption, after which it
There can be different reasons, Can you check the kafka consumer log and
see if there is any "conflict in".
And can u check weather, the console consumer is working fine or not.
Arjun Narasimha Kota
On Tuesday 15 April 2014 12:34 PM, ankit tyagi wrote:
I have increased the partition for parall
We are also using straight Java. I am not sure if Spring/Camel supports
past 0.8 beta.
On Mon, Apr 14, 2014 at 9:39 PM, Otis Gospodnetic <
otis.gospodne...@gmail.com> wrote:
> In our case it's straight Java.
>
> Otis
> --
> Performance Monitoring * Log Analytics * Search Analytics
> Solr & Elas
Yes. I checked that I was fully replicated. All topic/partitions leaders were
on broker #2.
Using the "--under-replicated-partitions" option in the listtopic command
returned no results.
Bob Bello
Middleware Applications Administrator
Direct: 720-514-6605
email: bob.be...@dish.com
-Origin
I have seen or heard first hand of many (almost all) of these "in the wild"
being used
https://cwiki.apache.org/confluence/display/KAFKA/Clients#Clients-For0.8.xin
production somewhere.
/***
Joe Stein
Founder, Principal Consultant
Big Data Open Source Sec
Thanks Magnus, very cool I added it to the client page
https://cwiki.apache.org/confluence/display/KAFKA/Clients
cheers!
/***
Joe Stein
Founder, Principal Consultant
Big Data Open Source Security LLC
http://www.stealth.ly
Twitter: @allthingshadoop
I performed another test. I build a single Kafka 0.8.1 Broker with a single ZK
instance. Brand new, no topics.
Upon start up of the Kafka broker, the zookeeper /admin node only contains
"/admin/delete_topics".
Even without creating a topic, I run a perfered replica election, and it's
successfu
https://issues.apache.org/jira/browse/KAFKA-1365
:)
-Original Message-
From: Bello, Bob [mailto:bob.be...@dish.com]
Sent: Tuesday, April 15, 2014 10:00 AM
To: users@kafka.apache.org
Cc: Bello, Bob
Subject: RE: Kafka upgrade 0.8.0 to 0.8.1 - kafka-preferred-replica-election
failure
I pe
Ok, we take a look and patch it in 0.8.1.1.
Thanks,
Jun
On Tue, Apr 15, 2014 at 9:00 AM, Bello, Bob wrote:
> I performed another test. I build a single Kafka 0.8.1 Broker with a
> single ZK instance. Brand new, no topics.
>
> Upon start up of the Kafka broker, the zookeeper /admin node only c
Ch3eck, check. 5 by 5!
> -Original Message-
> From: Jun Rao [mailto:jun...@gmail.com]
> Sent: Tuesday, April 15, 2014 10:06 PM
> To: users@kafka.apache.org
> Subject: Re: Kafka upgrade 0.8.0 to 0.8.1 - kafka-preferred-replica-election
> failure
>
> Ok, we take a look and patch it in 0.8.
12 matches
Mail list logo