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

See Changes: [github] KAFKA-10083: fix failed -- [...truncated 3.13 MB...] org.apache.kafka.streams.TestTopicsTest > testValue STARTED

Re: [DISCUSS] KIP-616: Rename implicit Serdes instances in kafka-streams-scala

Hi, John Thanks for pointing that out. I expressed my thoughts about KIP-513 and its connection to KIP-616 in the KIP-513 mail list. - Yuriy On Sun, May 31, 2020 at 1:26 AM John Roesler wrote: > Hi Yuriy, > > I was just looking back at KIP-513, and I’m wondering if there’s any > overlap we

Re: [DISCUSS] KIP-513: Distinguish between Key and Value serdes in scala wrapper library for kafka streams

Hi. I'm the author of the KIP-616. I got acquainted with the KIP-513 and I think overall it's a good idea. But I think workaround only on the scala side is not enough. We could consider moving a bit further and change serde hierarchy on the java side to something like this: KeySerializer-↘

Re: [DISCUSS] KIP-619 Deprecate ConsumerConfig#addDeserializerToConfig(Properties, Deserializer, Deserializer) and ProducerConfig#addSerializerToConfig(Properties, Serializer, Serializer)

Hi Chia, Hope you are doing well. I already took KIP-619 as my KIP identification number. Could you change your KIP id? Thank you. Best, - Cheng > On May 31, 2020, at 8:08 PM, Chia-Ping Tsai wrote: > > hi All, > > This KIP plans to deprecate two unused methods without replacement. > > All

[jira] [Created] (KAFKA-10088) The ephemeral node [%s] at %s has gone away while reading it

jinshaoling created KAFKA-10088: --- Summary: The ephemeral node [%s] at %s has gone away while reading it Key: KAFKA-10088 URL: https://issues.apache.org/jira/browse/KAFKA-10088 Project: Kafka

[jira] [Created] (KAFKA-10087) Properly throw LogTruncation exception from OffsetForLeaderEpoch future

Boyang Chen created KAFKA-10087: --- Summary: Properly throw LogTruncation exception from OffsetForLeaderEpoch future Key: KAFKA-10087 URL: https://issues.apache.org/jira/browse/KAFKA-10087 Project: Kafka

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

See Changes: [github] KAFKA-9945: TopicCommand should support --if-exists and --if-not-exists -- [...truncated 3.13 MB...]

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

See Changes: [github] KAFKA-9945: TopicCommand should support --if-exists and --if-not-exists -- [...truncated 3.16 MB...]

Build failed in Jenkins: kafka-2.6-jdk8 #12

