Re: Kafka replication error

lf. Ironically, this worked for us! After the >restart, the controller was able to send updateMetadataRequest to node > and >node started syncing with the leader. Took some time to be in-sync but > it >worked. > > Thanks, > Suman > Thanks, > Suman > > On Sun, Dec 9, 2

Re: Kafka replication error

you mentioned: 1. broker disconnection error, normally the case I have ever seen is when some broker is busy and can not response connection quickly to other replicas. 2. partitions under-replicated, normally pint to some broker may have a performance issue. 3. 90% under-replicat

Lots of warning log related with `expected version 10 failed due to nul`

Hi Guys, I found lots of warning log in broker's server.log, any idea you have ? my major concern why `failed due to null` will happen ? can I see it zookeeper not available at that moment ? WARNING log : [2018-07-20 20:47:34,868] WARN Conditional update of path /brokers/topics/HeartBeat/parti

Re: Monitor the state of an event-based choreography

Interested, will put some time learn about opentracing.org. On Thu, Jul 19, 2018 at 9:34 AM, Christopher Smith wrote: > This sounds like a pretty good use case for opentracing.org. There is some > nice integration with Kafka now too. > > --Chris > > On Thu, Jul 19, 2018, 8:26 AM Dan Rosanova >

Re: RecordTooLargeException

