have
around 1600.
Paul Lung
On 6/24/14, 10:31 PM, Prakash Gowri Shankor prakash.shan...@gmail.com
wrote:
How many files does each broker itself have open ? You can find this
from
'ls -l /proc/processid/fd'
On Tue, Jun 24, 2014 at 10:18 PM, Lung, Paul pl...@ebay.com wrote
How many files does each broker itself have open ? You can find this from
'ls -l /proc/processid/fd'
On Tue, Jun 24, 2014 at 10:18 PM, Lung, Paul pl...@ebay.com wrote:
Hi All,
I just upgraded my cluster from 0.8.1 to 0.8.1.1. I’m seeing the following
error messages on the same 3 brokers
Hi,
I've looked at the documentation for mirrormaker. It doesnt appear that
there is a notion of HA ( high availability ) for the mirrormaker tool
itself. Ideally, I would like to have some topics flowing to another
datacenter with a 2 node mirrormaker in between, where one mirrormaker is
always
On Wed, Jun 18, 2014 at 1:10 PM, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Hi,
I've looked at the documentation for mirrormaker. It doesnt appear that
there is a notion of HA ( high availability ) for the mirrormaker tool
itself. Ideally, I would like to have some topics
Hi,
I used the add partition functionality in create-topics to alter a previous
topic and increase the partitions. I noticed that after the new partitions
were added, they dont receive data immediately from the producer unless a
new producer is started up or the old producer is restarted.
Here is
without seeing LeaderNotAvailableExceptions (you may need to give
Kafka some time to re-elect the remaining, second broker as the new
leader for the first broker's partitions though).
Best,
Michael
On 06/12/2014 08:43 PM, Prakash Gowri Shankor wrote:
So if we go back to the 2 broker case
should see ZK session expirations (hence the
initial/transient exceptions, which in this case are expected and ok),
followed by new ZK sessions being established.
So this case is (should?) be very different from your case number 1.
--Michael
On 11.06.2014, at 23:13, Prakash Gowri Shankor
at 11:04 AM, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Hi,
I am running a cluster with a single broker, the performance producer
script and 3 consumers.
On a fresh start of the cluster , the producer throws this exception.
I was able to run this cluster successfully
values.
Guozhang
On Tue, Jun 10, 2014 at 9:54 AM, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Can you please tell me how to set this property ?
topic.metadata.refresh.interval.ms
Is a value of 100 low enough to solve this issue ?
Im guessing I can set it to 100 and restart
/2014 07:49 PM, Prakash Gowri Shankor wrote:
yes,
here are the steps:
Create topic as : ./kafka-topics.sh --topic test2 --create
--partitions 3
--zookeeper localhost:2181 --replication-factor 1
1) Start cluster with 2 brokers, 3 consumers.
2) Dont start any producer
3) Shutdown
, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Thank you Guozhang.
I've specified how i set and use the property in my previous mail. Can you
tell me if that is fine ?
I also noticed that the kafka-console-producer.sh takes a custom
property(key-value) on the command line. Would
Hi,
I am running a cluster with a single broker, the performance producer
script and 3 consumers.
On a fresh start of the cluster , the producer throws this exception.
I was able to run this cluster successfully on the same topic ( test2 )
successfully the first time.
The solution( from
-with-zookeeper-3
On Tue, Jun 10, 2014 at 12:47 PM, Guozhang Wang wangg...@gmail.com wrote:
Hello Prakash,
Is this exception transient or persistent on broker startup?
Guozhang
On Tue, Jun 10, 2014 at 11:04 AM, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Hi,
I am
to disable delete-topic support
on the broker.
Joel
On Tue, Jun 10, 2014 at 01:07:45PM -0700, Prakash Gowri Shankor wrote:
From the moment it starts occuring, it is persistent. Restarts dont seem
to
make it go away. The only thing that makes it go away is following the
steps listed
Hi,
This is with 0.8.1.1 and I ran the command line console consumer.
I have one broker, one producer and several consumers. I have one topic,
many partitions m, many consumers n, m=n , one consumer group defined for
all the consumers
From using Kafka Monitor, I see that each partition is
PM, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Hi,
This is with 0.8.1.1 and I ran the command line console consumer.
I have one broker, one producer and several consumers. I have one topic,
many partitions m, many consumers n, m=n , one consumer group defined for
all
Hi,
Is the perf module bundled with 0.8.1.1 ?
When i try to run kafka-producer-perf-test.sh I see
*Error: Could not find or load main class kafka.perf.ProducerPerformance*
I then tried to do a ./gradlew perf which resulted in:
*Task 'perf' not found in root project 'kafka-0.8.1.1-src'.*
Please
PM, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Hi,
This is with 0.8.1.1 and I ran the command line console consumer.
I have one broker, one producer and several consumers. I have one
topic,
many partitions m, many consumers n, m=n , one consumer group defined
topic.metadata.refresh.interval.ms
should help because the stickiness only persists until a metadata refresh.
Guozhang
On Mon, Jun 9, 2014 at 4:54 PM, Prakash Gowri Shankor
prakash.shan...@gmail.com wrote:
Is there a way to modify this duration ? This is not adhering to the
random behavior
Thanks Jun.
That worked. I can run the perf producer now.
On Mon, Jun 9, 2014 at 8:51 PM, Jun Rao jun...@gmail.com wrote:
Was that a source download? Then you need to run ./gradlew jar first.
Thanks,
Jun
On Mon, Jun 9, 2014 at 4:57 PM, Prakash Gowri Shankor
prakash.shan...@gmail.com
Hi,
I am running Kafka 0.8.1.1 with one Zookeeper and one broker. I created a
partition 'test2' as below:
/kafka-topics.sh --create --zookeeper localhost:2181 --replication-factor 1
--partitions 3 --topic test2
I noticed this exception in the state-change.log. Why is this occuring ?
Should I be
21 matches
Mail list logo
