FIPS Compliant(Apache Kafka)

Hi, I was wondering if Apache Kafka is Fips Compliant or not. I see that Confluent Kafka is FIPS Complaint(https://docs.confluent.io/platform/current/security/compliance.html). What about Apache Kafka, is there any documentation like above for apache kafka also? Regards, Brajesh

Re: [VOTE] 2.7.0 RC6

Thanks for taking on this release, Bill! I'm +1 (binding). I verified the signatures, built from source, and ran all the tests. I also read over the upgrade documentation. Thanks, -John On Wed, 2020-12-16 at 09:53 -0500, Bill Bejeck wrote: > Hello Kafka users, developers and client-developers,

[jira] [Created] (KAFKA-10864) Convert End Transaction Marker to use auto-generated protocal

dengziming created KAFKA-10864: -- Summary: Convert End Transaction Marker to use auto-generated protocal Key: KAFKA-10864 URL: https://issues.apache.org/jira/browse/KAFKA-10864 Project: Kafka

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: [DISCUSS] KIP-691: Transactional Producer Exception Handling

Thanks for everyone's feedback so far. I have polished the KIP after offline discussion with some folks working on EOS to make the exception handling more lightweight. The essential change is that we are not inventing a new intermediate exception type, but instead separating a full transaction

Re: [DISCUSS] KIP-691: Transactional Producer Exception Handling

Thanks Bruno for the feedback. On Mon, Dec 7, 2020 at 5:26 AM Bruno Cadonna wrote: > Thanks Boyang for the KIP! > > Like Matthias, I do also not know the producer internal well enough to > comment on the categorization. However, I think having a super exception > (e.g. RetriableException) that

[jira] [Resolved] (KAFKA-10846) FileStreamSourceTask buffer can grow without bound

[ https://issues.apache.org/jira/browse/KAFKA-10846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10846. Fix Version/s: 2.8.0 Resolution: Fixed > FileStreamSourceTask buffer can grow

Re: [VOTE] 2.7.0 RC6

Sorry, that should actually say (non-binding) :) Thanks Bill! On Thu, Dec 17, 2020 at 7:46 PM Sophie Blee-Goldman wrote: > Thanks for driving this release! I built from the tag and ran the tests, > and verified the signatures. > > +1 (binding) > > Sophie > > On Thu, Dec 17, 2020 at 3:53 PM

Re: [VOTE] 2.7.0 RC6

+1 (binding) Thank you for the release, Bill! I validated signatures, built from source package and ran the perf producer/consumer to validate. On Wed, Dec 16, 2020 at 6:53 AM Bill Bejeck wrote: > > Hello Kafka users, developers and client-developers, > > This is the seventh candidate for

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

On Thu, Dec 17, 2020, at 17:02, Jun Rao wrote: > Hi, Colin, > > Thanks for the reply. Sounds good. One more comment. > > 231. Currently, we have sasl.mechanism.inter.broker.protocol for inter > broker communication. It seems that we need a similar config for specifying > the sasl mechanism for

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hi, Colin, Thanks for the reply. Sounds good. One more comment. 231. Currently, we have sasl.mechanism.inter.broker.protocol for inter broker communication. It seems that we need a similar config for specifying the sasl mechanism for the communication between the broker and the controller. Jun

Re: [VOTE] 2.7.0 RC6

Thanks for driving this release! I built from the tag and ran the tests, and verified the signatures. +1 (binding) Sophie On Thu, Dec 17, 2020 at 3:53 PM Jakub Scholz wrote: > +1 (non-binding) ... I used the binaries (Scala 2.12) and the staged Maven > artifacts - all seems to work fine.

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

On Thu, Dec 17, 2020, at 10:19, Jun Rao wrote: > Hi, Colin, > > Thanks for the reply. > > 211. Hmm, I still don't see a clear benefit of registering a broker before > recovery. It's possible for the recovery to take time. However, during the > recovery mode, it seems the broker will still be in

Jenkins build is back to normal : Kafka » kafka-trunk-jdk8 #297

See

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] KIP-695: Improve Streams Time Synchronization

