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

See Changes: [github] KAFKA-8995: delete all topics before recreating (#8208) -- [...truncated 1.71 MB...] unit.kafka.cluster.AssignmentStateTest >

[jira] [Created] (KAFKA-9640) Allow use of RDMA for publishing, replicating, and consuming log entries

Steve Byan created KAFKA-9640: - Summary: Allow use of RDMA for publishing, replicating, and consuming log entries Key: KAFKA-9640 URL: https://issues.apache.org/jira/browse/KAFKA-9640 Project: Kafka

Re: [VOTE] KIP-557: Add emit on change support for Kafka Streams

Thanks, Guozhang and Bruno! 2) I had a similar though to both of you about the metrics, but I ultimately came out with a conclusion like Bruno's. These aren't dropped invalid records, they're intentionally dropped, valid, but unnecessary, updates. A "warning" for this case definitely seems wrong,

Re: [VOTE] KIP-557: Add emit on change support for Kafka Streams

Hi Bruno, John: 1) That makes sense. If we consider them to be node-specific metrics that only applies to a subset of built-in processor nodes that are irrelevant to alert-relevant metrics (just like suppression-emit (rate | total)), they'd better be per-node instead of per-task and we would not

[jira] [Resolved] (KAFKA-9106) metrics exposed via JMX shoud be configurable

[ https://issues.apache.org/jira/browse/KAFKA-9106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xavier Léauté resolved KAFKA-9106. -- Fix Version/s: 2.5.0 Resolution: Fixed > metrics exposed via JMX shoud be configurable

[jira] [Created] (KAFKA-9641) Kafka Client doesn't handle timeout exceptions for partition fetch requests

Madhav Kelkar created KAFKA-9641: Summary: Kafka Client doesn't handle timeout exceptions for partition fetch requests Key: KAFKA-9641 URL: https://issues.apache.org/jira/browse/KAFKA-9641 Project:

[jira] [Created] (KAFKA-9643) AlterConfigsRequest and IncrementalAlterConfigsRequest use conflicting type names

Dominic Evans created KAFKA-9643: Summary: AlterConfigsRequest and IncrementalAlterConfigsRequest use conflicting type names Key: KAFKA-9643 URL: https://issues.apache.org/jira/browse/KAFKA-9643

Re: Subject: [VOTE] 2.4.1 RC0

Hi, I ran: $ https://github.com/elalonde/kafka/blob/master/bin/verify-kafka-rc.sh 2.4.1 https://home.apache.org/~bbejeck/kafka-2.4.1-rc0 All checksums and signatures are

[jira] [Created] (KAFKA-9642) "BigDecimal(double)" should not be used

Soontaek Lim created KAFKA-9642: --- Summary: "BigDecimal(double)" should not be used Key: KAFKA-9642 URL: https://issues.apache.org/jira/browse/KAFKA-9642 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-557: Add emit on change support for Kafka Streams

Hi all, Thanks for the discussion! @Guozhang, I will make the corresponding changes to the KIP (i.e. renaming the sensor and adding some notes). With the current state of things, we are very close. Just need that one last binding vote. @Matthias J. Sax It would be ideal if we can also get

[jira] [Created] (KAFKA-9644) incrementalAlterConfigs OpType.APPEND on unset property fails with NullPointerException

Steve Rodrigues created KAFKA-9644: -- Summary: incrementalAlterConfigs OpType.APPEND on unset property fails with NullPointerException Key: KAFKA-9644 URL: https://issues.apache.org/jira/browse/KAFKA-9644

Re: [VOTE] KIP-570: Add leader epoch in StopReplicaRequest

Hi, David, Thanks for the KIP. +1 from me too. Just one comment below. 1. Regarding the sentinel leader epoch to indicate topic deletion, it seems that we need to use a different sentinel value to indicate that the leader epoch is not present when the controller is still on the old version

[jira] [Created] (KAFKA-9645) Records could not find corresponding partition/task

Boyang Chen created KAFKA-9645: -- Summary: Records could not find corresponding partition/task Key: KAFKA-9645 URL: https://issues.apache.org/jira/browse/KAFKA-9645 Project: Kafka Issue Type:

RE: Issue in retention with compact,delete cleanup policy

Bubbling this up to understand if anyone else are in similar use case. -Original Message- From: Koushik Chitta Sent: Sunday, February 23, 2020 1:35 PM To: us...@kafka.apache.org; dev@kafka.apache.org Subject: [EXTERNAL] Issue in retention with compact,delete cleanup policy Hi, I have

Build failed in Jenkins: kafka-2.4-jdk8 #163

See Changes: -- [...truncated 5.57 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldPassIfKeyAndValueAndTimestampIsEqualForCompareKeyValueTimestampWithProducerRecord

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

Hi, Guozhang Thanks a lot for the advice, that make sense! I have updated the KIP page with the operational steps of StreamsResetter. Thanks! Feyman -- 发件人：Guozhang Wang 发送时间：2020年3月3日(星期二) 14:22 收件人：dev ; feyman2009 主　

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

Thanks, +1 from me (binding). On Tue, Mar 3, 2020 at 9:39 PM feyman2009 wrote: > Hi, Guozhang > Thanks a lot for the advice, that make sense! > I have updated the KIP page with the operational steps of > StreamsResetter. > > Thanks! > Feyman > >

Build failed in Jenkins: kafka-2.4-jdk8 #162

See Changes: [wangguoz] KAFKA-8995: delete all topics before recreating (#8208) -- [...truncated 5.57 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [DISCUSS] KAFKA-4680: min.insync.replica can be set > replication factor

Thanks Paolo for taking care of this. I think option (3) would be the closest to iso-functionality. I wonder how useful it could be to always add the replication factor of the topic in the error message [1] versus returning a modified one fitted for this specific case? [1]

Re: Add a customized logo for Kafka Streams

Hi Boyang Great idea, that would help in some discussions. To throw in a first idea: https://imgur.com/a/UowXaMk best regards Patrik On Mon, 2 Mar 2020 at 18:23, Boyang Chen wrote: > Hey Apache Kafka committers and community folks, > > over the years Kafka Streams has been widely adopted and

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

See Changes: [wangguoz] KAFKA-8995: delete all topics before recreating (#8208) -- [...truncated 5.86 MB...] org.apache.kafka.streams.TestTopicsTest > testNonUsedOutputTopic

[jira] [Created] (KAFKA-9638) Do not trigger REBALANCING when specific exceptions occur in Kafka Streams

Levani Kokhreidze created KAFKA-9638: Summary: Do not trigger REBALANCING when specific exceptions occur in Kafka Streams Key: KAFKA-9638 URL: https://issues.apache.org/jira/browse/KAFKA-9638

Re: [VOTE] KIP-557: Add emit on change support for Kafka Streams

Hi Guozhang, I also had the same thought about using the existing "dropped-records" metrics. However, I think in this case it would be better to use a new metric because dropped idempotent updates is an optimization, they do not represent missed records. The dropped idempotent updates in general

[jira] [Created] (KAFKA-9639) Task is not killed despite being dead

Stéphane Derosiaux created KAFKA-9639: - Summary: Task is not killed despite being dead Key: KAFKA-9639 URL: https://issues.apache.org/jira/browse/KAFKA-9639 Project: Kafka Issue Type: