Re: Kafka SSL error

Hi, Looking at your commands it looks as if you generated a self signed key for server, self signed key for client and then imported the CA keys public keys into the truststores. I don’t think this will work because now you have two different self signed keys in the keystores and the presumably

Using different SSL keystore and truststore for different listeners

Hi, I would like to setup my Kafka cluster so that it has several SSL listeners (for replication, for clients in internal network, for clients in external network etc.). But I need to use different certificates for each listener. In particular I need: * different server keys (keystore) because

Re: Using different SSL keystore and truststore for different listeners

<manikumar.re...@gmail.com> wrote: > Hi, > > We can override per listener security settings. This way we can configure > each listener > to with different configs. > > https://issues.apache.org/jira/browse/KAFKA-4636 > > On Fri, Sep 22, 2017 at 2:00 PM, Jakub Scho

Re: Kafka SSL error

t; depth=0 C = US, ST = , L = Unknown, O = ., OU = > > , CN = > > > verify error:num=18:self signed certificate > > > > verify return:1 > > > > > - > -- > > > > 0

Re: Kafka - leadership

One broker can be leader for many partitions. Partitions are not only used to scale the brokers but also to scale the clients. So in many cases it makes perfect sense to have many partitions running from the same broker. (Of course having only one broker in total means no HA etc., but I guess you

Configuration of Kafka Connect REST interface

Hi, I have some questions about the configuration of the Kafka Connect REST interface. 1) What are the configuration options rest.advertised.host.name and rest.advertised.port useful for? The documentation says "If this is set, this is the hostname that will be given out to other workers to

Re: SSL setup in Kafka 2.10.0.10.2.1 for keystore and truststore files

t; > Regarding host name validation, does FQDN with hostname always present in > CN (common name) of the certificate? What if I want to use some free form > text in CSR for CN field to make it for multiple host? > > > Thanks > Awadhesh > > On Fri, Sep 29, 2017 at 5:59

Re: Add Kafka user list

Out of curiosity ... there seem to be quite a lot of these emails. I wonder if we can do something to improve on this. Was someone thinking about changing the UX on the Kafka website? Maybe removing the links from the users@kafka... email? Or rephrasing the sentence to make the subscribe email be

Re: SSL setup in Kafka 2.10.0.10.2.1 for keystore and truststore files

This normally means that the truststore in your producer doesn't contain a) the public key of your broker or b) the public keys of the CA which signed the broker key. With this error it didn't even get to the verification of the client certificate yet. Looking at the blog post it looks like there

Re: Disable anonymous access to zookeeper

