Re: Java 1.8 and TLSv1.3

Hi Andreas, The TLS code has run into changes in behavior across different Java versions, so we only wanted to allow TLS 1.3 in the versions we tested against. TLS 1.3 landed in Java 8 a while after we made the relevant changes for Java 11 and newer. That said, Java 8 support is deprecated and

Re: [ANNOUNCE] Apache Kafka 3.6.0

n, Erik van Oosten, ezio, Farooq Qaiser, > Federico Valeri, flashmouse, Florin Akermann, Gabriel Oliveira, > Gantigmaa Selenge, Gaurav Narula, GeunJae Jeon, Greg Harris, Guozhang > Wang, Hailey Ni, Hao Li, Hector Geraldino, hudeqi, hzh0425, Iblis Lin, > iit2009060, Ismael Juma, Ivan Yu

Re: [kafka-clients] [VOTE] 3.6.0 RC1

Given that this is not a regression and there have been no reports for over a year, I think it's ok for this to land in 3.6.1. Ismael On Sat, Sep 23, 2023 at 9:32 AM Satish Duggana wrote: > Thanks Luke for reporting KRaft issue[1]. > > I am not sure whether it is a release blocker for 3.6.0.

Re: [VOTE] 3.4.0 RC2

Thanks David and Sophie! Ismael On Mon, Feb 6, 2023, 7:22 AM David Arthur wrote: > I'd like to go ahead and close out this vote. There were three binding > votes and one non-binding vote. > > Binding +1 PMC votes: > * David Jacot > * Bill Bejeck > * Mickael Maison > > Non-binding community

Re: Kafka support for TLSv1.3

Hi Deepak, Kafka currently only supports TLS 1.3 with Java 11 or newer. As you said, Kafka 2.6 added support for it, but we recommend using something more recent as there were some fixes after the original release. Ismael On Fri, Dec 2, 2022 at 7:21 AM Deepak Nangia wrote: > Hello All, > > I

Re: [ANNOUNCE] New committer: Deng Ziming

Congratulations Ziming! Ismael On Mon, Oct 10, 2022 at 9:30 AM Jason Gustafson wrote: > Hi All > > The PMC for Apache Kafka has invited Deng Ziming to become a committer, > and we are excited to announce that he has accepted! > > Ziming has been contributing to Kafka for about three years. He

Re: [VOTE] 3.3.0 RC2

+1 provided that the system test results are good. Can you please post them along with the JUnit test results (these seem ok although there are some flakes)? I tested the kraft quick start with the Scala 2.13 binary and ran the tests on the source release. I noticed a non-blocker issue with the

Re: [VOTE] 3.1.1 RC0

I added a comment to that PR. Let's figure out if we need an additional change before doing the next RC. Ismael On Tue, Apr 12, 2022 at 7:47 PM Luke Chen wrote: > Thanks for pointing that out, David. > +1 to include this PR since we've already included the first fix for > KAFKA-13794, and this

Re: [VOTE] 2.8.1 RC1

Josep, This is fixed in 3.0.0, right? Ismael On Tue, Sep 14, 2021 at 11:32 AM Josep Prat wrote: > Hi Chris and David, > > Regarding the API search, this is a known bug in JDK 11 and prior. It can't > correctly generate URLs for projects not using the module system (Kafka) > that link to

Re: high CPU usage after Kafka upgrade

The last message format version was in 0.11. Once you have the flame graph, please file a JIRA with it attached. CPU usage is expected to be lower in the new version, not higher. Ismael On Fri, Feb 26, 2021, 9:59 AM Jhanssen Fávaro wrote: > Not sure if this applies only to this 0.10 version.

Re: [kafka-clients] Re: [VOTE] 2.6.1 RC3

a new RC to pick the > commit [1] that addresses CVE-2020-25649. > > 1: > https://github.com/apache/kafka/commit/101ba2844f92451f633d11fd2ad3813f15d4a4f3 > > So closing this vote, I'll open a new one soon > > On Fri, Dec 18, 2020 at 4:45 AM Ismael Juma wrote: > > >

Re: [ANNOUNCE] Apache Kafka 2.7.0

Chen, Brian Byrne, Bruno Cadonna, Can > Cecen, Cheng Tan, Chia-Ping Tsai, Chris Egerton, Colin Patrick McCabe, > David Arthur, David Jacot, David Mao, Dhruvil Shah, Dima Reznik, Edoardo > Comar, Ego, Evelyn Bayes, feyman2016, Gal Margalit, gnkoshelev, Gokul > Srinivas, Gonzalo Muñoz, Greg Ha

Re: [VOTE] 2.6.1 RC3