Thanks Jason, We would only return the metadata for the latest fetches. So, if someone wanted to use this to lazily maintain a client-side metadata map for all partitions, they'd have to store it separately and merge in new updates as they arrive. This way: 1. We don't need to increase the

Re: [VOTE] 2.7.0 RC6

Thanks for running the release Bill! +1 (binding) - verified signatures - build from sources and ran tests - verified quickstarts using Scala 2.12 binaries -Matthias On 12/16/20 6:53 AM, Bill Bejeck wrote: > Hello Kafka users, developers and client-developers, > > This is the seventh

Re: [VOTE] 2.6.1 RC3

Thanks for running the release Mickael! +1 (binding) - verified signatures - build from sources and ran tests - verified the three quickstarts -Matthias On 12/16/20 4:17 AM, Manikumar wrote: > Hi, > > +1 (binding) > - verified signatures > - ran the tests on the source archive with Scala

[apache/kafka] KAFKA-10413 Allow even distribution of lost/new tasks when more than one worker

Hi Team, Can some help re trigger the build for this PR. https://github.com/apache/kafka/pull/9319 Thanks Ramesh

Re: [DISCUSS] KIP-631: The Quorum-based Kafka Controller

Hi, Colin, Thanks for the reply. 211. Hmm, I still don't see a clear benefit of registering a broker before recovery. It's possible for the recovery to take time. However, during the recovery mode, it seems the broker will still be in the fenced mode and won't be able to do work for the clients.

[jira] [Resolved] (KAFKA-10862) kafka stream consume from the earliest by default

[ https://issues.apache.org/jira/browse/KAFKA-10862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yuexi Liu resolved KAFKA-10862. --- Resolution: Not A Problem > kafka stream consume from the earliest by default >

[jira] [Resolved] (KAFKA-10850) Use primitive type to replace deprecated 'new Integer' from BrokerToControllerRequestThreadTest

[ https://issues.apache.org/jira/browse/KAFKA-10850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-10850. Fix Version/s: 2.8.0 Resolution: Fixed > Use primitive type to replace deprecated

Re: [VOTE] KIP-695: Improve Streams Time Synchronization

Hi John, I've made a pass over the KIP and I think it will be a good addition. Modulo Jason's question, I'm a +1 (binding). Thanks, Bill On Wed, Dec 16, 2020 at 1:29 PM Jason Gustafson wrote: > Hi John, > > Just one question. It wasn't very clear to me exactly when the metadata > would be

[jira] [Resolved] (KAFKA-9126) Extend `StreamJoined` to allow more store configs

[ https://issues.apache.org/jira/browse/KAFKA-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leah Thomas resolved KAFKA-9126. Fix Version/s: 2.8.0 Resolution: Fixed > Extend `StreamJoined` to allow more store configs

[jira] [Created] (KAFKA-10863) Conver CONTROL_RECORD_KEY_SCHEMA_VERSION to use auto-generated protocal

dengziming created KAFKA-10863: -- Summary: Conver CONTROL_RECORD_KEY_SCHEMA_VERSION to use auto-generated protocal Key: KAFKA-10863 URL: https://issues.apache.org/jira/browse/KAFKA-10863 Project: Kafka

Re: [VOTE] voting on KIP-631: the quorum-based Kafka controller

Thanks for driving this KIP, Colin. The KIP is really well written. This is so exciting! +1 (binding) Best, David On Wed, Dec 16, 2020 at 11:51 PM Colin McCabe wrote: > On Wed, Dec 16, 2020, at 13:08, Ismael Juma wrote: > > Thanks for all the work on the KIP. Given the magnitude of the KIP, I

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #296

See Changes: [github] KAFKA-10861; Fix race condition in flaky test `testFencingOnSendOffsets` (#9762) -- [...truncated 6.93 MB...]