Hi Jamie, You should be able to use something like this: Client { com.sun.security.auth.module.Krb5LoginModule required useKeyTab=true storeKey=true keyTab="/etc/security/keytabs/kafka_server.keytab" principal="kafka/kafka1.hostname@example.com"; }; or this: Client {

Re: Recommended settings for Internal Topics

When you use the default replication factor of 3 with single node broker the offset and transaction topics will be never created. As a result applications using them will not work (for example a consumer using the offsets topic will not work). Kafka broker it self will keep running. Given how the

Re: Message Routing between several locations

Hi Andreas, What you are describing is basically one central cluster (managed by the central org.) and a set of "satelite" clusters (which are managed by different org. each). These will never form a single cluster and you cannot use features such as replication to mirror the messages. But you

Re: kafka compacted topic

There is quite a nice section on this in the documentation - http://kafka.apache.org/documentation/#compaction ... I think it should answer your questions. On Wed, Nov 29, 2017 at 7:19 AM, Kane Kim wrote: > How does kafka log compaction work? > Does it compact all of the

Re: Kafka Security SSL and SASL_PLAINTEXT

he > producer logs. > > Regards > Bhanu > > On Fri, Nov 3, 2017 at 10:37 PM, Jakub Scholz <ja...@scholz.cz> wrote: > > > Do you have some logs from your producer? Is it just the producer what is > > not working? Or is the producer not working because the Interbroker

Re: Kafka Security SSL and SASL_PLAINTEXT

a, is there any quick way to enable the > > producer logs. > > > > Regards > > Bhanu > > > > On Fri, Nov 3, 2017 at 10:37 PM, Jakub Scholz <ja...@scholz.cz> wrote: > > > >> Do you have some logs from your producer? Is it just the producer

Re: Kafka Security SSL and SASL_PLAINTEXT

Sure, you can use someting like this: listeners=SSL://:9092,REPLICATION://:19092 listener.security.protocol.map=SSL:SSL,REPLICATION:SASL_PLAINTEXT inter.broker.listener.name=REPLICATION (plus all the SSL and Kerberos configuration) Jakub On Fri, Nov 3, 2017 at 4:48 PM, chidigam .

Re: Kafka Security SSL and SASL_PLAINTEXT

ing, I tried what you have suggested, but producer is > not working. > If I enable SSL for replication,then every thing works fine. > > Regards > Bhanu > > On Fri, Nov 3, 2017 at 9:52 PM, Jakub Scholz <ja...@scholz.cz> wrote: > > > Sure, you can use someting

Re: Client addressable listener

Try something like this: listeners=CLIENT://:9090 ,PLAINTEXT://:9092 advertised.listeners=CLIENT://my.public.dns.name:9090,PLAINTEXT://:9092 This will tell the listener to listen on your local ip addresses but to advertise the DNS name. Jakub On Tue, Nov 7,

Re: Kafka JVM heap limit

This is probably because Kafka uses quite heavily the disk cache maintained by the operating system instead of storing messages in the JVM memory. So the requirements for the heap memory can be fairly small. The design section of the documentation describes the details:

Re: Client addressable listener

.public.dns.name:9090,PLAINTEXT://:9092 > > And now I'm getting the error 'No security protocol defined for listener > CLIENT://:9090 HTTP. > > I tried adding to listener.security.protocol.map the value > 'HTTP:PLAINTEXT' but I'm still getting the above error. Any thoughts on > tha

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

+1 (non-binding) ... I ran my tests and verified the RC1 with my applications. On Mon, Jun 25, 2018 at 7:31 PM Manikumar wrote: > +1 (non-binding) Ran tests, Verified quick start, producer/consumer perf > tests > > > On Sat, Jun 23, 2018 at 8:11 AM Dong Lin wrote: > > > Thank you for

Re: [VOTE] 2.0.0 RC0

+1 (non-binding) ... I ran my tests and verified the RC0 against my applications. On Mon, Jun 25, 2018 at 8:12 PM Thomas Crayford wrote: > +1 (non-binding) Heroku has run our usual set of upgrade and performance > tests, and we haven't found any notable issues through that. > > On Sat, Jun 23,

Re: one machine that have four network.....

Maybe a stupid question ... but if you just want to create a setup with 3 zookeepers and 3 brokers on a single machine you just need to use different port numbers. You do not need separate network interfaces. What are you trying to achieve with the different network interfaces? Regards Jakub On

Re: one machine that have four network.....

To be honest, I'm not familiar enough with the network configuration etc. But the advice from Svante looks like it might give some idea how to fix it. Regards Jakub On Tue, Jan 16, 2018 at 2:08 PM, 猪少爷 wrote: > Jakhub: I would like to increase the bandwidth by

Re: [Production Guideline] Is it good idea to provide limited number of brokers(3 brokers) in kafka client in large cluster

Hi Pritam, It is basically about the probabilities, right? If you use 3 brokers as bootstrap servers, what is the probability that all three will be unavailable at the same time? To make it more reliable: - the more brokers in the bootstrap list the lower the probability that all of them will be

Re: Static IP Configuration

Yes, the clients do not connect to Zookeeper anymore. You can create a loadbalancer which will point to all your Kafka brokers and use the address of such loadbalancer as the "bootstrap server" in your clients. The clients will use the loadbalancer and connect to one of the Kafka brokers and get

Re: Static IP Configuration

to change > key/password for my cluster how can I change it in my clients (producers) > because they might be sitting in my remote place (sensors/mobile apps)? > > On Thu, Feb 15, 2018 at 7:30 PM, Jakub Scholz <ja...@scholz.cz> wrote: > > > Yes, the clients do not connect

Re: [VOTE] 1.1.1 RC3

+1 (non-binbding) ... built from source, run tests and used it with several of my applications without any problems. Thanks & Regards Jakub On Mon, Jul 9, 2018 at 12:36 AM Dong Lin wrote: > Hello Kafka users, developers and client-developers, > > This is the fourth candidate for release of

Re: [VOTE] 2.0.0 RC2

+1 (non-binbding) ... I built the RC2 from source, run tests and used it with several of my applications without any problems. Thanks & Regards Jakub On Tue, Jul 10, 2018 at 7:17 PM Rajini Sivaram wrote: > Hello Kafka users, developers and client-developers, > > > This is the third candidate

Re: [VOTE] 2.0.1 RC0

+1 (non-binding) ... I used the staged binaries and run tests with different clients. On Fri, Oct 26, 2018 at 4:29 AM Manikumar wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of Apache Kafka 2.0.1. > > This is a bug fix release closing

Re: [VOTE] 2.1.0 RC0

+1 (non-binding) ... I used the staged binaries and checked it with different clients. On Wed, Oct 24, 2018 at 10:17 AM Dong Lin wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for feature release of Apache Kafka 2.1.0. > > This is a major version

Re: [VOTE] 2.1.0 RC1

+1 (non-binding) ... I used the staged artifacts and binaries and run my tests On Sat, Nov 10, 2018 at 12:33 AM Dong Lin wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate for feature release of Apache Kafka 2.1.0. > > This is a major version release

Re: [VOTE] 2.2.0 RC1

Thanks for driving the release Matthias. I noticed two very minor issues while testing the RC1 and opened PRs against master: * https://github.com/apache/kafka/pull/6379 * https://github.com/apache/kafka/pull/6381 I assume it might not be worth including these into 2.2 since it is nothing

Re: [VOTE] 2.2.0 RC2

+1 (non-binding). I used the staged binaries and run some of my tests against them. All seems to look good to me. On Sat, Mar 9, 2019 at 11:56 PM Matthias J. Sax wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for release of Apache Kafka 2.2.0. > >

Re: [VOTE] 2.1.1 RC2

+1 (non-binding). I built it from source and run my tests. Everything seems to be fine. On Sat, Feb 9, 2019 at 12:10 AM Magnus Edenhill wrote: > +1 > > Passes librdkafka test suite. > > Den fre 8 feb. 2019 kl 21:02 skrev Colin McCabe : > > > Hi all, > > > > This is the third candidate for

Re: [VOTE] 2.3.0 RC3

+1 (non-binding). I used the binaries and run some of my tests against them. On Thu, Jun 20, 2019 at 12:03 AM Colin McCabe wrote: > Hi all, > > We discovered some problems with the second release candidate (RC2) of > 2.3.0. Specifically, KAFKA-8564. I've created a new RC which includes the >

Re: [VOTE] 2.2.1 RC1

+1 (non-binding) ... I used the binaries and run tests with different clients. All seems to work fine. On Tue, May 14, 2019 at 5:15 AM Vahid Hashemian wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate for release of Apache Kafka 2.2.1. > > Compared

Re: How to un-subscribe from Kafka user group

I think you should send an email to users-unsubscr...@kafka.apache.org - that should get you unsubscribed. Jakub On Tue, Jul 30, 2019 at 3:25 PM ASHOK MACHERLA wrote: > Hi Teammates > > Can anyone guide me to un-subscribe from Kafka user group. > > > Sent from Outlook

Re: Subject: [VOTE] 2.2.2 RC2

+1 (non-binding) ... I used the prepared artifacts (Scala 2.12) and run my tests against them. All seems to be fine. On Sun, Nov 10, 2019 at 2:10 AM Matthias J. Sax wrote: > Thanks for running the release Randall! > > - verified all signatures > - build from source > - ran unit/integration

Re: [ANNOUNCE] New committer: David Jacot

Congrats David! Jakub On Fri, Oct 16, 2020 at 6:01 PM 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 active since

Re: [VOTE] 2.7.0 RC6

+1 (non-binding) ... I used the binaries (Scala 2.12) and the staged Maven artifacts - all seems to work fine. Thanks. Jakub On Wed, Dec 16, 2020 at 3:53 PM Bill Bejeck wrote: > Hello Kafka users, developers and client-developers, > > This is the seventh candidate for release of Apache Kafka

Re: [VOTE] 3.1.0 RC0

+1 (non-binding). I used the staged Scala 2.13 binaries and the staging Maven repository to run my tests. All seems to work fine. Thanks for running the release David! Jakub On Thu, Dec 23, 2021 at 11:17 PM David Jacot wrote: > Hello Kafka users, developers and client-developers, > > This is

Re: [VOTE] 3.0.1 RC0

+1 (non-binding). I used the staged Scala 2.13 binaries and the staging Maven repository to run my tests. All seems to work fine, no issues found. Thanks Jakub On Thu, Mar 3, 2022 at 7:05 PM Mickael Maison wrote: > Hello Kafka users, developers and client-developers, > > This is the first

Re: [ANNOUNCE] New committer: Luke Chen

Congrats Luke! Thanks for all your contributions! Jakub On Thu, Feb 10, 2022 at 12:22 AM Guozhang Wang wrote: > The PMC for Apache Kafka has invited Luke Chen (showuon) as a committer and > we are pleased to announce that he has accepted! > > Luke has been actively contributing to Kafka since

Re: [VOTE] 3.1.0 RC1

+1 (non-binding). I used the staged Scala 2.13 binaries and the staging Maven repository to run my tests. All seems to work fine, no issues found. Thanks Jakub On Wed, Jan 12, 2022 at 1:59 PM David Jacot wrote: > Hello Kafka users, developers and client-developers, > > This is the second

Re: [VOTE] 3.6.0 RC2

+1 (non-binding). I used the Scala 2.13 binaries and the staged Maven artifacts and run my tests. Everything seems to work fine for me. Thanks Jakub On Fri, Sep 29, 2023 at 8:17 PM Satish Duggana wrote: > Hello Kafka users, developers and client-developers, > > This is the third candidate for

Downgrading KRaft metadata version

Hi, I have a Kraft cluster running Kafka 3.5 and using the metadata.version 3.5 as well: $ bin/kafka-features.sh --bootstrap-server localhost:9092 describe Feature: metadata.version SupportedMinVersion: 3.0-IV1 SupportedMaxVersion: 3.5-IV2FinalizedVersionLevel: 3.5-IV2 Epoch: 140

Re: Upgrading Kafka Kraft in Kubernetes

Hi Jiří, Why can't you run it from another Pod? You should be able to specify --bootstrap-server and point it to the brokers to connect to. You can also pass further properties to it using the --command-config option. It should be also possible to use it from the Admin API

Re: [External Email] Re: Upgrading Kafka Kraft in Kubernetes

er:port] upgrade > --metadata 3.6 > > This is doable using declarative Kubernetes job. > > Thank you very much, I appreciate your help. > > Jiri > > From: Jakub Scholz > Sent: Thursday, October 19, 2023 5:18 PM > To: users@kafka.apache.org > Subject: [External Email] Re: U