Looks like you have your votes Mickael. :) Ismael On Fri, Dec 11, 2020 at 7:23 AM Mickael Maison wrote: > Hello Kafka users, developers and client-developers, > > This is the fourth candidate for release of Apache Kafka 2.6.1. > > Since RC2, the following JIRAs have been fixed: KAFKA-10811,

Re: [ANNOUNCE] New committer: A. Sophie Blee-Goldman

Congratulations Sophie! Ismael On Mon, Oct 19, 2020 at 9:41 AM Matthias J. Sax wrote: > Hi all, > > I am excited to announce that A. Sophie Blee-Goldman has accepted her > invitation to become an Apache Kafka committer. > > Sophie is actively contributing to Kafka since Feb 2019 and has >

Re: [ANNOUNCE] New committer: Chia-Ping Tsai

Congratulations Chia-Ping! Ismael On Mon, Oct 19, 2020 at 10:25 AM Guozhang Wang wrote: > Hello all, > > I'm happy to announce that Chia-Ping Tsai has accepted his invitation to > become an Apache Kafka committer. > > Chia-Ping has been contributing to Kafka since March 2018 and has made 74 >

Re: [ANNOUNCE] New committer: David Jacot

Congratulations David! Ismael On Fri, Oct 16, 2020 at 9:01 AM Gwen Shapira wrote: > The PMC for Apache Kafka has invited David Jacot as a committer, and > we are excited to say that he accepted! > > David Jacot has been contributing to Apache Kafka since July 2015 (!) > and has been very

Re: OpenJDK support statement for Kafka 2.5.0

Does the following help? https://kafka.apache.org/documentation/#java Ismael On Thu, Oct 1, 2020 at 6:17 PM Johnson, Brad wrote: > I am looking for some official statement that OpenJDK is supported for > Kafka, in particular 2.5.0. > I know that it works, but I need to “prove” it to a

Re: Kafka compatibility with ZK

Great, thanks for the update Manoj and and Andrey! I recommend the simple upgrade from 2.5.0 to 2.5.1 to get the fix for https://issues.apache.org/jira/browse/KAFKA-9835. Ismael On Thu, Sep 3, 2020 at 9:01 PM wrote: > We also upgraded kafka 2.2.1 to kafka 2.5.0 and kept same zookeeper . no >

Re: Kafka compatibility with ZK

