Rpm spec file for kafka

Hello, I wanted to build a rpm from scratch. Is there a spec file anyone could guide me to ? I can see ones for kafka-rest and schema-registry . it would be of great help if I could get for kafka as well. I know there are rpms available but I would prefer it to build on my own as it would be

Build failed in Jenkins: kafka-trunk-jdk8 #4395

See Changes: [github] MINOR: System test ZooKeeper upgrades (#8384) -- [...truncated 2.52 MB...] org.apache.kafka.streams.StreamsConfigTest >

Re: 2.5.0 Producer.sendOffsetsToTransaction() and Backwards Compatibility

Thanks Mattias >Hence, why do you want/need to switch to the newer overload that only works for 2.5+ brokers? So I can choose to use the producer per consumer thread Vs. the producer per group/topic/partition threading model for zombie fencing, based on the broker version. I don't have the same

Build failed in Jenkins: kafka-trunk-jdk11 #1316

See Changes: [github] KAFKA-6145: Pt. 5 Implement high availability assignment (#8337) -- [...truncated 6.02 MB...]

Re: 2.5.0 Producer.sendOffsetsToTransaction() and Backwards Compatibility

Gary, thanks for the question. We recently had a discussion about the exact some topic: http://mail-archives.apache.org/mod_mbox/kafka-dev/202003.mbox/%3CCAJKanumaUg7bcRr%3DoZqQq9aWuO%3DfA5U1uvxAciB6RbYsvsEbYQ%40mail.gmail.com%3E Note that the "old" `sendOffsetsToTransaction(..., String

Re: [VOTE] KIP-444: Refactor and Augment Metrics for Kafka Streams

A correction for the previous email: - number of alive global threads, INFO - number of alive restore threads, INFO These two metrics are not going to be added in this KIP, since we do not have restore threads in Kafka Streams yet. Guozhang On Thu, Apr 2, 2020 at 2:02 PM Guozhang

[jira] [Created] (KAFKA-9812) Integration tests hang and timeout the entire PR build on jenkins

Konstantine Karantasis created KAFKA-9812: - Summary: Integration tests hang and timeout the entire PR build on jenkins Key: KAFKA-9812 URL: https://issues.apache.org/jira/browse/KAFKA-9812

[jira] [Created] (KAFKA-9811) TransactionMetadata state and pendingState are non-volatile and read outside the metadata lock

Bob Barrett created KAFKA-9811: -- Summary: TransactionMetadata state and pendingState are non-volatile and read outside the metadata lock Key: KAFKA-9811 URL: https://issues.apache.org/jira/browse/KAFKA-9811

Re: [DISCUSS] KIP-585: Conditional SMT

Hi Tom, hi Chris, in principle an expression language sounds good, as it would allow us to cover pretty much any use-case that we could possibly come up with. And bearing in mind that I was the one who originally started talking about more complex use-cases, I should be happy about that :) That

Re: [DISCUSS] KIP-587 Suppress detailed responses for handled exceptions in security-sensitive environments

Hi Connor, Great stuff! I generally like being able to see the stack trace of an exception directly via the REST API but can definitely understand the security concerns here. I've got a few questions/remarks about the KIP and would be interested in your thoughts: 1. The KIP mentions a

Re: [VOTE] KIP-444: Refactor and Augment Metrics for Kafka Streams

Hello all, While implementing the last piece of this KIP for the coming 2.6 release, I realized that it is important to cover the following monitoring metrics as well so I'd propose adding them as part of KIP-444 too: Instance-level: - number of alive stream threads, INFO - number of

Re: 2.5.0 Producer.sendOffsetsToTransaction() and Backwards Compatibility

Thanks, Boyang, I maintain a framework (Spring for Apache Kafka) that sits on top of the clients, and I would like to be able to support all broker versions. I don't have control over what brokers my users are using. You guys have done a great job since 0.10.2.0 (I think) of supporting older

Re: 2.5.0 Producer.sendOffsetsToTransaction() and Backwards Compatibility

Thanks for the question Gary. The reasoning for crash the new sendTxnOffsets API is because we don't want users to unconsciously violate the EOS guarantee. In your case, using this API with 2.4.1 is not supported anyway, so the upgrade path has to start from broker first to 2.5, and then client

Build failed in Jenkins: kafka-trunk-jdk11 #1315

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H32 (ubuntu) in workspace

Build failed in Jenkins: kafka-trunk-jdk11 #1314

See Changes: [github] MINOR: System test ZooKeeper upgrades (#8384) -- [...truncated 2.97 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[DISCUSS] KIP-588: Allow producers to recover gracefully from transaction timeouts

Hey there, I would like to start discussion for KIP-588: https://cwiki.apache.org/confluence/display/KAFKA/KIP-588%3A+Allow+producers+to+recover+gracefully+from+transaction+timeouts which aims to improve Producer resilience to transaction timeout due to transient system gaps. Best, Boyang

2.5.0 Producer.sendOffsetsToTransaction() and Backwards Compatibility

Is there any way to determine the broker version in the kafka-clients? I need to determine whether I can use the new sendOffsetsToTransaction with ConsumerGroupMetadata or use the old one. If I use the new API with a 2.4.1 broker, I get UpsupportedVersionException: Attempted to write a

[jira] [Created] (KAFKA-9810) Document Connect Root REST API on /

Konstantine Karantasis created KAFKA-9810: - Summary: Document Connect Root REST API on / Key: KAFKA-9810 URL: https://issues.apache.org/jira/browse/KAFKA-9810 Project: Kafka Issue

[DISCUSS] KIP-587 Suppress detailed responses for handled exceptions in security-sensitive environments

Hello All! I’ve created the following KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-587:+Suppress+detailed+responses+for+handled+exceptions+in+security-sensitive+environments The PR that originated this discussion, is here: https://github.com/apache/kafka/pull/8355 It is based on

[jira] [Created] (KAFKA-9809) Shrink transaction timeout for Streams

Boyang Chen created KAFKA-9809: -- Summary: Shrink transaction timeout for Streams Key: KAFKA-9809 URL: https://issues.apache.org/jira/browse/KAFKA-9809 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS] KIP-584: Versioning scheme for features

Thanks for the reply. The only remaining question is the propagation path. KIP-500 only restricts `write access` to the controller, in a sense that brokers in the pre-KIP-500 world could still listen to Zookeeper notifications. Thus, we are open to discuss the engineering effort to go through

[jira] [Created] (KAFKA-9808) Refactor State Store Hierarchy

Richard Yu created KAFKA-9808: - Summary: Refactor State Store Hierarchy Key: KAFKA-9808 URL: https://issues.apache.org/jira/browse/KAFKA-9808 Project: Kafka Issue Type: Improvement

Build failed in Jenkins: kafka-trunk-jdk8 #4394

See Changes: [wangguoz] HOTFIX: remove redundant check for QueryableStateIntegrationTest [github] MINOR: Fix typo in version 2.4.1 of kafka folder in Dockerfile (#8393)

Rpm spec file for kafka

Hello, I wanted to build a rpm from scratch. Is there a spec file anyone could guide me to ? I can see ones for kafka-rest and schema-registry . it would be of great help if I could get for kafka as well. I know there are rpms available but I would prefer it to build on my own Thanks,

Re: [DISCUSS] KIP-585: Conditional SMT

Hi Chris and Sönke, Using the numbering from Chris's email... 1. That's a good point, I'll see what is needed to make that work. 2. I'm happy enough to add support for "and" and "or" as part of this KIP if people can see a need for it. In a similar vein, I was wondering about whether it would

[jira] [Created] (KAFKA-9807) Race condition updating high watermark allows reads above LSO

Jason Gustafson created KAFKA-9807: -- Summary: Race condition updating high watermark allows reads above LSO Key: KAFKA-9807 URL: https://issues.apache.org/jira/browse/KAFKA-9807 Project: Kafka

[jira] [Created] (KAFKA-9806) Unable to consume when __consumer_offsets is created under insufficient cluster ACLs

Paolo Moriello created KAFKA-9806: - Summary: Unable to consume when __consumer_offsets is created under insufficient cluster ACLs Key: KAFKA-9806 URL: https://issues.apache.org/jira/browse/KAFKA-9806

Build failed in Jenkins: kafka-trunk-jdk11 #1313

See Changes: [wangguoz] HOTFIX: remove redundant check for QueryableStateIntegrationTest [github] MINOR: Fix typo in version 2.4.1 of kafka folder in Dockerfile (#8393)

Re: [DISCUSS] KIP-585: Conditional SMT

Hi Tom, thanks for your detailed explanation! I may have mis-phrased my mail a little bit regarding the definition of conditions and caused you extra effort with that, sorry! I understood the not condition and its relationship to the has-header condition, I was just wondering whether the "" in

Re: [DISCUSS] KIP-579: new exception on min.insync.replicas > replication.factor

Hi, Thanks a lot for your feedback, I really appreciate your help on this. Given what you suggested, I will take some time to update the kip with a proposal to make invalid configuration requests FAIL. This involves checking multiple code paths, as James was saying, to eg.: validate topic

Re: [VOTE] KIP-579: new exception on min.insync.replicas > replication.factor

Hello, I'm suspending the vote to continue the discussion in the related email thread. Will resume the vote when that is completed. Paolo On Tue, 31 Mar 2020 at 17:31, Ismael Juma wrote: > I commented in the discussion thread. I think the rejected alternative of > validating during topic

[jira] [Created] (KAFKA-9805) Running MirrorMaker in a Connect cluster,but the task not running

ZHAO GH created KAFKA-9805: -- Summary: Running MirrorMaker in a Connect cluster,but the task not running Key: KAFKA-9805 URL: https://issues.apache.org/jira/browse/KAFKA-9805 Project: Kafka Issue

[jira] [Created] (KAFKA-9804) Extract ConsumerPerform config into one file

jiamei xie created KAFKA-9804: - Summary: Extract ConsumerPerform config into one file Key: KAFKA-9804 URL: https://issues.apache.org/jira/browse/KAFKA-9804 Project: Kafka Issue Type: Bug

Build failed in Jenkins: kafka-trunk-jdk8 #4393

See Changes: [github] MINOR: Improve close tests of caching state store (#8386) [github] MINOR: Rename TopicCommandTest (#8398) [github] KAFKA-9748: extend EosIntegrationTest for EOS-beta (#8331)