We also checked the jconsole for memory graph, it was taking only 80% of
the heap (i can see still 20% remaining).
-SK
On Tue, Sep 29, 2015 at 8:13 PM, Gerrit Jansen van Vuuren <
gerrit...@gmail.com> wrote:
> also check your'e GC, caused by using async without backpressuce, with the
> latest jdk
I keep seeing this error while creating topic :
Error is: replication factor: 3 larger than available brokers: 2
I have 4 kafka nodes, and replication factor of 3.
2 nodes on datacenter 1, 2 on datacenter 2 running kafka 0.8.2.0.
Joe,
Thanks for your help. Updating the server properties with ec2 instance's
hostname fixed it.
-Shri
-Original Message-
From: Joe Lawson [mailto:jlaw...@opensourceconnections.com]
Sent: Saturday, September 26, 2015 9:25 AM
To: users@kafka.apache.org
Subject: Re: Kafka on AWS - issue p
Hi
I heave read Jay Kreps post regarding the number of topics that can be handled
by a broker
(https://www.quora.com/How-many-topics-can-be-created-in-Apache-Kafka), and it
has left me with more questions that I dont see answered anywhere else.
We have a data stream which will be consumed by
Hello Kafka users!
Here is a blog post on how we migrated our 0.7 traffic over to 0.8 at
Knewton. I hope this might be useful for anyone considering doing a cutover.
http://tech.knewton.com/blog/2015/09/how-knewton-cutover-the-core-of-its-infrastructure-from-kafka-0-7-to-kafka-0-8/
also check your'e GC, caused by using async without backpressuce, with the
latest jdk and GC1 I've found that many time's a JVM app can become
unresponsive without throwing a OOM.
running jstat -gcutil 250 would tell you, e.g if S0 or S1 stay at
100.00 then you've got a GC problem, and need to re
Well, its possible that it is a networking issue which is why I asked for
results from a test from a machine that isn¹t on the kafka cluster. And
were all the producers run on the same member of the kafka cluster, or was
it spread out?
Also, for the topic you are testing with, how many partitions
Hi Erik,
I've not tested it on a producer that is not a part of the kafka cluster.
*Producer configuration on all machines:-*
root@x.x.x.x:/a/kafka/config# cat producer.properties | egrep -v '^#|^$'
metadata.broker.list=localhost:9092
producer.type=sync
compression.codec=none
serializer.cl
Hi
Iam using kafka async producer, after publisher 1M+ messages, all my
producer threads get hung and not doing any thing. Following is my thread
dump.
"KafkaMessageWorker-georrlite-2" #70 daemon prio=5 os_prio=0
tid=0x7f85d00cc800 nid=0x56b4 waiting on condition [0x7f859faf9000]
java.l
