Timestamp check in Kafka TransactionMetadata

We have come across an issue where in FATAL messages are logged in the broker. FATAL kafka.coordinator.transaction.TransactionMetadata: TransactionMetadata(transactionalId=tx-id-1, producerId=96011, producerEpoch=51, txnTimeoutMs=6, state=CompleteCommit, pendingState=Some(Ongoing), topicPar

Re: [DISCUSS] KIP-552: Add interface to handle unused config

Personally, I think that adding a specify prefix for user configs would be the simplest fix. Kafka Streams and Kafka Connect could just use this prefix to avoid the false positive WARN logs. Hence, the KIP does not need to fix every false positive warning, it just changes the AbstractConfig about

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

See Changes: [github] KAFKA-9701: Add more debug log on client to reproduce the issue (#8272) -- [...truncated 5.89 MB...] org.apache.kafka.streams.internals.WindowStore

回复：回复：回复：[Vote] KIP-571: Add option to force remove members in StreamsResetter

Hi, Sophie For 1) Sorry, I found that my expression is kind of misleading, what I actually mean is: "if --force not specified, an exception saying there are still active members on broker side will be thrown and suggesting using StreamsResetter with --force", I just updated the KIP page.

Build failed in Jenkins: kafka-2.5-jdk8 #61

See Changes: [matthias] MINOR: Update Streams IQ JavaDocs to not point to a deprecated method -- [...truncated 2.89 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

[jira] [Created] (KAFKA-9709) add a confirm when kafka-server-stop.sh find multiple kafka instances to kill

qiang Liu created KAFKA-9709: Summary: add a confirm when kafka-server-stop.sh find multiple kafka instances to kill Key: KAFKA-9709 URL: https://issues.apache.org/jira/browse/KAFKA-9709 Project: Kafka

[jira] [Resolved] (KAFKA-9605) EOS Producer could throw illegal state if trying to complete a failed batch after fatal error

[ https://issues.apache.org/jira/browse/KAFKA-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9605. Resolution: Fixed > EOS Producer could throw illegal state if trying to complete a failed b

[jira] [Created] (KAFKA-9708) Connector does not prefer to use packaged classes during configuration

Greg Harris created KAFKA-9708: -- Summary: Connector does not prefer to use packaged classes during configuration Key: KAFKA-9708 URL: https://issues.apache.org/jira/browse/KAFKA-9708 Project: Kafka

[jira] [Created] (KAFKA-9707) InsertField.Key transformation does not apply to tombstone records

Greg Harris created KAFKA-9707: -- Summary: InsertField.Key transformation does not apply to tombstone records Key: KAFKA-9707 URL: https://issues.apache.org/jira/browse/KAFKA-9707 Project: Kafka

[jira] [Created] (KAFKA-9706) Flatten transformation fails when encountering tombstone event

Greg Harris created KAFKA-9706: -- Summary: Flatten transformation fails when encountering tombstone event Key: KAFKA-9706 URL: https://issues.apache.org/jira/browse/KAFKA-9706 Project: Kafka Iss

Jira Cleanup

All, I left a few comments on some old but still open jiras in an attempt to clean up a little bit. Since probably no one would notice these comments I thought I'd quickly list them here to give people a chance to check on them: KAFKA-1265 - SBT

[jira] [Resolved] (KAFKA-5972) Flatten SMT does not work with null values

[ https://issues.apache.org/jira/browse/KAFKA-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-5972. Resolution: Fixed > Flatten SMT does not work with null values > --

[jira] [Resolved] (KAFKA-1292) Command-line tools should print what they do as part of their usage command

[ https://issues.apache.org/jira/browse/KAFKA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sönke Liebau resolved KAFKA-1292. - Resolution: Fixed This has been implemented by now, I do believe within the linked ticket. > Com

Re: Add a customized logo for Kafka Streams

Just to throw another proposal out there and inspire some debate, here's a similar-but-different idea (inspired by John + some sketches I found on google): *~~ See attachment, inlined image is too large for the mailing list ~~* This one's definitely more fun, my only concern is that it doesn't re

Re: [DISCUSS] KIP-519: Make SSL context/engine configuration extensible

Thanks Rajini. Sounds good. I'll make changes and update this thread. On Wed, Mar 11, 2020 at 6:41 AM Rajini Sivaram wrote: > Hi Maulin, > > I have reviewed the PR and left some comments, can you turn it into a PR > for https://github.com/apache/kafka? It looks good overall. > > We pass all conf

[jira] [Created] (KAFKA-9705) (Incremental)AlterConfig should be propagated from Controller in bridge release

Boyang Chen created KAFKA-9705: -- Summary: (Incremental)AlterConfig should be propagated from Controller in bridge release Key: KAFKA-9705 URL: https://issues.apache.org/jira/browse/KAFKA-9705 Project: Ka

Re: Re: [DISCUSS] KIP-500: Replace ZooKeeper with a Self-Managed Metadata Quorum

Hi Vijay, The current progress is tracked under the ticket https://issues.apache.org/jira/browse/KAFKA-9119 as sub-tasks. The first milestone would be moving off all admin request handling out of ZK and let them to talk to brokers. Guozhang On Wed, Mar 11, 2020 at 8:23 AM vijay gupta wrote: >

RE: Re: [DISCUSS] KIP-500: Replace ZooKeeper with a Self-Managed Metadata Quorum

Hi, What’s the latest status on this JIRA? Regards, Vijay On 2019/11/06 15:07:03 Viktor Somogyi-Vass wrote: > Hi Elmahdi, > > I've added the JIRA to the KIP (and also below) where you can track the > progress (but more subtask will come as the current ones don't represent > the full work to be

Re: [DISCUSS] KIP-552: Add interface to handle unused config

Long time no see, was on holiday 🇳🇿. Thread got an interesting twist into reporting and fixing every single warning individually, which is outside of my capacity. As I mentioned in the KIP and also as highlighted by Patric - you don't have to do anything extraordinary to get these warnings, you ju

Re: Feature request for 'prefixless' topic mirroring

Hello Marcin, actually KIP-382 includes LegacyReplicationPolicy (not yet released) which is similar to your PrefixlessReplicationPolicy and the MigrationReplicationPolicy mentioned. I don't think these are hacky, though maybe the documentation could better address what to do when a method doesn't n

[RESULTS] [VOTE] Release Kafka version 2.4.1 UPDATE

Previously I erroneously reported the vote with 4 PMC +1s. I thought one of the voters was also a PMC member. But since there are still 3 PMC + 1s, the passing vote for this release is still valid. This vote passes with 10 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members (in voti

Re: [DISCUSS] KIP-519: Make SSL context/engine configuration extensible

Hi Maulin, I have reviewed the PR and left some comments, can you turn it into a PR for https://github.com/apache/kafka? It looks good overall. We pass all configs to other plugins, so we can do the same here. That would be safer than assuming that all custom SSL-related configs start with `ssl.`

Has restarted broker caught up?

Hi. What is the idiomatic / correct way to know that a restarted broker in an existing Kafka cluster has caught up to all the leaders for the partitions it hosts? Is there a specific JMX metric published either by the leader / follower that we can monitor? Ideally, the metric would have the follo

Feature request for 'prefixless' topic mirroring

Dear All, I would like to raise a feature request for ‘prefixless’ topic mirroring with MirrorMaker2 (see detailed description below). As after quite a few tries I am not 100% sure, could you please confirm that by now the ‘prefixless’ mirroring is not supported and that my feature request is val

[jira] [Created] (KAFKA-9704) z/OS won't let us resize file when mmap

Shuo Zhang created KAFKA-9704: - Summary: z/OS won't let us resize file when mmap Key: KAFKA-9704 URL: https://issues.apache.org/jira/browse/KAFKA-9704 Project: Kafka Issue Type: Task Co

[jira] [Created] (KAFKA-9703) ProducerBatch.split takes up too many resources if the bigBatch is huge

jiamei xie created KAFKA-9703: - Summary: ProducerBatch.split takes up too many resources if the bigBatch is huge Key: KAFKA-9703 URL: https://issues.apache.org/jira/browse/KAFKA-9703 Project: Kafka

[jira] [Created] (KAFKA-9702) Suspected memory leak

Nishant Ranjan created KAFKA-9702: - Summary: Suspected memory leak Key: KAFKA-9702 URL: https://issues.apache.org/jira/browse/KAFKA-9702 Project: Kafka Issue Type: Bug Components: c