Re: [VOTE] 3.2.1 RC3

+1 (non-binding). I run my tests with the staged binaries and all seems to work fine. Thanks for running the release. Jakub On Fri, Jul 22, 2022 at 3:15 AM David Arthur wrote: > Hello Kafka users, developers and client-developers, > > This is the first release candidate of Apache Kafka 3.2.1.

Re: [VOTE] 3.1.1 RC1

+1 (non-binding). I used the Scala 2.13 binaries and staged Maven artifacts and ran various tests with them. Thanks for doing the release. Jakub On Fri, Apr 29, 2022 at 8:16 PM Mickael Maison wrote: > Hi Tom, > > Thanks for running this release! > > I've done the following: > - Checked

Re: [VOTE] 3.2.0 RC1

+1 (non-binding). I used the Scala 2.13 binaries and the staged Maven artifacts and ran various tests with them. Thanks for doing the release. Jakub On Tue, May 3, 2022 at 4:07 PM Bruno Cadonna wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate for

Re: [VOTE] 3.3.0 RC2

+1 (non-binding). I used the staged binaries (Scala 2.13) and Maven artifacts and ran my tests. All seems to work fine. Thanks for running the release. Jakub On Wed, Sep 21, 2022 at 1:17 AM David Arthur wrote: > Hello Kafka users, developers and client-developers, > > This is the second

