Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #3022

See

[jira] [Resolved] (KAFKA-16969) KRaft unable to upgrade to v3.7.1 and later when multiple log dir is set

[ https://issues.apache.org/jira/browse/KAFKA-16969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-16969. --- Fix Version/s: 3.8.0 3.7.1 Assignee: Igor Soarez Resolution: Fixed

[jira] [Created] (KAFKA-16988) InsufficientResourcesError in ConnectDistributedTest system test

Luke Chen created KAFKA-16988: - Summary: InsufficientResourcesError in ConnectDistributedTest system test Key: KAFKA-16988 URL: https://issues.apache.org/jira/browse/KAFKA-16988 Project: Kafka I

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Hi Matthias, I like this compromise a lot. +1 from me Best, Chris On Mon, Jun 17, 2024, 16:15 Justine Olshan wrote: > Makes sense to me. > > Thanks Matthias for summarizing the state. > > Justine > > On Mon, Jun 17, 2024 at 1:12 PM Matthias J. Sax wrote: > > > Hey, > > > > seems this KIP is

RE: [QUESTION] What to do about conflicted KIP numbers?

Thanks for the input Matthias, I guess we will keep things as they are to prevent yet another layer added on top. Eric has already taken the next available number and it's recorded on the wiki so I suppose there's no additional work required here. Regards, -Matt -Original Message- From

[jira] [Resolved] (KAFKA-12652) connector doesnt accept transformation configuration

[ https://issues.apache.org/jira/browse/KAFKA-12652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-12652. - Resolution: Duplicate > connector doesnt accept transformation configuration > -

[jira] [Resolved] (KAFKA-10568) transforms.InsertField.type

[ https://issues.apache.org/jira/browse/KAFKA-10568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-10568. - Resolution: Duplicate > transforms.InsertField.type > --- > >

[jira] [Created] (KAFKA-16987) Release connector & task resources when entering FAILED state

Greg Harris created KAFKA-16987: --- Summary: Release connector & task resources when entering FAILED state Key: KAFKA-16987 URL: https://issues.apache.org/jira/browse/KAFKA-16987 Project: Kafka

[jira] [Resolved] (KAFKA-10670) repo.maven.apache.org: Name or service not known

[ https://issues.apache.org/jira/browse/KAFKA-10670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-10670. - Resolution: Cannot Reproduce > repo.maven.apache.org: Name or service not known > --

Re: [DISCUSS] Apache Kafka 3.9.0 release

Would it be better to start a DISCUSS thread for 4.0 and keep this thread for 3.9 discussions? We seem to have agreement on 3.9. On Mon, Jun 17, 2024 at 4:29 PM José Armando García Sancio wrote: > > +1 for me. Thanks Colin for volunteering to be the release manager. > > On Mon, Jun 17, 2024 at 4:

Re: [DISCUSS] Apache Kafka 3.9.0 release

+1 for me. Thanks Colin for volunteering to be the release manager. On Mon, Jun 17, 2024 at 4:15 PM Ismael Juma wrote: > > Hi all, > > I think we should actually look at the target dates vs just looking at the > release length. 3.9 is an August release. I suggest we aim for a November > release f

[jira] [Resolved] (KAFKA-5736) Improve error message in Connect when all kafka brokers are down

[ https://issues.apache.org/jira/browse/KAFKA-5736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-5736. Assignee: (was: Konstantine Karantasis) Resolution: Won't Fix This appears to be a third-

Re: [DISCUSS] Apache Kafka 3.9.0 release

Hi all, I think we should actually look at the target dates vs just looking at the release length. 3.9 is an August release. I suggest we aim for a November release for 4.0, which is 3 months (instead of 4). Why? Because December is a tricky month given holidays and all. And it gives us a buffer f

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Makes sense to me. Thanks Matthias for summarizing the state. Justine On Mon, Jun 17, 2024 at 1:12 PM Matthias J. Sax wrote: > Hey, > > seems this KIP is very difficult, and we actually had a lot of > background discussion about it in the last weeks. I believe the problem > with this KIP is, t

[jira] [Resolved] (KAFKA-12164) ssue when kafka connect worker pod restart, during creation of nested partition directories in hdfs file system.

[ https://issues.apache.org/jira/browse/KAFKA-12164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-12164. - Resolution: Invalid This issue appears to deal only with a Connect plugin, which is not supporte

Re: [VOTE] KIP-1038: Add Custom Error Handler to Producer

I just replied to the DISCUSS thread, proposing to DISCARD this KIP in favor of a different solution to the problem. -Matthias On 5/20/24 9:27 AM, Kirk True wrote: +1 (non-binding) Thanks Alieh! On May 20, 2024, at 6:00 AM, Walker Carlson wrote: Hey Alieh, Thanks for the KIP. +1 bindin

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Hey, seems this KIP is very difficult, and we actually had a lot of background discussion about it in the last weeks. I believe the problem with this KIP is, that we have 3 starting points to look at a problem, but these 3 starting points don't align: 1. Producer API: we want a clean API d

[jira] [Resolved] (KAFKA-6353) Connector status shows FAILED but actually task is in RUNNING status

[ https://issues.apache.org/jira/browse/KAFKA-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-6353. Resolution: Not A Bug The REST API provides separate status for a connector and it's tasks. Any one

[jira] [Created] (KAFKA-16986) After upgrading to Kafka 3.41, the producer constantly produces logs related to topicId changes

Vinicius Vieira dos Santos created KAFKA-16986: -- Summary: After upgrading to Kafka 3.41, the producer constantly produces logs related to topicId changes Key: KAFKA-16986 URL: https://issues.apache.or

Re: [DISCUSS] Apache Kafka 3.9.0 release

In general I prefer to stick with the original time frame, but I believe an additional month would be good for KIP-848. Maybe we can cut down 2 weeks for the 4.1 and 4.2 releases each, to make up for the time? Not a must; just an idea. We can also just accept a one-time shift of the release ti

Re: [DISCUSS] Apache Kafka 3.8.0 release

I meant it from a time perspective, not from a branching point perspective. Sorry for the confusion. As said in the other thread, doing it four months after 3.9 is desirable for KIP-848 as I expect that we will need time to stabilize everything after switching all the default configs once 3.9 is cu

Re: [DISCUSS] Apache Kafka 3.9.0 release

+1 for the release plan. Thanks! +1 for releasing 4.0 four months after 3.9. 4.0 is actually a pretty big release as we will GA KIP-848, including new group coordinator and new consumer rebalance protocol. This is a pretty big change :). Best, David Le lun. 17 juin 2024 à 20:36, Colin McCabe a

Re: DISCUSS KIP-984 Add pluggable compression interface to Kafka

Hi Assane, Pluggable compression codecs in the protocol seem likely to greatly fragment the ecosystem. I don't see a corresponding benefit that offsets this. As Greg says, people who want to use a closed source codec already can, by forking Kafka. Open source clients won't be able to talk to t

Re: [VOTE] KIP-1042: Support for wildcard when creating new acls

My concern is that the extra complexity may actually slow us down. In general people already complain about the speed of ACL matches, and adding another "degree of freedom" seems likely to make things worse. It would be useful to understand how much faster or slower the code is with the propsed

RE: DISCUSS KIP-984 Add pluggable compression interface to Kafka

Hi Greg, Thank you for your thoughtful response. Our motivation is to enable new compression codecs and quick deployment of new codecs in a scalable way. Like most of the Kafka community, we also would like to prevent fragmentation of the ecosystem as a result of introducing incompatible te

Re: [DISCUSS] Apache Kafka 3.9.0 release

Hi all, Thanks, everyone. Quick update: on the release plan page, I moved feature freeze forward and code freeze by one week to make sure we can hit that. No other dates changed. With regard to 4.0, I was assuming that we'd do it 4 months after 3.9 was released. I think for that release, we sh

[jira] [Resolved] (KAFKA-15752) KRaft support in SaslSslAdminIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-15752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-15752. Fix Version/s: 3.9.0 Resolution: Fixed > KRaft support in SaslSslAdminIntegrationTe

[jira] [Resolved] (KAFKA-15751) KRaft support in BaseAdminIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-15751. Fix Version/s: 3.9.0 Resolution: Fixed > KRaft support in BaseAdminIntegrationTest

Re: [DISCUSS] Apache Kafka 3.8.0 release

Why would 4.0 be based on 3.8? My understanding is, that it will be based on 3.9. -Matthias On 6/14/24 11:22 PM, David Jacot wrote: I agree that we should keep 4.0 time-based. My question is based on which release. If I understand you, you would like to keep it based on 3.8. This means that 4.

[jira] [Created] (KAFKA-16985) Ensure consumer sends leave request on close even if interrupted

Lianet Magrans created KAFKA-16985: -- Summary: Ensure consumer sends leave request on close even if interrupted Key: KAFKA-16985 URL: https://issues.apache.org/jira/browse/KAFKA-16985 Project: Kafka

Re: [DISCUSS] KIP-1057: Add remote log metadata flag to the dump log tool

Thanks Federico for the KIP. This feature is helpful for developers while debugging tiered storage related issues. Even though RLMM is a pluggable interface, it is still useful to have a utility that is meant for the default/inbuilt implementation based on the internal topic. We can clarify that

Re: [EXTERNAL] Re: Kafka upgrade recommendation

First off, I'd suggest reading https://kafka.apache.org/documentation/#upgrade pretty carefully. It has your exact question more or less defined and outlined. As I mentioned, they are putting a lot of effort into how the world should migrate from

Re: [EXTERNAL] Re: Kafka upgrade recommendation

Hi, Thanks for the answer. However I still do not have a clear picture on how we should go from version 2.2.1 which we are on at the moment. Options 1. Straight jump from 2.2.1 to 3.6.3 2. Jump from 2.2.1 to 2.6.2 and then the second jump from 2.6.2. to 3.6.3 What’s you recommendation here

Re: [EXTERNAL] Re: Kafka upgrade recommendation

Hey Wojciech, It has been a long time since we did the jump but we had waited until 3.3.x release when we did the jump and there were a lot of manual steps at that time. We then had another manual step when going to either 3.4 or 3.5 don't remember which but that one was easier cause we did hav

Re: [EXTERNAL] Re: Kafka upgrade recommendation

Hi Sejal, Thanks for reaching out. What would be your recommended strategy to go from 2.2.1 into 3.6.2 version? Can we securely do it in one jump or we should use some step in between (e.g. to jump form 2.2.1 to 2.6.2 and then from 2.6.2 to 3.6.2)? Thanks, [A blue background with white text an

[DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi all, I'd like to kick off a discussion for KIP-1059 that suggests adding a new feature to the Producer flush() method. https://cwiki.apache.org/confluence/display/KAFKA/KIP-1059%3A+Enable+the+Producer+flush%28%29+method+to+clear+the+latest+send%28%29+error Cheers, Alieh

Re: [PR] MINOR: document how we deal with advisories for dependencies [kafka-site]

mjsax commented on PR #554: URL: https://github.com/apache/kafka-site/pull/554#issuecomment-2173755020 @raboof @divijvaidya -- What is the status of this PR? Seems nothing happened for a while. Do we still plant to get this merged, or should we close it? -- This is an automated message f

Re: [PR] Update ZK migration section to indicate GA [kafka-site]

mjsax commented on PR #545: URL: https://github.com/apache/kafka-site/pull/545#issuecomment-2173751898 @mumrah -- Any updates on this PR? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the speci

Re: [PR] Selected Kafka Americas 2021 presentations [kafka-site]

mjsax commented on PR #378: URL: https://github.com/apache/kafka-site/pull/378#issuecomment-2173749987 Closing this due to age -- not sure what the criteria is to add new talks TBH. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to Gi

Re: [PR] Selected Kafka Americas 2021 presentations [kafka-site]

mjsax closed pull request #378: Selected Kafka Americas 2021 presentations URL: https://github.com/apache/kafka-site/pull/378 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

Re: [PR] MINOR Add note about KAFKA-15552 to 3.6 upgrade section [kafka-site]

mjsax commented on PR #560: URL: https://github.com/apache/kafka-site/pull/560#issuecomment-2173746761 @mumrah -- what is the status of this PR? Was this also fixed in `kafka.git` (to avoid overwriting/reverting in case we would do another release -- even if unlikely for 3.6) -- This is

Re: [PR] MINOR: Copy over apache/kafka/3.6 docs into here [kafka-site]

mjsax commented on PR #586: URL: https://github.com/apache/kafka-site/pull/586#issuecomment-2173743835 @stanislavkozlovski -- what is the status of this PR? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above

Re: [PR] Fixed links to Streams Developer Guide subpages [kafka-site]

mjsax commented on PR #588: URL: https://github.com/apache/kafka-site/pull/588#issuecomment-2173742569 Thanks for the PR @thuri! Merged. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specif

Re: [PR] Fixed links to Streams Developer Guide subpages [kafka-site]

mjsax merged PR #588: URL: https://github.com/apache/kafka-site/pull/588 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.or

[jira] [Created] (KAFKA-16984) New consumer should wait for leave group response to avoid responses to disconnected clients

Lianet Magrans created KAFKA-16984: -- Summary: New consumer should wait for leave group response to avoid responses to disconnected clients Key: KAFKA-16984 URL: https://issues.apache.org/jira/browse/KAFKA-16984

Re: [PR] MINOR: update Kafka Streams docs with 3.2/3.3/3.4 KIP information [kafka-site]

mjsax merged PR #607: URL: https://github.com/apache/kafka-site/pull/607 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.or

[jira] [Resolved] (KAFKA-16970) Fix hash implementation of `ScramCredentialValue`, `ScramCredentialData`, and `ContextualRecord`

[ https://issues.apache.org/jira/browse/KAFKA-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16970. Fix Version/s: 3.9.0 Resolution: Fixed > Fix hash implementation of `ScramCredentia

Re: [DISCUSS] KIP-1058: Txn consumer exerts pressure on remote storage when reading non-txn topic

Divij, Thanks for the review! Updated the KIP with 1, 2, 3, and 4 review comments. > 4. Potential alternative - Instead of having an algorithm where we traverse across segment metadata and looking for isTxnIdxEmpty flag, should we directly introduce a nextSegmentWithTrxInx() function? This would

[jira] [Resolved] (KAFKA-15420) Kafka Tiered Storage V1

[ https://issues.apache.org/jira/browse/KAFKA-15420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana resolved KAFKA-15420. Resolution: Fixed > Kafka Tiered Storage V1 > --- > >

Re: [PR] Update docs for 3.7.1 [kafka-site]

mimaison commented on code in PR #604: URL: https://github.com/apache/kafka-site/pull/604#discussion_r1642745310 ## 37/generated/connect_metrics.html: ## @@ -1,5 +1,5 @@ -[2024-02-23 00:02:00,837] INFO Metrics scheduler closed (org.apache.kafka.common.metrics.Metrics:694) -[202

[jira] [Resolved] (KAFKA-16983) Generate the PR for Docker Official Images repo

[ https://issues.apache.org/jira/browse/KAFKA-16983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krish Vora resolved KAFKA-16983. Resolution: Done > Generate the PR for Docker Official Images repo > -

[jira] [Resolved] (KAFKA-16981) Remove any versions for which Docker Official Images should not be supported IF ANY

[ https://issues.apache.org/jira/browse/KAFKA-16981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krish Vora resolved KAFKA-16981. Resolution: Done > Remove any versions for which Docker Official Images should not be supported >

[jira] [Resolved] (KAFKA-16982) Docker Official Image Build and Test

[ https://issues.apache.org/jira/browse/KAFKA-16982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krish Vora resolved KAFKA-16982. Resolution: Done > Docker Official Image Build and Test > > >

[jira] [Resolved] (KAFKA-16980) Extract docker official image artifact

[ https://issues.apache.org/jira/browse/KAFKA-16980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krish Vora resolved KAFKA-16980. Resolution: Done > Extract docker official image artifact > --

[jira] [Resolved] (KAFKA-16979) Prepare Docker Official Image Source for 3.7.0 release

[ https://issues.apache.org/jira/browse/KAFKA-16979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krish Vora resolved KAFKA-16979. Resolution: Done > Prepare Docker Official Image Source for 3.7.0 release > --

[jira] [Created] (KAFKA-16983) Generate the PR for Docker Official Images repo

Krish Vora created KAFKA-16983: -- Summary: Generate the PR for Docker Official Images repo Key: KAFKA-16983 URL: https://issues.apache.org/jira/browse/KAFKA-16983 Project: Kafka Issue Type: Sub-t

[jira] [Created] (KAFKA-16982) Docker Official Image Build and Test

Krish Vora created KAFKA-16982: -- Summary: Docker Official Image Build and Test Key: KAFKA-16982 URL: https://issues.apache.org/jira/browse/KAFKA-16982 Project: Kafka Issue Type: Sub-task Aff

Re: [VOTE] KIP-1042: Support for wildcard when creating new acls

I give this a cautious +1 (non binding) as development may yield better head wildcard results. I think the adoption criteria for the ACL search needs to be specified in the KIP. We do not have a good handle on how long the current searches take. If the wildcard tests can be merged into a trie se

[jira] [Created] (KAFKA-16981) Remove any versions for which Docker Official Images should not be supported

Krish Vora created KAFKA-16981: -- Summary: Remove any versions for which Docker Official Images should not be supported Key: KAFKA-16981 URL: https://issues.apache.org/jira/browse/KAFKA-16981 Project: Ka

[jira] [Created] (KAFKA-16979) Prepare Docker Official Image Source for 3.7.0 release

Krish Vora created KAFKA-16979: -- Summary: Prepare Docker Official Image Source for 3.7.0 release Key: KAFKA-16979 URL: https://issues.apache.org/jira/browse/KAFKA-16979 Project: Kafka Issue Type

[jira] [Created] (KAFKA-16980) Extract docker official image artifact

Krish Vora created KAFKA-16980: -- Summary: Extract docker official image artifact Key: KAFKA-16980 URL: https://issues.apache.org/jira/browse/KAFKA-16980 Project: Kafka Issue Type: Sub-task A

[jira] [Resolved] (KAFKA-16373) Docker Official Image for Apache Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josep Prat resolved KAFKA-16373. Resolution: Fixed > Docker Official Image for Apache Kafka > -

[jira] [Created] (KAFKA-16978) Apache Kafka 3.7.0 release

Krish Vora created KAFKA-16978: -- Summary: Apache Kafka 3.7.0 release Key: KAFKA-16978 URL: https://issues.apache.org/jira/browse/KAFKA-16978 Project: Kafka Issue Type: Task Reporter:

RE: [VOTE] KIP-1040: Improve handling of nullable values in InsertField, ExtractField, and other transformations

Hi all, As @Mario Fiore Vitale mentioned, we have now received enough votes. Therefore, should we close this voting and start the development? On 2024/06/14 08:00:45 Mario Fiore Vitale wrote: > Hi All, > > We have 4 binding +1 votes. Do you think the vote can b

[jira] [Created] (KAFKA-16977) remote log manager dynamic configs are not available after broker restart.

Satish Duggana created KAFKA-16977: -- Summary: remote log manager dynamic configs are not available after broker restart. Key: KAFKA-16977 URL: https://issues.apache.org/jira/browse/KAFKA-16977 Projec

[jira] [Created] (KAFKA-16976) Improve the dynamic config handling for RemoteLogManagerConfig when a broker is restarted.

Satish Duggana created KAFKA-16976: -- Summary: Improve the dynamic config handling for RemoteLogManagerConfig when a broker is restarted. Key: KAFKA-16976 URL: https://issues.apache.org/jira/browse/KAFKA-16976

[jira] [Resolved] (KAFKA-15444) KIP-974: Docker Image for GraalVM based Native Kafka Broker

[ https://issues.apache.org/jira/browse/KAFKA-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna Agarwal resolved KAFKA-15444. - Resolution: Done > KIP-974: Docker Image for GraalVM based Native Kafka Broker > ---

Re: [DISCUSS] KIP-1058: Txn consumer exerts pressure on remote storage when reading non-txn topic

Hi Kamal Thanks for bringing this up. This is a problem worth solving. We have faced this in situations where some Kafka clients default to read_committed mode and end up having high latencies for remote fetches due to this traversal across all segments. First some nits to clarify the KIP: 1. The

[jira] [Resolved] (KAFKA-16932) Documentation changes for Native Docker image

[ https://issues.apache.org/jira/browse/KAFKA-16932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krishna Agarwal resolved KAFKA-16932. - Resolution: Done > Documentation changes for Native Docker image > -

Re: [DISCUSS] KIP-1057: Add remote log metadata flag to the dump log tool

Hi Kamal, On Mon, Jun 17, 2024 at 11:44 AM Kamal Chandraprakash wrote: > > We can use the console-consumer to read the contents of the > `__remote_log_metadata` topic. Why are we proposing a new tool? > > sh kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic > __remote_log_metada

[jira] [Resolved] (KAFKA-16673) Optimize toTopicPartitions with ConsumerProtocolSubscription

[ https://issues.apache.org/jira/browse/KAFKA-16673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16673. - Fix Version/s: 3.9.0 Resolution: Fixed > Optimize toTopicPartitions with ConsumerProtocol

Re: [DISCUSS] KIP-1057: Add remote log metadata flag to the dump log tool

We can use the console-consumer to read the contents of the `__remote_log_metadata` topic. Why are we proposing a new tool? sh kafka-console-consumer.sh --bootstrap-server localhost:9092 --topic __remote_log_metadata --consumer-property exclude.internal.topics=false --formatter org.apache.kafka.s

[DISCUSS] KIP-1058: Txn consumer exerts pressure on remote storage when reading non-txn topic

Hi all, I have opened a KIP-1058 to reduce the pressure on remote storage when transactional consumers are reading non-txn topics from remote storage. https://

Re: [VOTE] KIP-1017: A health check endpoint for Kafka Connect

Hi Chris, +1 (non binding) Thanks, Fede On Mon, Jun 17, 2024 at 9:57 AM Adrian Preston wrote: > > Hi Chris, > > +1 (non-binding) > > Regards, > - Adrian > > From: Edoardo Comar > Date: Sunday, 16 June 2024 at 07:57 > To: dev@kafka.apache.org > Subject: [EXTERNAL] Re: [VOTE] KIP-1017: A health

[jira] [Reopened] (KAFKA-15420) Kafka Tiered Storage V1

[ https://issues.apache.org/jira/browse/KAFKA-15420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamal Chandraprakash reopened KAFKA-15420: -- > Kafka Tiered Storage V1 > --- > > Key: KAFKA

[jira] [Resolved] (KAFKA-15420) Kafka Tiered Storage V1

[ https://issues.apache.org/jira/browse/KAFKA-15420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamal Chandraprakash resolved KAFKA-15420. -- Resolution: Fixed > Kafka Tiered Storage V1 > --- > >

[jira] [Created] (KAFKA-16975) The error message of creating `__cluster_metadata` should NOT be "Authorization failed"

Chia-Ping Tsai created KAFKA-16975: -- Summary: The error message of creating `__cluster_metadata` should NOT be "Authorization failed" Key: KAFKA-16975 URL: https://issues.apache.org/jira/browse/KAFKA-16975

[jira] [Created] (KAFKA-16974) KRaft support in SslAdminIntegrationTest

Mickael Maison created KAFKA-16974: -- Summary: KRaft support in SslAdminIntegrationTest Key: KAFKA-16974 URL: https://issues.apache.org/jira/browse/KAFKA-16974 Project: Kafka Issue Type: Task

[VOTE] KIP-1042: Support for wildcard when creating new acls

Hi all, I would like to call a vote on KIP-1042 which extends creation of acls with MATCH pattern type. KIP - https://cwiki.apache.org/confluence/display/KAFKA/KIP-1042%3A+Support+for+wildcard+when+creating+new+acls Discussion thread - https://lists.apache.org/thread/xx3lcg60kp4v34x0j9p6xobby8l4

Adserver reporting with Kafka and necessary tools

Dear Kafka Team, We are reaching out as a team new to Kafka and are interested in exploring its use for adserver reporting. We believe Kafka's capabilities can be valuable in handling our reporting data efficiently. Our goal is to learn more about the necessary tools and best practices for settin

Re: Kafka upgrade recommendation

I would suggest going from 2.6.2 to 3.6.2 and then stopping and waiting until 3.7.1 comes out. There is a pretty serious flaw in 3.7.0 that hit us and we ended up having to downgrade to 3.6.2 to recover. The bug is fixed but not going to be released until 3.7.1 comes out. The bug prevented metad

RE: [VOTE] KIP-1017: A health check endpoint for Kafka Connect

Hi Chris, +1 (non-binding) Regards, - Adrian From: Edoardo Comar Date: Sunday, 16 June 2024 at 07:57 To: dev@kafka.apache.org Subject: [EXTERNAL] Re: [VOTE] KIP-1017: A health check endpoint for Kafka Connect Thanks for this KIP, Chris, +1 (binding) Edo On Fri, 14 Jun 2024 at 20:20, Greg H

[jira] [Created] (KAFKA-16973) Fix caught-up condition

David Jacot created KAFKA-16973: --- Summary: Fix caught-up condition Key: KAFKA-16973 URL: https://issues.apache.org/jira/browse/KAFKA-16973 Project: Kafka Issue Type: Sub-task Report

Re: [DISCUSS] KIP-1057: Add remote log metadata flag to the dump log tool

Hi Divij, On Sun, Jun 16, 2024 at 7:38 PM Divij Vaidya wrote: > > Hello Federico > > Please note that the topic-based RLMM is one of the possible > implementations of RLMM. Hence, whatever solution we design here should: 1\ > be explicit that this tooling only works for topic based RLMM 2\ specif