See Changes: [ismael] KAFKA-9320: Enable TLSv1.3 by default (KIP-573) (#8695) [cmccabe] KAFKA-9945: TopicCommand should support --if-exists and --if-not-exists --

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

See Changes: [github] KAFKA-9320: Enable TLSv1.3 by default (KIP-573) (#8695) [github] KAFKA-9945: TopicCommand should support --if-exists and --if-not-exists --

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

See Changes: [github] KAFKA-9320: Enable TLSv1.3 by default (KIP-573) (#8695) -- [...truncated 3.13 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: [VOTE] KIP-589: Add API to update Replica state in Controller

+1 I agree with Guozhang that broker epoch will need a separate discussion. Thanks! Jason On Thu, May 28, 2020 at 9:34 AM Guozhang Wang wrote: > David, thanks for the KIP. I'm +1 on it as well. > > One note is that in post-ZK world, we would need a different way to get > broker epoch since it

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

See Changes: [github] KAFKA-9320: Enable TLSv1.3 by default (KIP-573) (#8695) -- [...truncated 3.16 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Resolved] (KAFKA-9945) TopicCommand should support --if-exists and --if-not-exists when --bootstrap-server is used

[ https://issues.apache.org/jira/browse/KAFKA-9945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-9945. - Fix Version/s: 2.6.0 Reviewer: Colin McCabe Resolution: Fixed > TopicCommand

Re: KIP-599: Throttle Create Topic, Create Partition and Delete Topic Operations

Hi David, Thanks for the KIP. A few questions below: 1) The KIP says: *`Typically, applications tend to send one request to create all the topics that they need`*. What would the point of throttling be in this case? If there was a user quota for the principal used by that application, wouldn't

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

See Changes: [github] KAFKA-10082: Fix the failed testMultiConsumerStickyAssignment (#8777) -- [...truncated 3.15 MB...]

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

See Changes: [wangguoz] MINOR: Remove unused variable to fix spotBugs failure (#8779) [wangguoz] KAFKA-10082: Fix the failed testMultiConsumerStickyAssignment (#8777) --

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

See Changes: [wangguoz] MINOR: Remove unused variable to fix spotBugs failure (#8779) [wangguoz] KAFKA-10082: Fix the failed testMultiConsumerStickyAssignment (#8777) --

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

See Changes: [github] KAFKA-10082: Fix the failed testMultiConsumerStickyAssignment (#8777) -- [...truncated 3.14 MB...] org.apache.kafka.streams.TopologyTestDriverTest

[jira] [Created] (KAFKA-10086) Write Integration Test for StreamsTaskAssignor/HighAvailabilityTaskAssignor

John Roesler created KAFKA-10086: Summary: Write Integration Test for StreamsTaskAssignor/HighAvailabilityTaskAssignor Key: KAFKA-10086 URL: https://issues.apache.org/jira/browse/KAFKA-10086 Project:

[jira] [Created] (KAFKA-10085) Compute lag correctly for optimized source changelogs

Sophie Blee-Goldman created KAFKA-10085: --- Summary: Compute lag correctly for optimized source changelogs Key: KAFKA-10085 URL: https://issues.apache.org/jira/browse/KAFKA-10085 Project: Kafka

Build failed in Jenkins: kafka-2.6-jdk8 #11

See Changes: [wangguoz] MINOR: Remove unused variable to fix spotBugs failure (#8779) [wangguoz] KAFKA-10082: Fix the failed testMultiConsumerStickyAssignment (#8777) --

[jira] [Created] (KAFKA-10084) System test failure: StreamsEosTest.test_failure_and_recovery_complex

John Roesler created KAFKA-10084: Summary: System test failure: StreamsEosTest.test_failure_and_recovery_complex Key: KAFKA-10084 URL: https://issues.apache.org/jira/browse/KAFKA-10084 Project: Kafka

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

See Changes: [github] MINOR: Remove unused variable to fix spotBugs failure (#8779) [github] KAFKA-10082: Fix the failed testMultiConsumerStickyAssignment (#8777) --

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

See Changes: [github] MINOR: Remove unused variable to fix spotBugs failure (#8779) -- [...truncated 3.15 MB...]

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

See Changes: [github] MINOR: Remove unused variable to fix spotBugs failure (#8779) -- [...truncated 3.13 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Resolved] (KAFKA-9987) Improve sticky partition assignor algorithm

[ https://issues.apache.org/jira/browse/KAFKA-9987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman resolved KAFKA-9987. Fix Version/s: 2.5.1 2.4.2 2.6.0

[jira] [Resolved] (KAFKA-8723) flaky test LeaderElectionCommandTest#testAllTopicPartition

[ https://issues.apache.org/jira/browse/KAFKA-8723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski resolved KAFKA-8723. Resolution: Fixed > flaky test LeaderElectionCommandTest#testAllTopicPartition >

Build failed in Jenkins: kafka-2.6-jdk8 #10

See Changes: [wangguoz] MINOR: ChangelogReader should poll for duration 0 for standby restore -- [...truncated 335.32 KB...] kafka.admin.TopicCommandWithZKClientTest >

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Thanks Jun for your comments. >100. It would be useful to provide more details on how those apis are used. >Otherwise, it's kind of hard to really assess whether the new apis are >sufficient/redundant. A few examples below. We will update the wiki and let you know. >100.1 deleteRecords seems

Re: [VOTE] KIP-518: Allow listing consumer groups per state

Thanks for the update, Mickael. Changes look good to me. On Fri, May 29, 2020 at 11:39 AM Mickael Maison wrote: > Quick update: > While implementing the KIP, we made a couple of changes: > - Use regular fields instead of flexible fields. We had to bump the > protocol version to detect

Re: KIP-599: Throttle Create Topic, Create Partition and Delete Topic Operations

Hi Jun, Thanks for your reply. 10. I think that both options are likely equivalent from an accuracy point of view. If we put the implementation aside, conceptually, I am not convinced by the used based approach because resources don't have a clear owner in AK at the moment. A topic can be

[jira] [Created] (KAFKA-10083) fix failed testReassignmentWithRandomSubscriptionsAndChanges

Luke Chen created KAFKA-10083: - Summary: fix failed testReassignmentWithRandomSubscriptionsAndChanges Key: KAFKA-10083 URL: https://issues.apache.org/jira/browse/KAFKA-10083 Project: Kafka

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

See Changes: [github] MINOR: ChangelogReader should poll for duration 0 for standby restore -- [...truncated 1.74 MB...] org.apache.kafka.streams.TopologyTestDriverTest

Re: [VOTE] KIP-601: Configurable socket connection timeout in NetworkClient

Hi Cheng, Not sure if the discussion should move back to the DISCUSS thread. I have a few questions: 1) The KIP motivation says that in some cases `request.timeout.ms` doesn't timeout connections properly and as a result it takes 127s to detect a connection failure. This sounds like a bug rather

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

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

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

See Changes: [github] MINOR: ChangelogReader should poll for duration 0 for standby restore -- [...truncated 1.74 MB...] org.apache.kafka.streams.TopologyTestDriverTest

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

See Changes: [github] MINOR: ChangelogReader should poll for duration 0 for standby restore -- [...truncated 1.74 MB...] org.apache.kafka.streams.TopologyTestDriverTest

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

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

[jira] [Created] (KAFKA-10082) fix failed kafka.api.PlaintextConsumerTest.testMultiConsumerStickyAssignment

Luke Chen created KAFKA-10082: - Summary: fix failed kafka.api.PlaintextConsumerTest.testMultiConsumerStickyAssignment Key: KAFKA-10082 URL: https://issues.apache.org/jira/browse/KAFKA-10082 Project:

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

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

Build failed in Jenkins: kafka-2.6-jdk8 #9

See Changes: [wangguoz] KAFKA-9987: optimize sticky assignment algorithm for same-subscription [konstantine] MINOR: Code cleanup and assertion message fixes in Connect integration [matthias] Kafka-10064 Add