[jira] [Created] (KAFKA-9063) KAfka performance drops with number of topics even when producer is producing on one topic

Pradeep Bansal created KAFKA-9063: - Summary: KAfka performance drops with number of topics even when producer is producing on one topic Key: KAFKA-9063 URL: https://issues.apache.org/jira/browse/KAFKA-9063

[jira] [Created] (KAFKA-9064) Observe transient issue with kinit cimmand

Pradeep Bansal created KAFKA-9064: - Summary: Observe transient issue with kinit cimmand Key: KAFKA-9064 URL: https://issues.apache.org/jira/browse/KAFKA-9064 Project: Kafka Issue Type:

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

See Changes: [ismael] MINOR: Upgrade zk to 3.5.6 (#7544) [jason] KAFKA-9004; Prevent older clients from fetching from a follower (#7531) [jason] MINOR: Augment log4j to add generation number in performAssign

Build failed in Jenkins: kafka-2.3-jdk8 #130

See Changes: [bbejeck] Fix bug in AssignmentInfo#encode and add additional logging (#7545) -- [...truncated 2.93 MB...]

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

See Changes: [wangguoz] Explain the separate upgrade paths for consumer groups and Streams [rhauch] KAFKA-8340, KAFKA-8819: Use PluginClassLoader while statically --

Build failed in Jenkins: kafka-2.2-jdk8 #178

See Changes: [rhauch] KAFKA-8340, KAFKA-8819: Use PluginClassLoader while statically -- [...truncated 2.77 MB...] kafka.security.auth.ZkAuthorizationTest > testZkMigration

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

See Changes: [wangguoz] KAFKA-9000: fix flaky FK join test by using TTD (#7517) [wangguoz] KAFKA-8104: Consumer cannot rejoin to the group after rebalancing [matthias] KAFKA-8884: class cast exception improvement

Re: [DISCUSS] Apache Kafka 2.4.0 release

Hi all, The code freeze deadline has now passed and at this point only blockers will be allowed. We have three blockers for 2.4.0. I will move out most of the JIRAs that aren't currently being worked on. If you think any of the other JIRAs are critical to include in 2.4.0, please update the fix

Need to subscribe to dev group

Hi, I was using kafka for last 3 years. I wanna contribute to kafka. Please add me in the "dev@kafka.apache.org" Thanks, -- *Sriram G* *Tech*

Re: [VOTE] KIP-352: Distinguish URPs caused by reassignment

Hi Ismael, By Jason's suggestion we finally went with the originally voted proposal that is to include reassignment bytes in/out in replication bytes in/out and we discuss this when throttling is changed. Sorry for not updating this thread, I was busy with the code review. I'll get the KIP in

Jenkins build is back to normal : kafka-trunk-jdk11 #889

See

Re: [VOTE] 2.3.1 RC1

Hi David, Have merged the fix for https://issues.apache.org/jira/browse/KAFKA-8950 to the 2.3 branch as well, since it is a critical consumer issue. I set fix version to 2.3.2 & 2.4.0 in the JIRA since I wasn't sure we will have another RC for 2,3,1. But it will be good to get it in possible.

Jenkins build is back to normal : kafka-2.3-jdk8 #128

See

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

See Changes: [jason] KAFKA-7981; Add fetcher and log cleaner thread count metrics (#6514) [rhauch] KAFKA-8340, KAFKA-8819: Use PluginClassLoader while statically [bill] MINOR: Improve FK Join docs and optimize

[jira] [Resolved] (KAFKA-8950) KafkaConsumer stops fetching

[ https://issues.apache.org/jira/browse/KAFKA-8950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-8950. --- Fix Version/s: 2.3.2 2.4.0 Resolution: Fixed > KafkaConsumer stops

[jira] [Created] (KAFKA-9059) Implement MaxReassignmentLag

Viktor Somogyi-Vass created KAFKA-9059: -- Summary: Implement MaxReassignmentLag Key: KAFKA-9059 URL: https://issues.apache.org/jira/browse/KAFKA-9059 Project: Kafka Issue Type:

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

See Changes: [github] MINOR: Update Kafka Streams upgrade docs for KIP-444, KIP-470, KIP-471, [wangguoz] Explain the separate upgrade paths for consumer groups and Streams [rhauch] KAFKA-8340, KAFKA-8819: Use

Build failed in Jenkins: kafka-2.2-jdk8 #179

See Changes: [matthias] MINOR: log reason for fatal error in locking state dir (#7534) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment

Build failed in Jenkins: kafka-2.3-jdk8 #127

See Changes: [rhauch] KAFKA-8945/KAFKA-8947: Fix bugs in Connect REST extension API (#7392) [rhauch] KAFKA-8340, KAFKA-8819: Use PluginClassLoader while statically --

Re: KAFKA-8584: Support of ByteBuffer for bytes field implemented[Convert Kafka RPCs to use automatically generated code]

Hello. Is there something wrong with the PR? Do we need this ticket to be done? [2] If no, let's close both PR [1] and ticket. The design or implementation details were changed? If yes, can you, please, send a link where I can find details. [1] https://github.com/apache/kafka/pull/7342 [2]

[jira] [Resolved] (KAFKA-9004) Fetch from follower unintentionally allowed for old consumers

[ https://issues.apache.org/jira/browse/KAFKA-9004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9004. Resolution: Fixed > Fetch from follower unintentionally allowed for old consumers >

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Hi Guozhang, It's a fair point. For control records, I think it's a non-issue since they are tiny and not batched. So the only case where this might matter is large batch deletions. I think the size difference is not a major issue itself, but I think it's worth mentioning in the KIP the risk of

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Here's my understanding: when log compaction kicks in, the system time at the moment would be larger than the message timestamp to be compacted, so the modification on the batch timestamp would practically be increasing its value, and hence the deltas for each inner message would be negative to

Build failed in Jenkins: kafka-2.3-jdk8 #129

See Changes: [rajinisivaram] KAKFA-8950: Fix KafkaConsumer Fetcher breaking on concurrent disconnect -- [...truncated 2.93 MB...] kafka.log.LogValidatorTest >

[jira] [Reopened] (KAFKA-8700) Flaky Test QueryableStateIntegrationTest#queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reopened KAFKA-8700: -- Re-opening to further investigation cc [~cpettitt-confluent] > Flaky Test

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

See Changes: [cmccabe] MINOR: AbstractRequestResponse should be an interface (#7513) -- [...truncated 2.70 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

[jira] [Resolved] (KAFKA-8902) Benchmark cooperative vs eager rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-8902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Roesler resolved KAFKA-8902. - Resolution: Fixed I wrote a simple Streams application using the Processor API to update 10

[jira] [Resolved] (KAFKA-9058) Foreign Key Join should not require a queriable store

[ https://issues.apache.org/jira/browse/KAFKA-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-9058. Fix Version/s: 2.4.0 Resolution: Fixed > Foreign Key Join should not require a

Re: [VOTE] - KIP-213 (new vote) - Simplified and revised.

Hello all, While writing some new test cases for foreign key joins (as accepted in KIP-213), I realized that there was an oversight in the review process: we only proposed to add join methods that take a Materialized parameter. This poses an unnecessary burden on users who don't _need_ to

[jira] [Created] (KAFKA-9060) Publish BOMs for Kafka

Michael Holler created KAFKA-9060: - Summary: Publish BOMs for Kafka Key: KAFKA-9060 URL: https://issues.apache.org/jira/browse/KAFKA-9060 Project: Kafka Issue Type: Improvement

Re: [VOTE] - KIP-213 (new vote) - Simplified and revised.

Awesome. Thanks John for fixing this! On Thu, Oct 17, 2019 at 3:07 PM John Roesler wrote: > Hello all, > > While writing some new test cases for foreign key joins (as accepted > in KIP-213), I realized that there was an oversight in the review > process: we only proposed to add join methods

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

See Changes: [bbejeck] MINOR: Improve FK Join docs and optimize null-fk case (#7536) [wangguoz] KAFKA-9053: AssignmentInfo#encode hardcodes the LATEST_SUPPORTED_VERSION [wangguoz] KAFKA-8496: System test for

Re: [DISCUSS] KIP-535: Allow state stores to serve stale reads during rebalance

Looks like we are covering ground :) >>Only if it is within a permissible range(say 1) we will serve from Restoring state of active. +1 on having a knob like this.. My reasoning is as follows. Looking at the Streams state as a read-only distributed kv store. With num_standby = f , we should

Re: [DISCUSS] Apache Kafka 2.4.0 release

Just FYI: There was also https://issues.apache.org/jira/browse/KAFKA-9058 that I just merged. -Matthias On 10/17/19 7:59 AM, Manikumar wrote: > Hi all, > > The code freeze deadline has now passed and at this point only blockers > will be allowed. > We have three blockers for 2.4.0. I will

Build failed in Jenkins: kafka-2.2-jdk8 #182

See Changes: [bill] Fix bug in AssignmentInfo#encode and add additional logging (#7545) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment

Build failed in Jenkins: kafka-2.1-jdk8 #238

See Changes: [bill] Fix bug in AssignmentInfo#encode and add additional logging (#7545) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment

Build failed in Jenkins: kafka-2.2-jdk8 #183

See Changes: -- Started by user rhauch Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H37 (ubuntu xenial) in workspace

[DISCUSS] KIP-539: Implement mechanism to flush out records in low volume suppression buffers

Hi all, I wish to discuss this KIP which would help us in resolving some issues we have with suppression buffers. Below is the link: https://cwiki.apache.org/confluence/display/KAFKA/KIP-539%3A+Implement+mechanism+to+flush+out+records+in+low+volume+suppression+buffers @John Roesler if you have

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

See Changes: [github] MINOR: AbstractRequestResponse should be an interface (#7513) [jason] KAFKA-9004; Prevent older clients from fetching from a follower (#7531) [github] MINOR: Upgrade zk to 3.5.6 (#7544)

[jira] [Created] (KAFKA-9062) RocksDB writes may stall after bulk loading lots of state

Sophie Blee-Goldman created KAFKA-9062: -- Summary: RocksDB writes may stall after bulk loading lots of state Key: KAFKA-9062 URL: https://issues.apache.org/jira/browse/KAFKA-9062 Project: Kafka

Build failed in Jenkins: kafka-2.2-jdk8 #180

See Changes: -- Started by user rhauch Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H27 (ubuntu) in workspace

Re: [DISCUSS] KIP-399: Extend ProductionExceptionHandler to cover serialization exceptions

I have read through the logs and I am of the opinion that while we should not let the store and the change Log diverge. However, it is not obvious how we would be able to do that and allow the custom serializer to effect that topic. In order to get around this we can create a shell around the

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Good catch I updated that. I have made a PR for this KIP I then am splitting it into 3 parts, first cogroup for a key-value store ( here ), then for a timeWindowedStore, and then a sessionWindowedStore + ensuring partitioning. Walker On Tue, Oct 15,

Build failed in Jenkins: kafka-2.2-jdk8 #181

See Changes: -- Started by user rhauch Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H33 (ubuntu) in workspace

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Thanks for the reply Jason. On Thu, Oct 17, 2019 at 10:40 AM Jason Gustafson wrote: > Hi Guozhang, > > It's a fair point. For control records, I think it's a non-issue since they > are tiny and not batched. So the only case where this might matter is large > batch deletions. I think the size

[jira] [Resolved] (KAFKA-8728) Flaky Test KTableSourceTopicRestartIntegrationTest #shouldRestoreAndProgressWhenTopicWrittenToDuringRestorationWithEosDisabled

[ https://issues.apache.org/jira/browse/KAFKA-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8728. Resolution: Cannot Reproduce > Flaky Test KTableSourceTopicRestartIntegrationTest >

[jira] [Created] (KAFKA-9061) StreamStreamJoinIntegrationTest flaky test failures

Chris Pettitt created KAFKA-9061: Summary: StreamStreamJoinIntegrationTest flaky test failures Key: KAFKA-9061 URL: https://issues.apache.org/jira/browse/KAFKA-9061 Project: Kafka Issue

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Hi Guozhang, Jason, I've updated the KIP to include this warning as well. If there is anything else that we need for it, let me know. :) Otherwise, we should vote this KIP in. Cheers, Richard On Thu, Oct 17, 2019 at 10:41 AM Jason Gustafson wrote: > Hi Guozhang, > > It's a fair point. For

[jira] [Resolved] (KAFKA-9053) AssignmentInfo#encode hardcodes the LATEST_SUPPORTED_VERSION

[ https://issues.apache.org/jira/browse/KAFKA-9053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-9053. Resolution: Fixed > AssignmentInfo#encode hardcodes the LATEST_SUPPORTED_VERSION >