s. Hope it helps. Ismael > > Thank you! > Marina > > Sent with [ProtonMail](https://protonmail.com) Secure Email. > > ‐‐‐ Original Message ‐‐‐ > On Tuesday, August 11, 2020 6:02 PM, Ismael Juma > wrote: > > > Note that 2.5.1 has now been released. >

Re: [ANNOUNCE] Apache Kafka 2.5.1

oyang > Chen, Bruno Cadonna, Chia-Ping Tsai, Chris Egerton, David > Arthur, David Jacot, Dezhi “Andy” Fang, Dima Reznik, Ego, > Evelyn Bayes, Ewen Cheslack-Postava, Greg Harris, Guozhang > Wang, Ismael Juma, Jason Gustafson, Jeff Widman, Jeremy > Custenborder, jiameixie, John Roe

Re: Kafka compatibility with ZK

Note that 2.5.1 has now been released. Ismael On Sun, Aug 2, 2020 at 11:13 AM Ismael Juma wrote: > Hi Marina, > > If you upgrade to ZK 3.5.x, I highly recommend going with 3.5.8. It has a > few critical fixes when compared to 3.5.6. Also, Kafka 2.5.1 should be out > in a f

Re: compatible kafka version to use when using with logstash 7.5.1-1

Note that 2.5.1 has just been released. Ismael On Tue, Aug 11, 2020 at 7:54 AM Ismael Juma wrote: > Yeah, I'd recommend upgrading to 2.5.1 (will be announced very soon) or > 2.6.0. > > Ismael > > On Tue, Aug 11, 2020, 7:43 AM REYMOND Jean-max (BPCE-IT - SYNCHRONE >

Re: compatible kafka version to use when using with logstash 7.5.1-1

Yeah, I'd recommend upgrading to 2.5.1 (will be announced very soon) or 2.6.0. Ismael On Tue, Aug 11, 2020, 7:43 AM REYMOND Jean-max (BPCE-IT - SYNCHRONE TECHNOLOGIES) wrote: > Hi, > May be this issue : https://issues.apache.org/jira/browse/KAFKA-9669 ? > > -Message d'origine- > De :

Re: [ANNOUNCE] Apache Kafka 2.6.0

rles Feduke, Chia-Ping Tsai, Chris > Egerton, Colin Patrick McCabe, Daniel, Daniel Beskin, David Arthur, David > Jacot, David Mao, dengziming, Dezhi “Andy” Fang, Dima Reznik, Dominic > Evans, Ego, Eric Bolinger, Evelyn Bayes, Ewen Cheslack-Postava, fantayeneh, > feyman2016, Florian Hussonn

Re: [VOTE] 2.6.0 RC2

+1 (binding), verified signatures, ran the tests on the source archive with Scala 2.13 and Java 14 and verified the quickstart with the source archive and Scala 2.13 binary archive. Thanks, Ismael On Tue, Jul 28, 2020, 2:52 PM Randall Hauch wrote: > Hello Kafka users, developers and

Re: Kafka compatibility with ZK

Hi Andrey, ZK 3.4.6 probably works, but we haven't tested with that version for a while. Generally, we recommend upgrading to the latest bug fix release of ZooKeeper (3.4.13, 3.5.8) as they tend to include important fixes. However, you can do that in your own time, independently of the Kafka

Re: Kafka compatibility with ZK

Hi Marina, If you upgrade to ZK 3.5.x, I highly recommend going with 3.5.8. It has a few critical fixes when compared to 3.5.6. Also, Kafka 2.5.1 should be out in a few days and I'd recommend that over 2.4.1. Ismael On Sun, Aug 2, 2020 at 10:04 AM Marina Popova wrote: > > Actually, I'm very

Re: [VOTE] 2.5.1 RC0

+1 (binding), verified signatures, ran the tests on the source archive with Scala 2.13 and Java 11 and verified the quickstart with the source archive and Scala 2.13 binary archive. Ismael On Thu, Jul 23, 2020 at 7:39 PM John Roesler wrote: > Hello Kafka users, developers and

Re: CVEs for the dependency software guava and rocksdbjni of Kafka

I don't think Guava is a dependency in master or 2.5.0. Ismael On Tue, Apr 14, 2020 at 11:08 AM Guozhang Wang wrote: > Thanks for the reported issue. > > For guava I think we should just upgrade version to 24.1.1 or newer to > resolve 10237. > > For rocksdbjni, I saw that at the moment even

Re: Consumer loses partition offset and resets post 2.4.1 version upgrade

Hi Nitay, What version were you running before the upgrade? And was this a broker upgrade? I would suggest filing a JIRA ticket, including as much information as possible and ideally consumer and broker logs from the period where the issue happened. Ismael On Sun, Apr 5, 2020, 10:13 AM Nitay

Re: Reg : Slowness in Kafka

Hi James, A JIRA would be helpful. It looks like something we should fix. Ismael On Mon, Mar 30, 2020 at 8:17 PM James Olsen wrote: > Christophe, > > See "Problems when Consuming from multiple Partitions” in the list > archive. I’ll forward you the full conversation privately. It includes >

Re: [VOTE] 2.5.0 RC2

Hi Boyang, Is this a regression? Ismael On Fri, Mar 20, 2020, 5:43 PM Boyang Chen wrote: > Hey David, > > I would like to raise https://issues.apache.org/jira/browse/KAFKA-9701 as > a > 2.5 blocker. The impact of this bug is that it could throw fatal exception > and kill a stream thread on

Re: Subject: [VOTE] 2.4.1 RC0

Is this a blocker given that it's been like this for months and no-one noticed? 2.4.1 seemingly has all the votes needed for the release. Why not go ahead with it. When KAFKA-9675 is merged, it can be included in the next release. Ismael On Mon, Mar 9, 2020 at 8:43 PM Bill Bejeck wrote: >

Re: Default values for max.request.size and message.max.bytes seem wrong

This was fixed recently: https://github.com/apache/kafka/commit/bd5a1c4d368b9e91398e48400965d30d3045062e Ismael On Tue, Mar 3, 2020 at 11:34 AM Michael Rubin wrote: > (I am re-asking my SO question: >

Re: High CPU in 2.2.0 kafka cluster

be related to our problems but it seems like it's projected > to be included in 2.5.0. > > Thanks, > Brandon > > ____ > From: Ismael Juma > Sent: Monday, February 3, 2020 7:31 AM > To: Kafka Users > Subject: Re: High CPU in 2.2.0 kafka

Re: High CPU in 2.2.0 kafka cluster

Hi Brandon, Are you still seeing this behavior with Apache Kafka 2.4.0? Ismael On Fri, Jan 31, 2020 at 10:51 AM Brandon Barron wrote: > We were running client version 2.3.0 for a while, then bumped to 2.3.1 for > a particular kafka streams bug fix. We saw this issue while both versions > were

Re: Minor version upgrade instructions from 0.11.0.0 to 0.11.0.3

One note is that 0.11.0.3 is pretty old by now and no new releases in that series are planned. I recommend planning an upgrade to the 2.x series whenever possible. Ismael On Mon, Jan 20, 2020 at 12:47 AM Manikumar wrote: > Hi, > > Your approach is correct. For minor version upgrade (0.11.0.0

Re: Kafka send() call, ack, and message writes to the filesystem

To all the in-sync replicas. You can set the minimum number of in-sync replicas via the min.insync.replicas topic/broker config. Ismael On Tue, Jan 14, 2020 at 11:11 AM Anindya Haldar wrote: > I have a question related to the semantics of a producer send and the get > calls on the future

Re: [ANNOUNCE] New Kafka PMC Members: Colin, Vahid and Manikumar

Congratulations Colin, Vahid and Manikumar! Ismael On Tue, Jan 14, 2020 at 9:30 AM Gwen Shapira wrote: > Hi everyone, > > I'm happy to announce that Colin McCabe, Vahid Hashemian and Manikumar > Reddy are now members of Apache Kafka PMC. > > Colin and Manikumar became committers on Sept 2018

Re: High CPU Usage on Brokers

pics, producers and consumers but the CPU is still >80%. How can we > troubleshoot to find where exactly is the problem? > > Thanks > > On Wed, Jan 8, 2020 at 10:33 AM Ismael Juma wrote: > > > Has the behavior changed after an upgrade or has it been consistent since > > the s

Re: High CPU Usage on Brokers

Has the behavior changed after an upgrade or has it been consistent since the start? Ismael On Thu, Jan 2, 2020 at 4:18 PM Navneeth Krishnan wrote: > Hi All, > > We have a kafka cluster with 12 nodes and we are pretty much seeing 90% > cpu usage on all the nodes. Here is all the information.

Re: Significant CPU utilization increase in 2.4.0

Hi James, Thanks for the report. This is not expected. How many partitions per broker and what Java version? I suggest filing a JIRA and, if possible, attach a flight recorder profile. Ismael On Fri, Dec 27, 2019, 7:07 PM James Brown wrote: > I just upgraded one of our test clusters from

Re: Kafka trunk vs master branch

Looks like someone pushed that branch by mistake. We should delete it. Ismael On Thu, Dec 26, 2019, 9:18 PM Matthias J. Sax wrote: > Should we delete `master` ? (Was not even aware it exists...) > > > -Matthias > > On 12/25/19 9:50 AM, M. Manna wrote: > > +1 with what John mentioned. > > > >

Re: Broker Interceptors

eally asking is "how should I have known this?" > > Tom > > On Fri, Dec 6, 2019 at 4:12 PM Ismael Juma wrote: > > > AbstractRequest and AbstractResponse are currently internal classes. > > > > Ismael > > > > On Fri, Dec 6, 2019 at 1:56 AM Tom Bent

Re: Broker Interceptors

t number of internal classes with general interceptor framework. A > > less > > > general solution more along the lines of the producer/consumer > > > interceptors on the client would satisfy the majority of use cases. If > we > > > are smart, we should be able to

Re: broken cluster / com.fasterxml.jackson.databind.ext.Java7Support.getDeserializerForJavaNioFilePath

Are you using ZooKeeper 3.5.6 client libraries with Kafka 2.3.1? Kafka 2.3.1 ships with ZooKeeper 3.4.x. Ismael On Thu, Dec 5, 2019 at 8:18 AM Charles Bueche wrote: > Hello all, > > I do have two Kafka clusters in action, test and prod. The two are formed > by 3 nodes each, are independent and

Re: Broker Interceptors

The main challenge is doing this without exposing a bunch of internal classes. I haven't seen a proposal that handles that aspect well so far. Ismael On Tue, Dec 3, 2019 at 7:21 AM Sönke Liebau wrote: > Hi Thomas, > > I think that idea is worth looking at. As you say, if no interceptor is >

Re: Preliminary blog post about the Apache Kafka 2.4.0 release

Manikumar, One thing I had previously missed, should we mention the upgrade to ZK 3.5? Ismael On Thu, Nov 14, 2019 at 10:41 AM Manikumar wrote: > Hi all, > > I've prepared a preliminary blog post about the upcoming Apache Kafka 2.4.0 > release. > Please take a look and let me know if you want

Re: Can not compile kafka

We have recently merged a PR that should fix the issue: https://github.com/apache/kafka/commit/09f700ab3e2a8441109e26851cc861be7856f5e4 `gradlew` now auto downloads the correct version so this kind of issue should no longer happen in the future. Ismael On Sun, Nov 24, 2019 at 5:40 AM Kun Song

Re: Broker shutdown slowdown between 1.1.0 and 2.3.1

Can you please file a JIRA? Ismael On Thu, Nov 21, 2019 at 3:52 PM Nicholas Feinberg wrote: > I've been looking at upgrading my cluster from 1.1.0 to 2.3.1. While > testing, I've noticed that shutting brokers down seems to take consistently > longer on 2.3.1. Specifically, the process of

Re: BufferOverflowException on rolling new segment after upgrading Kafka from 1.1.0 to 2.3.1

Can you please file a JIRA? Ismael On Tue, Nov 19, 2019 at 11:52 AM Daniyar Kulakhmetov < dkulakhme...@liftoff.io> wrote: > Hi Kafka users, > > We updated our Kafka cluster from 1.1.0 version to 2.3.1. > Message format and inter-broker protocol versions left the same: > >

Re: [DISCUSS] Streams-Broker compatibility regression in 2.2.1 release

+1 to the proposal. Let's also highlight this in the release notes for 2.2.2 and 2.3.0 please. Ismael On Wed, Sep 11, 2019 at 10:23 AM Matthias J. Sax wrote: > Hi, > > recently a user reported an issue upgrading a Kafka Streams application > from 2.2.0 to 2.2.1 (cf >

Re: [DISCUSS] Apache Kafka 2.4.0 release

Thanks for volunteering Manikumar. +1 Ismael On Mon, Aug 12, 2019 at 7:54 AM Manikumar wrote: > Hi all, > > I would like to volunteer to be the release manager for our next time-based > feature release (v2.4.0). > > If that sounds good, I'll post the release plan over the next few days. > >

Re: [VOTE] 2.2.1 RC1

Sorry for the delay Vahid. I suspect votes are more likely next week, after the feature freeze. Ismael On Thu, May 16, 2019 at 9:45 PM Vahid Hashemian wrote: > Since there is no vote on this RC yet, I'll extend the deadline to Monday, > May 20, at 9:00 am. > > Thanks in advance for checking /

Re: Broker deregisters from ZK, but stays alive and does not rejoin the cluster

Any clue what that might be? > - if I really start filing JIRA's should it rather be one single, or one > per error scenario > > On 3/21/19 4:05 PM, Ismael Juma wrote: > > Hi Joe, > > > > This is not expected behaviour, please file a JIRA. > > > > Ismael &

Re: Broker deregisters from ZK, but stays alive and does not rejoin the cluster

Hi Joe, This is not expected behaviour, please file a JIRA. Ismael On Mon, Mar 18, 2019 at 7:29 AM Joe Ammann wrote: > Hi all > > We're running several clusters (mostly with 3 brokers) with 2.1.1 > > We quite regularly see the pattern that one of the 3 brokers "detaches" > from ZK (the broker

Re: Kafka 2.0: High level consumer is slow to deal with SSL certification expiration

Hi, It would be great to verify that this happens with Kafka 2.2.0 RC1. If it does, then please file a JIRA so that this doesn't get lost. Ismael On Thu, Mar 7, 2019 at 4:19 PM Henry Cai wrote: > Hi, > > We have been using Kafka 2.0's mirror maker (which used High level > consumer) to do

Re: Kafka segment.index.bytes

We use sparse files by default so they don't actually take space (at least on Linux). However, there was a bug in Java 8 where sparse files were taking all the space. It was fixed in Java 8 update 202. Ismael On Sat, Feb 23, 2019 at 2:19 AM Soheil Pourbafrani wrote: > Hi, > > I have a 2-node

Re: COORDINATOR_NOT_AVAILABLE exception on the broker side and Disconnection Exception on the consumer side breaks the entire cluster

g kafka version 2.1.0 > and Kafka streams version 2.0.0 > > Just you let you know, I was able to fix the problem by changing processing > guarantee config from exactly once to at least once but now I'll need to > verify if results are affected. > > > > > > >

Re: COORDINATOR_NOT_AVAILABLE exception on the broker side and Disconnection Exception on the consumer side breaks the entire cluster

Hi, What version of Kafka are you using? Ismael On Fri, Feb 15, 2019 at 8:32 PM Ankur Rana wrote: > Any comments anyone? > > On Fri, Feb 15, 2019 at 6:08 PM Ankur Rana > wrote: > >> Hi everyone, >> >> We have a Kafka cluster with 5 brokers with all topics having at least 2 >> replication

Re: [ANNOUNCE] New Committer: Randall Hauch

Congratulations Randall! On Thu, Feb 14, 2019, 6:16 PM Guozhang Wang Hello all, > > The PMC of Apache Kafka is happy to announce another new committer joining > the project today: we have invited Randall Hauch as a project committer and > he has accepted. > > Randall has been participating in

Re: [ANNOUNCE] New Committer: Vahid Hashemian

Congratulations Vahid! On Tue, Jan 15, 2019, 2:45 PM Jason Gustafson Hi All, > > The PMC for Apache Kafka has invited Vahid Hashemian as a project > committer and > we are > pleased to announce that he has accepted! > > Vahid has made numerous contributions to the Kafka community over the past >

Re: SIGSEGV (0xb) on TransactionCoordinator

It's been explained that this is a bug in the JDK and updating to the latest release of Java 8 fixes it. Ismael On Thu, Jan 10, 2019 at 6:46 PM Ankur Rana wrote: > But G1GC is the default garbage collection algo used in kafka, it'll still > be using G1GC. > Did you add remove/add other

Re: Getting "Illegal batch type" exception on consumers

Hi, Best to keep the discussion in the JIRA. I asked a few questions. Ismael On Sat, Jan 5, 2019 at 9:38 AM Asaf Mesika wrote: > Hi, > > We've recently started encountering the following exceptions, which appears > to happen a lot on the Consumer side - we're using the old consumer (ZK >

Re: Kafka 2.1.0 JMX mbean broken ?

The metric was changed to include the API version. I believe this was in the upgrade notes for 2.0.0. Ismael On Thu, Dec 13, 2018, 3:35 PM Raghav Hi > > We are trying to move from Kafka 1.1.0 to Kafka 2.1.0. We used to monitor > our 3 node Kafka using JMX. Upon moving to 2.1.0, we have observed

Re: Kafka producer throw "TimeoutException: Batch Expired" when consumer begin to read data

This is likely the issue fixed by KIP-91. You'll get the right behaviour if you upgrade to 2.1 or you can increase the request timeout. Ismael On Tue, Dec 4, 2018, 10:12 PM JF Chen I have a system keep sending data to kafka continuously, and a spark > streaming application reading these data

Re: [ANNOUNCE] Apache Kafka 2.1.0

zmalkin, Alex Dunayevsky, Amit Sela, Andras > Katona, Andy Coates, Anna Povzner, Arjun Satish, Attila Sasvari, Aviem Zur, > Bibin Sebastian, Bill Bejeck, Bob Barrett, Brandon Kirchner, Bridger > Howell, Chia-Ping Tsai, Colin Hicks, Colin Patrick McCabe, Dhruvil Shah, > Dong Lin, Edoardo

Re: [VOTE] 2.0.1 RC0

Manikumar, looks like you have the necessary votes. :) Ismael On Wed, Nov 7, 2018, 10:45 AM Rajini Sivaram +1 (binding) > > Checked source build and unit tests. Ran quickstart with source and binary. > > Thank you for managing the release, Manikumar! > > Regards, > > Rajini > > On Wed, Nov 7,

Re: SIGSEGV fault in Kafka broker

e > > I also noticed that this error occurs when Kafka tries to rebuild corrupt > indices. > The code flow looks like this : > ProduceraStateManager.readSnapshot() -> Crc32C.compute() -> SIGSEGV > > Thanks, > Vishnu > > On Tue, Oct 16, 2018 at 11:19 AM Ismael Ju

Re: [DISCUSS] 2.0.1 bug fix release

Thanks for managing the release Manikumar! Ismael On Tue, 16 Oct 2018, 12:13 Manikumar, wrote: > Hi all, > > I would like to volunteer to be the release manager for 2.0.1 bug fix > release. > 2.0 was released July 30, 2018 and 44 issues are fixed so far. > > Please find all the resolved

Re: SIGSEGV fault in Kafka broker

Looks like a JVM bug. What Java distribution and version are you using? Ismael On Mon, Oct 15, 2018 at 6:34 PM Vishnu Viswanath < vishnu.viswanat...@gmail.com> wrote: > Hello Kafka experts, > > I am running Kafka version 1.1.0 in docker container and the container is > exiting with SIGSEGV. >

Re: [ANNOUNCE] New Committer: Manikumar Reddy

Congratulations Manikumar! Thanks for your continued contributions. Ismael On Thu, Oct 11, 2018 at 10:39 AM Jason Gustafson wrote: > Hi all, > > The PMC for Apache Kafka has invited Manikumar Reddy as a committer and we > are > pleased to announce that he has accepted! > > Manikumar has

[ANNOUNCE] New committer: Colin McCabe

Hi all, The PMC for Apache Kafka has invited Colin McCabe as a committer and we are pleased to announce that he has accepted! Colin has contributed 101 commits and 8 KIPs including significant improvements to replication, clients, code quality and testing. A few highlights were KIP-97 (Improved

Re: Java 11 OpenJDK/Oracle Java Release Cadence Questions

gt; Software Engineer > www.helixeducation.com > Blog | Twitter | Facebook | LinkedIn > > ____ > From: Ismael Juma > Sent: Tuesday, September 11, 2018 6:04 PM > To: Kafka Users > Subject: Re: Java 11 OpenJDK/Oracle Java Release Cadence Questions > > H

Re: Kafka Upgrade Issue

You can use Apache Kafka 1.1.1 if you need Java 7 support. Ismael On Fri, Aug 24, 2018 at 7:23 AM Nitya Mehrotra wrote: > Hi, > > > We are using Kafka 2.10_0.9.0.1 and recently trying to upgrade it to > latest Kafka version(i.e. Kafka 2.11_2.0.0).But we are having Kafka > Consumer in our

Re: Is Kafka broker 1.1.0 backward compatible with Java Kafka Client 0.10.1.1?

Yes. Ismael On Fri, Aug 24, 2018 at 12:20 AM Debraj Manna wrote: > Hi > > Is Kafka broker 1.1.0 backward compatible with Java Kafka Client ? It is > yes as per my understanding after reading this page > > but > I want to

[ANNOUNCE] New Kafka PMC member: Dong Lin

Hi everyone, Dong Lin became a committer in March 2018. Since then, he has remained active in the community and contributed a number of patches, reviewed several pull requests and participated in numerous KIP discussions. I am happy to announce that Dong is now a member of the Apache Kafka PMC.

Re: [ANNOUNCE] Apache Kafka 2.0.0 Released

vzner, Arjun Satish, asutosh936, > > Attila Sasvari, bartdevylder, Benedict Jin, Bill Bejeck, Blake Miller, > > Boyang Chen, cburroughs, Chia-Ping Tsai, Chris Egerton, Colin P. Mccabe, > > Colin Patrick McCabe, ConcurrencyPractitioner, Damian Guy, dan norwood, > > Daniel Sh

Re: [ANNOUNCE] Apache Kafka 1.1.1 Released

et data > between > systems or applications. > > ** Building real-time streaming applications that transform or react > to the streams > of data. > > > Apache Kafka is in use at large and small companies worldwide, including > Capital One, Goldman Sachs, ING, LinkedIn, Netf

Re: [VOTE] 2.0.0 RC2

ael, > > Thank you for pointing that out. I have re-uploaded the RC2 artifacts to > maven including streams-scala_2.12. Also submitted a PR to update build & > release scripts to include this. > > Thank you, > > Rajini > > > > On Fri, Jul 13, 2018 at 7

Re: [VOTE] 1.1.1 RC3

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 8, verified quickstart on binary artifact (Scala 2.12) with Java 8, sanity checked release notes and Maven staging repository. Thanks for managing the release Dong! Ismael On Sun,

Re: [VOTE] 2.0.0 RC2

Hi Rajini, Thanks for generating the RC. It seems like the kafka-streams-scala 2.12 artifact is missing from the Maven repository: https://repository.apache.org/content/groups/staging/org/apache/kafka/ Since this is the first time we are publishing this artifact, it is possible that this never

Re: [kafka-clients] [VOTE] 1.1.1 RC2

f so, can we get another +1 from PMC? > > Thanks! > Dong > > On Thu, Jul 5, 2018 at 10:38 AM, Ismael Juma wrote: > Thanks Dong. There are a couple of quickstart links below: >> >> https://repository.apache.org/content/groups/staging/org/apache/kafka/ >> >> Ism

Re: [kafka-clients] [VOTE] 1.1.1 RC2

Thanks Dong. There are a couple of quickstart links below: https://repository.apache.org/content/groups/staging/org/apache/kafka/ Ismael On Thu, Jul 5, 2018 at 10:32 AM Dong Lin wrote: > Hey everyone, > > Thanks for the vote! Sorry for late reply. I have been trying to understand > whether

Re: [ANNOUNCE] Apache Kafka 0.11.0.3 Released

am, Randall Hauch, tedyu, Jagadesh > Adireddi, Jarek Rudzinski, Jason Gustafson, Jeremy Custenborder, Anna > Povzner, Joel Hamill, John Roesler, Max Zheng, Mickael Maison, Robert > Yokota, Yaswanth Kumar, parafiend, Jiangjie (Becket) Qin, Arjun > Satish, Bill Bejeck, Damian Guy, Gitomain,

Re: [VOTE] 1.0.2 RC1

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 7, verified quickstart on binary artifact (Scala 2.12) with Java 8, sanity checked release notes and Maven staging repository. Ismael On Fri, Jun 29, 2018 at 10:02 PM Matthias J.

Re: [VOTE] 0.11.0.3 RC0

+1 (binding) Verified signature of source artifact, ran tests and verified quickstart on source artifact with Java 7, verified quickstart on binary artifact (Scala 2.11) with Java 7, sanity checked release notes and Maven staging repository. Thanks for running the release! Ismael On Fri, Jun

Re: ConsumerConnector and 0.10 message format

The performance impact happens if the consumer doesn't support the message format defined by log.message.format.version. The old consumer in Kafka 0.10 supports the message format introduced in 0.10 (including timestamps and the ability to avoid recompression in the produce path) so what you

Re: Broker cannot start switch to Java9 - weird file system issue ?

Thanks, I updated it. On Thu, Apr 26, 2018 at 4:09 AM, Enrico Olivelli <eolive...@gmail.com> wrote: > Here it is ! > > https://issues.apache.org/jira/browse/KAFKA-6828 > > Thank you > > Enrico > > 2018-04-24 20:53 GMT+02:00 Ismael Juma <ism...@ju

Re: Broker cannot start switch to Java9 - weird file system issue ?

A JIRA ticket would be appreciated. :) Ismael On Sat, Apr 21, 2018 at 12:51 AM, Enrico Olivelli <eolive...@gmail.com> wrote: > Il sab 21 apr 2018, 06:29 Ismael Juma <ism...@juma.me.uk> ha scritto: > > > Hi Enrico, > > > > It is a real problem because it ca

Re: Broker cannot start switch to Java9 - weird file system issue ?

Hi Enrico, It is a real problem because it causes indexes to take a lot more disk space upfront. The sparsity is an important if people over partition, for example. Ismael On Fri, Apr 20, 2018 at 12:41 PM, Enrico Olivelli <eolive...@gmail.com> wrote: > Il ven 20 apr 2018, 20:24 Is

Re: Broker cannot start switch to Java9 - weird file system issue ?

Hi Enrico, Coincidentally, I saw your message to nio-dev and followed up there. Ismael On Fri, Apr 20, 2018 at 8:18 AM, Enrico Olivelli wrote: > It is a deliberate change in JDK code > > Just for reference see this discussion on nio-dev list on OpenJDK >

Re: Kafka bug ISR expands/shrinks "Count" JMX attribute doesn't work as expected

How are you checking these metrics? They are per leader. That is, if broker A is the leader for topic partition topic-0 and broker B is a follower, then shutting down broker B should cause the IsrShrinksPerSec for broker A to be updated. You would also something like the following in the

Re: accessing Kafka broker 0.9.0.1 with Kafka-client 1.0.0

1.0.0 supports brokers with version 0.10.0 and higher. Ismael On Tue, Apr 3, 2018 at 6:36 AM, Nomar Morado wrote: > Hi, > > I am trying to access my Kafka brokers using springbok 2.0 which is using > Kafka-client 1.0.0 and it seems like running into timeout exceptions >

Re: suggestion for 1.1.0 release notes

I updated the JIRA to make this clearer. Ismael On Fri, Mar 30, 2018 at 3:38 PM, Gibson, Bill (ArcSight) < bill.gib...@microfocus.com> wrote: > The release notes include this resolved issue: > > [KAFKA-6390] - Update ZooKeeper to 3.4.11, Gradle and other minor updates > > I saw 3.4.10 in the

Re: [ANNOUNCE] Apache Kafka 1.1.0 Released

Netflix, Pinterest, Rabobank, > > Target, The New York Times, Uber, Yelp, and Zalando, among others. > > > > > A big thank you for the following 120 contributors to this release! > > > Adem Efe Gencer, Alex Good, Andras Beni, Andy Bryant, Antony Stubbs, > > Apurva M

Re: [ANNOUNCE] New Committer: Dong Lin

Congratulations Dong! Thanks for your contributions so far and looking forward to future ones. Ismael On Wed, 28 Mar 2018, 10:58 Becket Qin, wrote: > Hello everyone, > > The PMC of Apache Kafka is pleased to announce that Dong Lin has accepted > our invitation to be a new

Re: Upgrade choice between 0.11.0 and 1.0.1

1.0.1 is the best choice right now. 1.1.0 is going to be out this week though. Ismael On Tue, Mar 27, 2018 at 4:07 AM, chou.fan wrote: > Hi, we are planning to upgrade our kafka cluster to benefit from the new > feature of transactional processing. There are two

Re: Confluent Docker Images Using Older Debian and older Azul JDK 8?

Hi Clayton, I have forwarded the message to the Confluent mailing list and bcc'd the kafka-users mailing list since this is a question about the Confluent Docker images. Ismael On Thu, Mar 22, 2018 at 4:14 PM, Clayton Wohl wrote: > I see the official upcoming Confluent

Re: Subject: [VOTE] 1.1.0 RC3

Vahid, The Java 9 Connect issue is similar to the one being fixed for Trogdor in the following PR: https://github.com/apache/kafka/pull/4725 We need to do something similar for Connect. Ismael On Fri, Mar 16, 2018 at 3:10 PM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Hi Damian,

  1   2   3   4   5   >