any help ?
On Mon, Jan 19, 2015 at 11:43 AM, Tousif tousif.pa...@gmail.com wrote:
Here are the logs from broker id 0 and 1 and it was captured when broker
1 went down.
http://paste.ubuntu.com/9782553/
http://paste.ubuntu.com/9782554/
i'm using netty in storm and here are the configs
Those errors are expected - if broker 10.0.0.11 went down, it will
reset the connection and the other broker will close the socket.
However, it looks like 10.0.0.11 crashes every two minutes?
Do you have the logs from 10.0.0.11?
On Thu, Jan 15, 2015 at 9:51 PM, Tousif tousif.pa...@gmail.com
Tousif,
I meant to say if kafka broker is going down often its better to
analyze whats the root of cause of the crash. Using supervisord
to monitor kafka broker is fine, sorry about the confusion.
-Harsha
On Fri, Jan 16, 2015, at 11:25 AM, Gwen Shapira wrote:
Those errors
i'm using kafka 2.9.2-0.8.1.1 and zookeeper 3.4.6.
i noticed that only one broker is going down.
My message size is less thn 3 kb and KAFKA_HEAP_OPTS=-Xmx512M
and KAFKA_JVM_PERFORMANCE_OPTS=-server -XX:+UseCompressedOops
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled
Tousif,
Which version of kafka and zookeeper are you using and whats your
message size and jvm size that you allocated for kafka brokers.
There is only 1 zookeeper node , if its a production cluster I recommend
you to have quorum of zookeeper nodes. Both kafka storm are heavy
users
i see this error
ERROR [ReplicaFetcherThread-0-1], Error for partition
[realtimestreaming,1] to broker 1:class
kafka.common.NotLeaderForPartitionException
(kafka.server.ReplicaFetcherThread)
[2015-01-15 10:00:04,348] INFO [ReplicaFetcherManager on broker 0]
Removed fetcher for partitions
Tousif,
Do you see any other errors in server.log
-Harsha
On Wed, Jan 14, 2015, at 01:51 AM, Tousif wrote:
Hello,
I have configured kafka nodes to run via supervisord and see following
exceptions
and eventually brokers going out of memory. i have given enough memory
and
process 1
Hello Chia-Chun Shih,
There are multiple issues,
First thing is i don't see out of memory error every time and OOM happens
after supervisord keep retrying to start kafka.
It goes down when it tries to add partition fetcher
it starts with
*conflict in /controller data:
Thanks harsha for quick response.
I don't see any other error. I used to see replica fetcher error but seems
to be disappeared after setting replica fetcher threads to 2 as I have 2
partitions. Some times I see zookeeper session expiration.
On Jan 14, 2015 8:02 PM, Harsha ka...@harsha.io wrote:
Hello,
I have configured kafka nodes to run via supervisord and see following
exceptions
and eventually brokers going out of memory. i have given enough memory and
process 1 event/second. kafka goes down every day
i'm wondering what configurastion is missing or need to be added
Here are my
10 matches
Mail list logo
