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

See Changes: [github] MINOR: improve tests for TopologyTestDriver (#8631) [github] MINOR: Fix ProcessorContext JavaDocs and stream-time computation (#8603) [github] MINOR: Replace null with an actual value

[jira] [Created] (KAFKA-9985) Sink connector may exhaust broker when writing in DLQ

Mario Molina created KAFKA-9985: --- Summary: Sink connector may exhaust broker when writing in DLQ Key: KAFKA-9985 URL: https://issues.apache.org/jira/browse/KAFKA-9985 Project: Kafka Issue

[DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hey all, I'd like to kick off discussion on KIP-613 which aims to add end-to-end latency metrics to Streams. Please take a look: https://cwiki.apache.org/confluence/display/KAFKA/KIP-613%3A+Add+end-to-end+latency+metrics+to+Streams Cheers, Sophie

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

See

[jira] [Created] (KAFKA-9984) Should fail the subscription when pattern is empty

Boyang Chen created KAFKA-9984: -- Summary: Should fail the subscription when pattern is empty Key: KAFKA-9984 URL: https://issues.apache.org/jira/browse/KAFKA-9984 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-9983) Add end-to-end latency metrics to Streams

Sophie Blee-Goldman created KAFKA-9983: -- Summary: Add end-to-end latency metrics to Streams Key: KAFKA-9983 URL: https://issues.apache.org/jira/browse/KAFKA-9983 Project: Kafka Issue

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

See

Re: [DISCUSS] KIP-614: Add Prefix Scan support for State Stores

Hi Guozhang For clarity, the issues I was running into was not about the actual *prefixSeek* function itself, but about exposing it to the same level of access as the *range* function throughout Kafka Streams. It required a lot of changes, and also required that most state stores stub it out

Re: [DISCUSS] KIP-614: Add Prefix Scan support for State Stores

Hello Adam, I'm wondering if you can provide a bit more context on the blockers of using prefixSeek of RocksDB (I saw you have a RocksDBPrefixIterator class but not used anywhere yet)? I'm currently looking at ways to allow some secondary indices with rocksDB following some existing approaches

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

Hi all, I'd like to start a vote on KIP-604: Remove ZooKeeper Flags from the Administrative Tools. As a reminder, this KIP is for the next major release of Kafka, the 3.0 release. So it won't go into the upcoming 2.6 release. It's a pretty small change that just removes the --zookeeper

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

See Changes: [github] MINOR: Remove allow concurrent test (#8641) [github] KAFKA-8770: KIP-557: Drop idempotent KTable source updates (#8254) [github] KAFKA-9669; Loosen validation of inner offsets for older

Jenkins build is back to normal : kafka-trunk-jdk14 #76

See

[jira] [Resolved] (KAFKA-8820) kafka-reassign-partitions.sh should support the KIP-455 API

[ https://issues.apache.org/jira/browse/KAFKA-8820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-8820. - Fix Version/s: 2.5.0 Resolution: Fixed > kafka-reassign-partitions.sh should support the

[jira] [Created] (KAFKA-9982) [kafka-connect] Source connector does not guarantee at least once delivery

Qinghui Xu created KAFKA-9982: - Summary: [kafka-connect] Source connector does not guarantee at least once delivery Key: KAFKA-9982 URL: https://issues.apache.org/jira/browse/KAFKA-9982 Project: Kafka

Re: [DISCUSS] KIP-572: Improve timeouts and retires in Kafka Streams

John, Guozhang, thanks a lot for your feedback. I updated the KIP on a slightly different angle: instead of using retries, we should switch to a timeout based approach. I also extended the KIP to deprecate producer/admin `retries` config. I like the proposal to skip a task if a client

[jira] [Reopened] (KAFKA-8803) Stream will not start due to TimeoutException: Timeout expired after 60000milliseconds while awaiting InitProducerId

[ https://issues.apache.org/jira/browse/KAFKA-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta reopened KAFKA-8803: > Stream will not start due to TimeoutException: Timeout expired after > 6milliseconds while

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

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

[jira] [Resolved] (KAFKA-9669) Kafka 2.4.0 Chokes on Filebeat 5.6 Produced Data

[ https://issues.apache.org/jira/browse/KAFKA-9669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9669. Resolution: Fixed > Kafka 2.4.0 Chokes on Filebeat 5.6 Produced Data >

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

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

Re: [DISCUSS] KIP-612: Ability to Limit Connection Creation Rate on Brokers

Hello, Thank you for the KIP. I experienced in the past genuine broker brownouts due to connection storms consuming most of the CPU available on the server and I think it is useful to protect against it. I tend to share the questions asked in points 2 and 4 from David. Is there still a risk of

Re: [VOTE] KIP-605 - Expand Connect Worker Internal Topic Settings

FYI: I made a few clarifications to more carefully describe what happens with extra topic settings that the broker doesn't accept. First, the description in the patterns table now is a bit more clear: Here "" must be any valid Kafka topic-level configurations for the version of the Kafka broker

Re: [DISCUSS] - Kafka Summit - A Talk on Getting Started with Contributing

Fantastic Matthias! I am wrapping up the draft tomorrow and I will share it with you and others that have offered to help for review and feedback. The more eyes and feedback I can get the better, I believe. I am not aware of count limit as presenters regarding the sessions but I guess I will

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

Hey David, I accepted your suggestion and add Monitorable interface. Thanks for great suggestion. Please review KIP-608 again and see any suggestion on name of function or other stuff. jeff. On 2020/05/11 15:16:30, David Jacot wrote: > Hey, > > Thanks for the KIP. > > I think that having

Re: [VOTE] KIP-221: Enhance KStream with Connecting Topic Creation and Repartition Hint

Sounds fair to me; I think as a syntax sugar it is a good to have, but sometimes it was "enforced" to be used for repartitioning purposes. On Mon, May 11, 2020 at 7:08 PM Matthias J. Sax wrote: > As an afterthought to KIP-221, I am wondering if we should deprecate > `KStream#through()`? > > The

Re: Kafka Contributor List Addition

Thanks! I look forward to contributing and being part of the community. Best saher On Mon, May 11, 2020 at 4:53 PM Matthias J. Sax wrote: > Saher, > > I added you to the list of contributors on Jira. You can now self-assign > tickets. > > A good way to get started is to checkout the web page:

Re: [DISCUSS] - Kafka Summit - A Talk on Getting Started with Contributing

Great idea! I submitted a talk myself, and I am not sure (if my talk gets accepted) if being in two talks is desired by the program committee. But I would be interested personally to help and/or co-present. Let me know if/how I can help with the talk abstract. -Matthias On 5/12/20 7:39 AM,

[jira] [Resolved] (KAFKA-9963) High CPU during replication of replaced (empty) broker

[ https://issues.apache.org/jira/browse/KAFKA-9963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evan Williams resolved KAFKA-9963. -- Resolution: Abandoned > High CPU during replication of replaced (empty) broker >

[jira] [Created] (KAFKA-9981) Running a dedicated mm2 cluster with more than one nodes,When the configuration is updated the task is not aware and will lose the update operation.

victor created KAFKA-9981: - Summary: Running a dedicated mm2 cluster with more than one nodes,When the configuration is updated the task is not aware and will lose the update operation. Key: KAFKA-9981 URL:

Re: [DISCUSS] - Kafka Summit - A Talk on Getting Started with Contributing

Hi Israel, This sounds like a very interesting topic. It will be great if there is anything that I can help with. Best wishes, Leonard On Tue, May 12, 2020 at 2:43 PM Israel Ekpo wrote: > Hello Everyone, > > I am in the process of submitting a 40-minute talk on how to get involved > with the

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

Hi Colin, It's not clear whether users of the Java API would need to supply the salt and salted password directly, or whether the constructor of ScramCredential would take the password and perform the hashing itself. I also wonder a little about consistency with the other APIs which have

[DISCUSS] - Kafka Summit - A Talk on Getting Started with Contributing

Hello Everyone, I am in the process of submitting a 40-minute talk on how to get involved with the Apache Kafka project. As a beginning contributor to the project, it was a bit overwhelming earlier on in the process knowing where to start, what to do and how to get involved. I would like to

Re: [DISCUSS] KIP-614: Add Prefix Scan support for State Stores

Hi Sagar I implemented a very similar interface for KIP-213, the foreign-key joiner. We pulled it out of the final implementation and instead used RocksDB range instead. You can see the particular code where we use RocksDB.range(...) to get the same iterator result.

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

Hi David, Thanks for the reply. >> If I understand the proposed throttling algorithm, an initial request > would > >> be allowed (possibly making K negative) and only subsequent requests > >> (before K became positive) would receive the QUOTA_VIOLATED. That would > >> mean it was still possible

[jira] [Resolved] (KAFKA-5948) EosIntegrationTest fails with TopicAlreadyMarkedForDeletionException

[ https://issues.apache.org/jira/browse/KAFKA-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-5948. -- Resolution: Cannot Reproduce > EosIntegrationTest fails with

[VOTE] KIP-578: Add configuration to limit number of partitions

Hello, I'd like to initialize voting on KIP-578: https://cwiki.apache.org/confluence/display/KAFKA/KIP-578%3A+Add+configuration+to+limit+number+of+partitions . Got some good feedback from Stanislav Kozlovski, Alexandre Dupriez and Tom Bentley on the discussion thread. I have addressed their

Re: [VOTE] KIP-577: Allow HTTP Response Headers Configured for Kafka Connect

+1 (binding) Thanks for the KIP. On Wed, May 6, 2020 at 7:57 PM Randall Hauch wrote: > Thanks for putting this together. > > +1 (binding) > > On Fri, Apr 17, 2020 at 2:02 PM Aneel Nazareth wrote: > > > Thanks Jeff, this seems like it addresses a user need. > > > > +1 (non-binding) > > > > On

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

See Changes: [github] KAFKA-9466: Update Kafka Streams docs for KIP-447 (#8621) -- [...truncated 6.16 MB...] org.apache.kafka.streams.TestTopicsTest > testTimestamp

Re: [DISCUSS] KIP-612: Ability to Limit Connection Creation Rate on Brokers

Hi Anna, Thanks for the KIP! I have few questions: 1. You mention that some clients may create a new connections for each requests: "Another example is clients that create a new connection for each produce/consume request". I am curious here but do we know any clients behaving like this? 2. I

[jira] [Created] (KAFKA-9980) Reserved word "" may not be santinized to "%3Cdefault%3E"

Cheng Tan created KAFKA-9980: Summary: Reserved word "" may not be santinized to "%3Cdefault%3E" Key: KAFKA-9980 URL: https://issues.apache.org/jira/browse/KAFKA-9980 Project: Kafka Issue Type:

[DISCUSS] KIP-614: Add Prefix Scan support for State Stores

Hi All, I would like to start a discussion on the KIP that I created below to add prefix scan support in State Stores: https://cwiki.apache.org/confluence/display/KAFKA/KIP-614%3A+Add+Prefix+Scan+support+for+State+Stores Thanks! Sagar.