Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

Congrats and great job, everyone! Thanks Rajini for driving the release! -James Sent from my iPhone > On Jul 30, 2018, at 3:25 AM, Rajini Sivaram wrote: > > The Apache Kafka community is pleased to announce the release for > > Apache Kafka 2.0.0. > > > > > > This is a major release and

Re: RocksDB error with KStream

Hello Vishnu, Maybe this is the root cause of your issue? https://github.com/docker-flink/docker-flink/issues/14 Guozhang On Mon, Jul 30, 2018 at 8:44 AM, Vishnu Viswanath < vishnu.viswanat...@gmail.com> wrote: > Hi All, > > While running Kafka streams application with a "aggregate" function

Re: Kafka stream application load balancing

Hello Siva, To better understand your situation, I'd need to ask a few more questions: 1) What triggers your REBALANCING event? 2) Does your application contain any states? If yes, how are they configured (persistent or in-memory, is logging enabled, etc)? 3) What is your commit interval

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

Thanks to everyone who contributed to the release (including testing and bug reports)! And thank you Rajini for managing the release. Ismael On Mon, 30 Jul 2018, 03:25 Rajini Sivaram, wrote: > The Apache Kafka community is pleased to announce the release for > > Apache Kafka 2.0.0. > > > > > >

RocksDB error with KStream

Hi All, While running Kafka streams application with a "aggregate" function in it. Running via docker (alpine linux). I am getting *"*java.lang.UnsatisfiedLinkError: /tmp/librocksdbjni20844899025353663*88.so: libstdc++.so.6: cannot open shared object file: No such file or directory". *similar to

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

Great news! Thanks for driving the release Rajini. Guozhang On Mon, Jul 30, 2018 at 8:33 AM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Such a good news on a Monday morning ... > > Thank you Rajini for driving the release! > > --Vahid > > > > > From: Mickael Maison > To:

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

Such a good news on a Monday morning ... Thank you Rajini for driving the release! --Vahid From: Mickael Maison To: Users Cc: dev , annou...@apache.org, kafka-clients Date: 07/30/2018 04:37 AM Subject:Re: [ANNOUNCE] Apache Kafka 2.0.0 Released Great news! Thanks

Re: How set properly infinite retention

Thanks a lot! I will try that! David El lun., 30 jul. 2018 a las 13:26, Kamal Chandraprakash (< kamal.chandraprak...@gmail.com>) escribió: > log.retention.ms = 9223372036854775807 (Long.MAX_VALUE) > > > On Mon, Jul 30, 2018 at 3:04 PM David Espinosa wrote: > > > Hi thanks a lot for the reply. >

Re: Kafka sometime truncate new messages

I didn't test that. All other software is compatible with Kafka 0.11 and we can not change it easily. On Mon, Jul 30, 2018 at 5:07 PM, M. Manna wrote: > The release came out earlier today 2.0.0 - Does this not work for you if > you upgrade to that? > > On 30 July 2018 at 13:02, Soheil

Re: Kafka sometime truncate new messages

The release came out earlier today 2.0.0 - Does this not work for you if you upgrade to that? On 30 July 2018 at 13:02, Soheil Pourbafrani wrote: > In addition, I should say this behavior is for when topics are created > automatically. > > On Mon, Jul 30, 2018 at 2:01 PM, Soheil Pourbafrani >

Re: Kafka sometime truncate new messages

In addition, I should say this behavior is for when topics are created automatically. On Mon, Jul 30, 2018 at 2:01 PM, Soheil Pourbafrani wrote: > I have a 3 node Kafka cluster. Upgrading Kafka version from 0.11.0.2 to > 0.11.0.3, I notice that Kafka sometimes truncate new message's topic. Here

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

Great news! Thanks for running the release On Mon, Jul 30, 2018 at 12:20 PM, Manikumar wrote: > Thanks for driving the release! > > > > On Mon, Jul 30, 2018 at 3:55 PM Rajini Sivaram wrote: > >> The Apache Kafka community is pleased to announce the release for >> >> Apache Kafka 2.0.0. >> >> >>

Re: How set properly infinite retention

log.retention.ms = 9223372036854775807 (Long.MAX_VALUE) On Mon, Jul 30, 2018 at 3:04 PM David Espinosa wrote: > Hi thanks a lot for the reply. > > The thing is that I need compaction to delete some messages (for GDPR > purposes), and for that I need the log cleaner to be enabled (with >

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

Thanks for driving the release! On Mon, Jul 30, 2018 at 3:55 PM Rajini Sivaram wrote: > The Apache Kafka community is pleased to announce the release for > > Apache Kafka 2.0.0. > > > > > > This is a major release and includes significant new features from > > 40 KIPs. It contains fixes and

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

Excellent! Thanks for running the release Rajini! On Mon, 30 Jul 2018 at 11:25 Rajini Sivaram wrote: > The Apache Kafka community is pleased to announce the release for > > Apache Kafka 2.0.0. > > > > > > This is a major release and includes significant new features from > > 40 KIPs. It

[ANNOUNCE] Apache Kafka 2.0.0 Released

The Apache Kafka community is pleased to announce the release for Apache Kafka 2.0.0. This is a major release and includes significant new features from 40 KIPs. It contains fixes and improvements from 246 JIRAs, including a few critical bugs. Here is a summary of some notable changes: **

Re: How set properly infinite retention

Hi thanks a lot for the reply. The thing is that I need compaction to delete some messages (for GDPR purposes), and for that I need the log cleaner to be enabled (with policy=compact). David El lun., 30 jul. 2018 a las 11:27, M. Manna () escribió: > I believe you can simply disable log

Kafka sometime truncate new messages

I have a 3 node Kafka cluster. Upgrading Kafka version from 0.11.0.2 to 0.11.0.3, I notice that Kafka sometimes truncate new message's topic. Here is the log: [2018-07-30 09:19:39,612] WARN [ReplicaFetcherThread-0-101]: Based on follower's leader epoch, leader replied with an unknown offset in

Re: How set properly infinite retention

I believe you can simply disable log cleaner. On Mon, 30 Jul 2018, 10:07 David Espinosa, wrote: > Hi all, > I would like to set infinite retention for all topics created in the > cluster by default. > I have tried with: > > *log.retention.ms =-1* at *server.properties*

How set properly infinite retention

Hi all, I would like to set infinite retention for all topics created in the cluster by default. I have tried with: *log.retention.ms =-1* at *server.properties* But messages get deleted approx after 10 days. Which configuration at broker level should I use for infinite