Re: Clients may fetch incomplete set of topic partitions during cluster startup

Anyone any update on my below query? On Thu, 28 May 2020, 15:45 Debraj Manna, wrote: > Hi > > Is the below issue fixed in latest Kafka 2.5? > > https://issues.apache.org/jira/browse/KAFKA-8480 > > I am seeing this issue still open. So just confirming before upgrading > Kafka to the latest. > > T

Kafka _Querys

Hi Kafka team, As of now we have successfully implemented kafka for our environment, We stuck up with below questions so please provide assistance and help for below questions. 1) What are the distinct consumer group names currently consuming messages from the same topic 2) Total number of messa

Re: Repeated UnknownProducerIdException

The issue with producer metadata often occurs for repartition topics. Those are purged actively by Kafka Streams. It might help to increase the segment size and maybe `segment.ms` config for those topics to preserve a large history (the active segment is not purged). By default, Kafka Streams crea

a few URP causes high latencies to producers and consumers

Hi, We have noticed that where a URPs in the cluster causes increase in producer and consumer latencies. The cause of the URP was either one of the broker went down or Kafka rebalancer was running. Is it the expected scenario ? Thanks, Nitin

Re: NEED HELP : OutOfMemoryError: Java heap space error while starting KafkaStream with a simple topology

Thanks for the update Pushkar! I'd have to say it is indeed very very misleading error message and we should fix it asap. Will follow-up on the ticket. Guozhang On Thu, May 28, 2020 at 9:17 AM John Roesler wrote: > Woah, that's a nasty bug. I've just pinged the Jira ticket. Please feel > free t

Re: NEED HELP : OutOfMemoryError: Java heap space error while starting KafkaStream with a simple topology

Woah, that's a nasty bug. I've just pinged the Jira ticket. Please feel free to do the same. Thanks, -John On Thu, May 28, 2020, at 02:55, Pushkar Deole wrote: > Thanks for the help Guozhang! > however i realized that the exception and actual problem is totally > different. The problem was the cl

Re: How to manually start ingesting in kafka source connector ?

You could look at https://rmoff.net/2019/08/15/reset-kafka-connect-source-connector-offsets/ and experiment with creating the connector elsewhere to see if you can pre-empt the key value that Kafka Connect will use when writing the offsets, and so do your list 2 - 1 - 3 instead -- Robin Moffatt

Repeated UnknownProducerIdException

Good morning, Since a couple of days ago we suddenly have the issue in our Kafka Steams application that a UnknownProducerException occurs. Digging into this I came across KIP-360. We are using a centrally managed Kafka

Clients may fetch incomplete set of topic partitions during cluster startup

Hi Is the below issue fixed in latest Kafka 2.5? https://issues.apache.org/jira/browse/KAFKA-8480 I am seeing this issue still open. So just confirming before upgrading Kafka to the latest. Thanks,

Re: How to manually start ingesting in kafka source connector ?

Robin Thank you for the reply. Any way to not automatically start after creating connector ? I am trying to find a way to change connector offset as described in below link before starting connector .. https://www.confluent.jp/blog/kafka-connect-deep-dive-jdbc-source-connector/#starting-table-

Re: How to manually start ingesting in kafka source connector ?

When you create the connector, it will start. -- Robin Moffatt | Senior Developer Advocate | ro...@confluent.io | @rmoff On Thu, 28 May 2020 at 04:12, Yu Watanabe wrote: > Dear community . > > I would like to ask question related to source connector in kafka > connect (2.4.0) . > > Is there

Re: can kafka state stores be used as a application level cache by application to modify it from outside the stream topology?

Matthias, I realized that the exception and actual problem is totally different. The problem was the client was not set with SSL truststore while server is SSLenabled. I also found this open bug on kafka https://issues.apache.org/jira/browse/KAFKA-4493 After setting the SSL properties on stream, I

Re: NEED HELP : OutOfMemoryError: Java heap space error while starting KafkaStream with a simple topology

Thanks for the help Guozhang! however i realized that the exception and actual problem is totally different. The problem was the client was not set with SSL truststore while server is SSLenabled. I also found this open bug on kafka https://issues.apache.org/jira/browse/KAFKA-4493 After setting the