​you can configure max.request.size ​ when you create Kafka producer, about the second questions, Where is the key size + value size + header size calculated? you can check ` org.apache.kafka.common.record.AbstractRecords.estimateSizeInBytesUp

Re: RecordTooLargeException

sorry, just saw your email a little late. I am confused with why you said `I cannot increase the max size of messages stored in Kafka` ? can we add some explanation ? On Thu, Jul 5, 2018 at 10:09 AM, Jerry Richardson < jerryrichard...@tutanota.com> wrote: > > What class is this in? What's the m

Re: RecordTooLargeException

You can consider increase `max.request.size` ​a little big (the default value is `1048576`.), after checking Kafka client source code, they count [`key size` + `value size` + `header size` + others] together, so it's possible the calculated size is a little bigger than the default value. please ch

Any idea why zookeeper will run into connection issue.

Hi Guys, Anyone has ever run into the following issue or give me suggestion to do addressing, thanks. 2018-02-07 18:59:59,783 [myid:9] - INFO [NIOServerCxn.Factory:0.0.0.0/ 0.0.0.0:2181:NIOServerCnxn@1040] - Closed socket connection for client / 10.92.74.216:27897 (no session established for cli

Re: Any suggestion about Kafka/Zookeeper migration.

> On Wed, Jan 3, 2018 at 11:39 PM, Tony Liu wrote: > > > This post here is aimed to ask experience about what did you do migration > > `Kafka/zookeeper` ? :) > > > > > I think the easiest way to migrate kafka is to do a blue/green deploy. > Stand up an ent

Re: Any suggestion about Kafka/Zookeeper migration.

, Jan 3, 2018 at 8:39 PM, Tony Liu wrote: > Hi All, > > This post here is aimed to ask experience about what did you do migration > `Kafka/zookeeper` ? :) > > All of Kafka/zookeeper are running on AWS, because of some reason, we have > to replace all the existed server (yo

Any suggestion about Kafka/Zookeeper migration.

Hi All, This post here is aimed to ask experience about what did you do migration `Kafka/zookeeper` ? :) All of Kafka/zookeeper are running on AWS, because of some reason, we have to replace all the existed server (you can simply think we will terminate the old server and create new server to re

Kafka topic 's timeindex size is zero.

Hi Guys, I found one of topic's time index size is zero, we are using kafka version 0.10.1.1. is there anyone have any idea why the zero time index will be happened ? thanks. the following is the data snippet: -rw-r--r-- 1 root root0 May 4 05:36 /kafka/data/thl_raw-1/000114296521.t

Re: broker disconnected from cluster

hi, you are hitting this issue , https://issues.apache.org/jira/browse/KAFKA-4477 On Wed, Dec 28, 2016 at 3:43 PM, Alessandro De Maria < alessandro.dema...@gmail.com> wrote: > Hello, > > I would like to get some help/advise on some issues I am having with my > kafka cluster. > > I am running kaf

Re: One Kafka Broker Went Rogue

​Hi, I just found a reported issue, https://issues.apache.org/jira/browse/KAFKA-4477, hopefully, it's useful for you.​ On Thu, Dec 29, 2016 at 12:08 PM, Tony Liu wrote: > Hi Thomas or Anyone, > > I also encountered the same issue like you reported, the only workaround > i

Re: One Kafka Broker Went Rogue

Hi Thomas or Anyone, I also encountered the same issue like you reported, the only workaround is to restart that broken node, but I did not find root cause how to solve it right now, so I wonder do you have some progress how to solve that issue right now? i.e, at the beginning, I thought this iss

Kafka offset monitoring sounds not support `kafka 0.10.1.0`.

Hi, I am trying to use KafkaOffsetMonitor to monitor kakfa consumer Lag, but I can not see any consumer offset information. so I doubt there may be `KafkaOffsetMonitor` not support `kafka 0.10.1.0`, is anyone running into the issue I am encounter

Re: WARN [ReplicaFetcherThread-1-1011], Error in fetch kafka.server.ReplicaFetcherThread$FetchRequest@5dad549c

Mon, Dec 19, 2016 at 4:33 PM, Tony Liu wrote: > ​Hi Experts, > > is there anyone run into this connection error ? > > [2016-12-17 20:13:32,728] WARN [ReplicaFetcherThread-1-1011], Error in fetch > kafka.server.ReplicaFetcherThread$FetchRequest@5dad549c > (kafka.server

WARN [ReplicaFetcherThread-1-1011], Error in fetch kafka.server.ReplicaFetcherThread$FetchRequest@5dad549c

​Hi Experts, is there anyone run into this connection error ? [2016-12-17 20:13:32,728] WARN [ReplicaFetcherThread-1-1011], Error in fetch kafka.server.ReplicaFetcherThread$FetchRequest@5dad549c (kafka.server.ReplicaFetcherThread)java.io.IOException: Connection to 10.137.126.113:9092 (id: 1011 r

Re: Timeout publishing message to Kafka cluster.

it too small (137M for each log file) ? I still guess this issue is mostly caused by my `server.properties`, but just no idea which part is wrong. Thanks. On Sun, Dec 18, 2016 at 5:35 PM, Tony Liu wrote: > ​Post the configuration here for help: > > [root@2494f8e6fb37 co

Re: Timeout publishing message to Kafka cluster.

ime.ms=2000 zookeeper.connect=10.105.212.11:2181,10.105.211.109:2181,10.105.210.103:2181 jvm.performance.opts=-javaagent:/opt/jolokia/jolokia-jvm-1.3.5-agent.jar=host= port=9092 advertised.host.name=10.105.210.24 advertised.port=9092​ On Sun, Dec 18, 2016 at 5:35 PM, Tony Liu wrote: > when that error happene

Re: Timeout publishing message to Kafka cluster.

4,1005)* *(1002)* *true* *true* *​After start:* 3 *​ ​1002* <http://fjord-staging2-kafka-manager.infradev.zuora.com:9000/clusters/fjord-staging2/brokers/1002> *(1002,1004,1005)* *(1002​, 1004, 1005​)* *true* *true* ​ On Sun, Dec 18, 2016 at 5:29 PM, Tony Liu wrote: > Hi, > >

Timeout publishing message to Kafka cluster.

Hi, Recently, we ran into the `batch expired` error in several days, may be 3 or 5 days, there is not fixed frequency. *A,* the error is: Exception Class : org.apache.kafka.common.errors.TimeoutException Error Message : Batch Expired *B*: server.log from kafka : [2016-12-18 20:45:32,371] INFO