Build failed in Jenkins: kafka-trunk-jdk14 #58

See Changes: [github] KAFKA-9946; Partition deletion event should only be sent if deletion was -- [...truncated 3.08 MB...] org.apache.kafka.streams.TopologyTestDriverTes

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

See Changes: [github] KAFKA-9946; Partition deletion event should only be sent if deletion was -- [...truncated 3.08 MB...] org.apache.kafka.streams.TopologyTestDriverT

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

See Changes: [github] KAFKA-9946; Partition deletion event should only be sent if deletion was -- [...truncated 3.06 MB...] org.apache.kafka.streams.TopologyTestDriverT

Re: [DISCUSS] Kafka 3.0

IMO a bridge release, or one that you have to upgrade to before upgrading to the breaking release should be numbered as the last of the 2.x series... In other words, it's acceptable to say "before upgrading to 3.0, first upgrade to 2.9" but it's very unexpected to say "before upgrading to 3.1, fir

Build failed in Jenkins: kafka-trunk-jdk14 #57

See Changes: [github] MINOR: Improve TopologyTestDriver JavaDocs (#8619) -- [...truncated 6.15 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldPunctuateIf

Jenkins build is back to normal : kafka-trunk-jdk8 #4503

See

[jira] [Resolved] (KAFKA-9946) KAFKA-9539/StopReplicaRequest deletePartition changes may cause premature topic deletion handling in controller

[ https://issues.apache.org/jira/browse/KAFKA-9946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9946. Resolution: Fixed > KAFKA-9539/StopReplicaRequest deletePartition changes may cause prematu

Re: [DISCUSS] KIP-596 Safely abort Producer transactions during application shutdown

Hey Matthias, I'm not sure I follow your question, the producer will not automatically close when there is fatal error IIUC. Boyang On Tue, May 5, 2020 at 6:16 PM 张祥 wrote: > Thanks for the comment Matthias. > > In fact, I cannot think of why we cannot close the producer no matter what. > On t

Re: [DISCUSS] KIP-596 Safely abort Producer transactions during application shutdown

Thanks for the comment Matthias. In fact, I cannot think of why we cannot close the producer no matter what. On the other hand, it is also okay to reuse the producer when the error is not fatal. @Guozhang Wang @Boyang Chen Matthias J. Sax 于2020年5月1日周五 上午7:52写道： > Thanks for the KIP. Make sen

[jira] [Created] (KAFKA-9961) Brokers may be left in an inconsistent state after reassignment

Dhruvil Shah created KAFKA-9961: --- Summary: Brokers may be left in an inconsistent state after reassignment Key: KAFKA-9961 URL: https://issues.apache.org/jira/browse/KAFKA-9961 Project: Kafka

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

See Changes: [github] MINOR: Improve TopologyTestDriver JavaDocs (#8619) -- [...truncated 3.08 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldThrowForMis

[DISCUSS] KIP-606: Add Metadata Context to MetricsReporter

Hi Everyone, I've published a KIP to address some shortcoming of our current metrics reporter interface. Would appreciate feedback. https://cwiki.apache.org/confluence/display/KAFKA/KIP-606%3A+Add+Metadata+Context+to+MetricsReporter Thank you, Xavier

[jira] [Created] (KAFKA-9960) Metrics Reporter should support additional context tags

Xavier Léauté created KAFKA-9960: Summary: Metrics Reporter should support additional context tags Key: KAFKA-9960 URL: https://issues.apache.org/jira/browse/KAFKA-9960 Project: Kafka Issue T

[jira] [Created] (KAFKA-9959) leastLoadedNode() does not provide a node fairly

Cheng Tan created KAFKA-9959: Summary: leastLoadedNode() does not provide a node fairly Key: KAFKA-9959 URL: https://issues.apache.org/jira/browse/KAFKA-9959 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-9958) Add a new method to AuthorizerServerInfo Interface

Jeff Huang created KAFKA-9958: - Summary: Add a new method to AuthorizerServerInfo Interface Key: KAFKA-9958 URL: https://issues.apache.org/jira/browse/KAFKA-9958 Project: Kafka Issue Type: Improv

[DISCUSS] KIP-608: Add a new method to AuthorizerServerInfo Interface

https://cwiki.apache.org/confluence/display/KAFKA/KIP-608+-+Add+a+new+method+to+AuthorizerServerInfo+Interface

Re: [DISCUSS] Kafka 3.0

> In 3.0 it sounds like nothing is breaking and our big change won't be > complete... so, what's the motivation for the major release? Exactly. Why would 3.1 be the breaking release? No one would expect everything to break going from 3.0 to 3.1 Ryanne On Tue, May 5, 2020 at 2:34 PM Gwen Shapira

Re: [DISCUSS] Kafka 3.0

It sounds like the decision to make the next release 3.0 is a bit arbitrary then? With Exactly Once, we announced 1.0 as one release after the one where EOS shipped, when we felt it was "ready" (little did we know... but that's another story). 2.0 was breaking due to us dropping Java 7. In 3.0 it

Re: Avro DeSerializeation Issue in Kafka Streams

When specific.avro.reader is set to true Deserializer tries to create the instance of the Class. The class name is formed by reading the schema (writer schema) from schema registry and concatenating the namespace and record name. It is trying to create that instance and it is not found in the c

Re: [DISCUSS] Kafka 3.0

I think there's a confusion regarding the "bridge release" proposed in KIP-500: should it be release "3.0" or be release "2.X" (i.e. the last minor release before 3.0). My understanding is that "3.0" would be the bridge release, i.e. it would not break any compatibility, but 3.1 potentially would,

[DISCUSS] Apache Kafka 2.6.0 release

Greetings! I'd like to volunteer to be release manager for the next time-based feature release which will be 2.6.0. I've published a release plan at https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=152113430, and have included all of the KIPs that are currently approved or actively

[jira] [Resolved] (KAFKA-6468) Replication high watermark checkpoint file read for every LeaderAndIsrRequest

[ https://issues.apache.org/jira/browse/KAFKA-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kyle Ambroff-Kao resolved KAFKA-6468. - Resolution: Fixed > Replication high watermark checkpoint file read for every LeaderAndIs

Re: [DISCUSS] KIP-554: Add Broker-side SCRAM Config API

Hi Colin, SCRAM is better than SASL PLAIN because it doesn't send the password over the wire in the clear. Presumably this property is important for some users who have chosen to use SCRAM. This proposal does send the password in the clear when setting the password. That doesn't mean it can't be u

Avro DeSerializeation Issue in Kafka Streams

Hi All, Currently, I'm working on a usecase wherein I have to deserialie an Avro object and convert to some other format of Avro. Below is the flow. DB -> Source Topic(Avro format) -> Stream Processor -> Target Topic (Avro as nested object). When I deserialize the message from the Source Topic,

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

See Changes: [manikumar] MINOR: MockAdminClient should return InvalidReplicationFactorException -- [...truncated 6.12 MB...] org.apache.kafka.streams.TopologyTestDriver

Re: [DISCUSS] KIP-589 Add API to Update Replica State in Controller

Hi Colin, Yeah, that makes sense, thanks. I was thinking, longer term, that there are other benefits to having the log dir information available to the controller. For example it would allow the possibility for CREATE_TOPIC requests to include the intended log dir for each replica. But that's obvi

Re: [DISCUSS] KIP-585: Conditional SMT

Hi, Again, reusing the existing numbering... 3) I had exactly the same thought. The reason I didn't already rename it was because : * Filter is not exactly wrong (by default it just filters out all the messages) * Filter is a useful hint about how it's intended to be used. But I don't have a st

[jira] [Resolved] (KAFKA-9731) Increased fetch request rate with leader selector due to HW propagation

[ https://issues.apache.org/jira/browse/KAFKA-9731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9731. Resolution: Fixed > Increased fetch request rate with leader selector due to HW propagation > -

Re: [DISCUSS] KIP-566: Add rebalance callbacks to ConsumerInterceptor

Bumping to get and get some attention on this KIP before initiating a vote. Using ConsumerInterceptor for its intended purpose quite difficult without this. On Mon, 2020-02-10 at 15:50 +, Thomas Becker wrote: [EXTERNAL EMAIL] Attention: This email was sent from outside TiVo. DO NOT CLICK an

[jira] [Created] (KAFKA-9957) Kafka Controller doesn't failover during hardware failure

Eric Ward created KAFKA-9957: Summary: Kafka Controller doesn't failover during hardware failure Key: KAFKA-9957 URL: https://issues.apache.org/jira/browse/KAFKA-9957 Project: Kafka Issue Type: B

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

See Changes: [github] KAFKA-9748: Add Streams eos-beta integration test (#8496) -- [...truncated 6.12 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldProc

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

See Changes: [wangguoz] HOTFIX: set correct numIterations in shouldAllowConcurrentAccesses [github] KAFKA-9731: Disable immediate fetch response for hw propagation if [github] KAFKA-9748: Add Streams eos-beta

Build failed in Jenkins: kafka-trunk-jdk14 #56

See Changes: [wangguoz] HOTFIX: set correct numIterations in shouldAllowConcurrentAccesses [github] KAFKA-9731: Disable immediate fetch response for hw propagation if [github] KAFKA-9748: Add Streams eos-beta in

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

See Changes: [github] MINOR: Clean up some test dependencies on ConfigCommand and TopicCommand -- [...truncated 2.46 MB...] org.apache.kafka.streams.processor.internal

Build failed in Jenkins: kafka-trunk-jdk14 #55

See Changes: [github] MINOR: Clean up some test dependencies on ConfigCommand and TopicCommand -- [...truncated 5.21 MB...] org.apache.kafka.connect.converters.ByteArray

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

See Changes: [wangguoz] HOTFIX: set correct numIterations in shouldAllowConcurrentAccesses [github] KAFKA-9731: Disable immediate fetch response for hw propagation if --

Re: [DISCUSS] KIP-604: Remove ZooKeeper Flags from the Administrative Tools

Thanks for making the changes Colin, lgtm! On Mon, 4 May 2020 at 23:13, Colin McCabe wrote: > Hi Sönke, > > You're right on both counts. Thanks for the corrections. > > Thinking about this more, I think we should just remove > kafka-preferred-replica-election.sh. It just duplicates > kafka-lea