Re: [VOTE] 3.3.1 RC0

+1 (non-binding). I used the staged Scala 2.13 artifacts and the staged Maven repo to run my tests and didn't find any issues. Thanks Jakub On Thu, Sep 29, 2022 at 11:41 PM José Armando García Sancio wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate

Re: [VOTE] 3.3.2 RC1

+1 (non-binding). I used the staged Scala 2.13 binaries and Maven repo to run my tests. All seems to work fine. Thanks for running the release. Jakub On Wed, Dec 21, 2022 at 11:22 PM Chris Egerton wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate

Re: Kafka Connect Startup Hook

In Strimzi, we use a Java agent to register the tracer ( https://github.com/strimzi/strimzi-kafka-operator/tree/main/tracing-agent/ if you wanna check the source code). Jakub On Mon, Mar 20, 2023 at 9:18 AM Jan Baudisch (extern) < jan.baudisch.ext...@bdess.com> wrote: > Hello, > > can someone

Re: Compatibility / Optimisation to IBM's Power10 architecture

Hi Yiannis, For the Strimzi Operator it might be best to ask in the Strimzi community as that is not part of the Apache Kafka project: https://github.com/strimzi/strimzi-kafka-operator#getting-help ... in general, as of today, Strimzi supports the amd64, arm64, and s390x architectures. I know

Re: [VOTE] 3.4.0 RC2

+1 (non-binding). I run my tests with the staged Scala 2.13 binaries and staged Maven artifacts. All seems to work fine. Thanks & Regards Jakub On Tue, Jan 31, 2023 at 8:01 PM David Arthur wrote: > Hey folks, we found a couple of blockers with RC1 and have fixed them in > the latest release

Re: [VOTE] 3.5.1 RC0

+1 (non-binding). I used the staged Scala 2.13 binaries and the Maven artifacts for my tests and all seems to work fine. Thanks. Jakub On Wed, Jul 12, 2023 at 12:03 PM Divij Vaidya wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of

Re: [VOTE] 3.5.0 RC1

+1 (non-binding) ... I used the staged binaries with Scala 2.13 and staged artifacts to run my tests. All seems to work fine. Thanks for running the release Mickael! Jakub On Mon, Jun 5, 2023 at 3:39 PM Mickael Maison wrote: > Hello Kafka users, developers and client-developers, > > This is

Re: [VOTE] 3.4.1 RC3

+1 (non-binding) ... I used the staged binaries and Maven artifacts to run my tests and all seems to work fine. Thanks for running the release. Jakub On Fri, May 26, 2023 at 9:34 AM Luke Chen wrote: > Hello Kafka users, developers and client-developers, > > This is the 4th candidate for

Re: [VOTE] 3.7.0 RC4

+1 (non-binding). I used the staged binaries with Scala 2.13 and the staged Maven artifacts to run my tests. All seems to work fine. Thanks. Jakub On Fri, Feb 9, 2024 at 4:20 PM Stanislav Kozlovski wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate

Re: [VOTE] 3.6.1 RC0

+1 non-binding. I used the staged Scala 2.13 artifacts and the staged Maven repo for my tests. All seems to work fine. Thanks Jakub On Fri, Nov 24, 2023 at 4:37 PM Mickael Maison wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of Apache

Re: [VOTE] 3.5.2 RC1

+1 non-binding. I used the staged Scala 2.13 binaries and the staged Maven repo to run my tests and all seems to work fine. Thanks & Regards Jakub On Tue, Nov 21, 2023 at 11:09 AM Luke Chen wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for

Re: Security Vulnerabilities found in Kafka 3.5.1

As I told you on the Strimzi mailing list: * You should check the paths where the vulnerabilities are found and in which component they are => that should tell you where it needs to be addressed * You should also compare which ones are already addressed in the upcoming Kafka 3.5.2 (or in Kafka

Re: [VOTE] 3.6.2 RC2

+1 (non-binding). I used the staged Scala 2.13 binaries and the staging Maven repo for my testing. All seems to work fine. Thanks for doing the release. Jakub On Thu, Mar 28, 2024 at 10:51 AM Manikumar wrote: > Hello Kafka users, developers and client-developers, > > This is the second