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

See Changes: [jiangjie.qj] KAFKA-9703; Free up compression buffer after splitting a large batch [github] KAFKA-9838; Add log concurrency test and fix minor race condition

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Thanks Raymond and Colin for the detailed discussions! I totally agree with the rational here. The new `Envelope` RPC has been added to the KIP and the forwarding section logic has been revised, feel free to take another look. On Wed, Apr 15, 2020 at 5:19 PM Colin McCabe wrote: > Hi Boyang, > >

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

See Changes: [github] KAFKA-9864: Avoid expensive QuotaViolationException usage (#8477) [github] MINOR: Serialize state change logs for handling LeaderAndIsr and [github] KAFKA-9832: extend Kafka Streams EOS

Re: [ANNOUNCE] Apache Kafka 2.5.0

Thanks for running the release David. Congratulations to everyone involved. -Navinder Pal Singh Brar On Thursday, 16 April, 2020, 07:26:25 am IST, Konstantine Karantasis wrote: Thanks for driving the release David and congrats to all the contributors. Nicely done! Konstantine On

Re: [DISCUSS] KIP-594: Expose output topic names from TopologyTestDriver

Hi Andy, Thanks for the KIP! To Matthias’s concern, I have to agree that the motivation doesn’t build a particularly strong case for the KIP, and people often look back to these documents to understand why something was done, and done a particular way. So, it would be nice to flesh it out a

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

See

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

Hi everyone, I have opened a small KIP about safely aborting transaction during shutdown. I'd like to use this thread to discuss about it and any feedback is appreciated (sorry for earlier KIP number mistake). Here is a link to KIP-596 :

Re: [ANNOUNCE] Apache Kafka 2.5.0

Thanks for driving the release David and congrats to all the contributors. Nicely done! Konstantine On Wed, Apr 15, 2020 at 3:16 PM Randall Hauch wrote: > Thanks, David! > > Congratulations to the whole AK community, and thanks to everyone that > contributed! > > On Wed, Apr 15, 2020 at 4:47

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

Thanks for reminding, I will change my KIP number and start a new thread now. Kowshik Prakasam 于2020年4月16日周四 上午9:49写道： > Hi, > > It appears "KIP-594" is already taken. Please see this existing link: > >

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

Hi, It appears "KIP-594" is already taken. Please see this existing link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-594%3A+Expose+output+topic+names+from+TopologyTestDriver . To avoid a duplicate, please change your KIP number to pick the next available KIP number, as mentioned here:

[DISCUSS] KIP-594 Safely abort Producer transactions during application shutdown

Hi everyone, I have opened a small KIP about safely aborting transaction during shutdown. I'd like to use this thread to discuss about it and any feedback is appreciated. Here is a link to KIP-594 :

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

Hi Jun, Thanks for the feedback! I have addressed the comments in the KIP. > 200. In the validation section, there is still the text "*from* > {"max_version_level": > X} *to* {"max_version_level": X’}". It seems that it should say "from X to > Y"? (Kowshik): Done. I have reworded it a bit to

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

Hi Jun, Sorry the links were broken in my last response, here are the right links: 200. https://cwiki.apache.org/confluence/display/KAFKA/KIP-584%3A+Versioning+scheme+for+features#KIP-584:Versioning Scheme For Features-Validations

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

See Changes: [github] Kafka 9739: Fix for 2.5 branch (#8492) [matthias] KAFKA-9675: Fix bug that prevents RocksDB metrics to be updated (#8256) [matthias] KAFKA-9540: Move "Could not find the standby task while

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

See Changes: [gwen] MINOR: avoid autoboxing in FetchRequest.PartitionData.equals [github] MINOR: Eliminate unnecessary partition lookups (#8484) -- [...truncated 1.84

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Hi Boyang, I agree that we need a version bump on the request types we are going to forward. The new versions will be able to return the NOT_CONTROLLER error, and let the client do the retrying, which is what we typically prefer. The existing versions can't ever return NOT_CONTROLLER.

[jira] [Resolved] (KAFKA-9838) Add additional log concurrency test cases

[ https://issues.apache.org/jira/browse/KAFKA-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9838. Resolution: Fixed > Add additional log concurrency test cases >

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Hi Ismael, I agree that sending these requests through the controller will not work during the periods when there is no controller. However, those periods should be short-- otherwise we have bigger problems in the cluster. These requests are very infrequent because they are administrative

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

See Changes: [github] MINOR: Eliminate unnecessary partition lookups (#8484) [github] KAFKA-9864: Avoid expensive QuotaViolationException usage (#8477) [github] MINOR: Serialize state change logs for handling

[VOTE] KIP-594: Expose output topic names from TopologyTestDriver

Hey all, I would like to start the vote for KIP- 594 . Thanks, Andy

updates on Kafka Summit in 2020

Hi, Everyone, Here is an update on the upcoming Kafka Summit events in 2020. 1. Unfortunately, Kafka Summit London, originally planned on Apr 27/28, has been cancelled due to COVID-19. 2. Kafka Summit Austin (Aug 24/25) is still on. The CFP (

[jira] [Resolved] (KAFKA-9779) Add version 2.5 to streams system tests

[ https://issues.apache.org/jira/browse/KAFKA-9779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-9779. Fix Version/s: 2.6.0 Resolution: Fixed > Add version 2.5 to streams system tests >

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

Hi, Kowshik, Looks good to me now. Just a couple of minor things below. 200. In the validation section, there is still the text "*from* {"max_version_level": X} *to* {"max_version_level": X’}". It seems that it should say "from X to Y"? 110. Could we add that we need to document the bumped

Jenkins build is back to normal : kafka-2.5-jdk8 #94

See

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Hi Boyang, Thanks for the KIP. Have we considered that this reduces availability for these operations since we have a single Controller instead of the ZK quorum? Ismael On Fri, Apr 3, 2020 at 4:45 PM Boyang Chen wrote: > Hey all, > > I would like to start off the discussion for KIP-590, a

Re: [RESULTS] [VOTE] 2.5.0 RC3

Thanks for doing a fantastic job with this release, David. On Tue, Apr 14, 2020 at 11:15 AM David Arthur wrote: > Thanks everyone! The vote passes with 7 +1 votes (4 of which are binding) > and no 0 or -1 votes. > > 4 binding +1 votes from PMC members Manikumar, Jun, Colin, and Matthias > 1

Re: [ANNOUNCE] Apache Kafka 2.5.0

Thanks, David! Congratulations to the whole AK community, and thanks to everyone that contributed! On Wed, Apr 15, 2020 at 4:47 PM Sönke Liebau wrote: > Thanks David!! > > > On Wed, 15 Apr 2020 at 23:07, Bill Bejeck wrote: > > > David, > > > > Thanks for running the release! > > > > -Bill > >

Re: [ANNOUNCE] Apache Kafka 2.5.0

Thanks David!! On Wed, 15 Apr 2020 at 23:07, Bill Bejeck wrote: > David, > > Thanks for running the release! > > -Bill > > On Wed, Apr 15, 2020 at 4:45 PM Matthias J. Sax wrote: > > > Thanks for running the release David! > > > > -Matthias > > > > On 4/15/20 1:15 PM, David Arthur wrote: > > >

[jira] [Created] (KAFKA-9876) Implement Raft Protocol for Metadata Quorum

Jason Gustafson created KAFKA-9876: -- Summary: Implement Raft Protocol for Metadata Quorum Key: KAFKA-9876 URL: https://issues.apache.org/jira/browse/KAFKA-9876 Project: Kafka Issue Type:

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

Hi all, Thank you very much for all the insightful feedback! How do you feel about the KIP? Does the scope and the write up look OK to you, and is it time to call a vote? Cheers, Kowshik On Wed, Apr 15, 2020 at 1:08 PM Kowshik Prakasam wrote: > Hi Jun, > > Thank you for the suggestion! I

Re: [ANNOUNCE] Apache Kafka 2.5.0

David, Thanks for running the release! -Bill On Wed, Apr 15, 2020 at 4:45 PM Matthias J. Sax wrote: > Thanks for running the release David! > > -Matthias > > On 4/15/20 1:15 PM, David Arthur wrote: > > The Apache Kafka community is pleased to announce the release for Apache > > Kafka 2.5.0 >

Re: [ANNOUNCE] Apache Kafka 2.5.0

Thanks for running the release David! -Matthias On 4/15/20 1:15 PM, David Arthur wrote: > The Apache Kafka community is pleased to announce the release for Apache > Kafka 2.5.0 > > This release includes many new features, including: > > * TLS 1.3 support (1.2 is now the default) > * Co-groups

Re: [ANNOUNCE] Apache Kafka 2.5.0

Thanks David for taking this initiative, great work! On Wed, Apr 15, 2020 at 1:15 PM David Arthur wrote: > The Apache Kafka community is pleased to announce the release for Apache > Kafka 2.5.0 > > This release includes many new features, including: > > * TLS 1.3 support (1.2 is now the

[ANNOUNCE] Apache Kafka 2.5.0

The Apache Kafka community is pleased to announce the release for Apache Kafka 2.5.0 This release includes many new features, including: * TLS 1.3 support (1.2 is now the default) * Co-groups for Kafka Streams * Incremental rebalance for Kafka Consumer * New metrics for better operational

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

Hi Jun, Thank you for the suggestion! I have updated the KIP, please find my response below. > 200. I guess you are saying only when the allowDowngrade field is set, the > finalized feature version can go backward. Otherwise, it can only go up. > That makes sense. It would be useful to make that

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

See Changes: [gwen] MINOR: avoid autoboxing in FetchRequest.PartitionData.equals -- [...truncated 6.05 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

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

Hi Chris, I can ask the customer if they can disclose any additional information. I provided the information around "PCI-DSS" to give the community a flavor of the type of environment the customer was operating in. The current mode is /not/ insecure, I would agree with this. I would be willing

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

Hi Connor, I still would like to hear more about whether this feature is required for PCI-DSS or any other security certification. Nobody I talked to seemed to think that it was-- if there are certifications that would require this, it would be nice to know. However, I don't object to

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

Hi, Kowshik, 200. I guess you are saying only when the allowDowngrade field is set, the finalized feature version can go backward. Otherwise, it can only go up. That makes sense. It would be useful to make that clear when explaining the usage of the allowDowngrade field. In the validation

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

Hi Jun, Great question! Please find my response below. > 200. My understanding is that If the CLI tool passes the > '--allow-downgrade' flag when updating a specific feature, then a future > downgrade is possible. Otherwise, the feature is now downgradable. If so, I > was wondering how the

[jira] [Created] (KAFKA-9875) Flaky Test SuppressionDurabilityIntegrationTest.shouldRecoverBufferAfterShutdown[exactly_once]

Sophie Blee-Goldman created KAFKA-9875: -- Summary: Flaky Test SuppressionDurabilityIntegrationTest.shouldRecoverBufferAfterShutdown[exactly_once] Key: KAFKA-9875 URL:

[jira] [Resolved] (KAFKA-7484) Fix test SuppressionDurabilityIntegrationTest.shouldRecoverBufferAfterShutdown()

[ https://issues.apache.org/jira/browse/KAFKA-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman resolved KAFKA-7484. Resolution: Fixed > Fix test >

[jira] [Reopened] (KAFKA-7484) Fix test SuppressionDurabilityIntegrationTest.shouldRecoverBufferAfterShutdown()

[ https://issues.apache.org/jira/browse/KAFKA-7484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sophie Blee-Goldman reopened KAFKA-7484: failed on a PR with h3. Stacktrace java.lang.RuntimeException:

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

Hi, Kowshik, Thanks for the reply. Makes sense. Just one more question. 200. My understanding is that If the CLI tool passes the '--allow-downgrade' flag when updating a specific feature, then a future downgrade is possible. Otherwise, the feature is now downgradable. If so, I was wondering how

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

See

[jira] [Resolved] (KAFKA-8870) Prevent dirty reads of Streams state store from Interactive queries

[ https://issues.apache.org/jira/browse/KAFKA-8870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8870. Resolution: Duplicate > Prevent dirty reads of Streams state store from Interactive queries >

[jira] [Resolved] (KAFKA-9764) Deprecate Stream Simple benchmark

[ https://issues.apache.org/jira/browse/KAFKA-9764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-9764. Resolution: Fixed > Deprecate Stream Simple benchmark > - > >

[jira] [Resolved] (KAFKA-9793) Stream HandleAssignment should guarantee task close

[ https://issues.apache.org/jira/browse/KAFKA-9793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-9793. Resolution: Fixed > Stream HandleAssignment should guarantee task close >

[jira] [Resolved] (KAFKA-9873) DNS故障时服务处理线程hang住

[ https://issues.apache.org/jira/browse/KAFKA-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhang chao resolved KAFKA-9873. --- Resolution: Duplicate > DNS故障时服务处理线程hang住 > - > > Key: KAFKA-9873 >

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

See Changes: [github] KAFKA-9797; Fix -- [...truncated 3.04 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Created] (KAFKA-9874) broker can not work when use dns fault

para created KAFKA-9874: --- Summary: broker can not work when use dns fault Key: KAFKA-9874 URL: https://issues.apache.org/jira/browse/KAFKA-9874 Project: Kafka Issue Type: Bug Components:

[jira] [Resolved] (KAFKA-9797) Fix flaky system test TestSecurityRollingUpgrade.test_enable_separate_interbroker_listener

[ https://issues.apache.org/jira/browse/KAFKA-9797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-9797. --- Reviewer: Manikumar Resolution: Fixed > Fix flaky system test >

[jira] [Created] (KAFKA-9873) DNS故障时服务处理线程hang住

zhang chao created KAFKA-9873: - Summary: DNS故障时服务处理线程hang住 Key: KAFKA-9873 URL: https://issues.apache.org/jira/browse/KAFKA-9873 Project: Kafka Issue Type: Bug Components: core

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

See Changes: [gwen] MINOR: cleaner resume log message is misleading [github] [KAFKA-9826] Handle an unaligned first dirty offset during log cleaning. -- [...truncated

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

See Changes: [gwen] MINOR: cleaner resume log message is misleading [github] [KAFKA-9826] Handle an unaligned first dirty offset during log cleaning. -- [...truncated

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

See Changes: [github] KAFKA-8611: Refactor KStreamRepartitionIntegrationTest (#8470) -- [...truncated 6.08 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Resolved] (KAFKA-9664) Flaky Test KafkaStreamsTest#testStateThreadClose

[ https://issues.apache.org/jira/browse/KAFKA-9664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-9664. -- Resolution: Cannot Reproduce > Flaky Test KafkaStreamsTest#testStateThreadClose >

[jira] [Created] (KAFKA-9872) After restart kafka by a abnormal way，kafkaconsumer cannot read messages

Lee chen created KAFKA-9872: --- Summary: After restart kafka by a abnormal way，kafkaconsumer cannot read messages Key: KAFKA-9872 URL: https://issues.apache.org/jira/browse/KAFKA-9872 Project: Kafka

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

See Changes: [matthias] MINOR: Upgrade ducktape to 0.7.7 (#8487) -- [...truncated 7.05 MB...] org.apache.kafka.connect.transforms.TimestampConverterTest > testKey PASSED

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

See

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

See Changes: [matthias] MINOR: Upgrade ducktape to 0.7.7 (#8487) -- [...truncated 5.88 MB...] org.apache.kafka.streams.TopologyTestDriverTest >