[jira] [Created] (KAFKA-17383) Update upgrade notes about removal of `offsets.commit.required.acks`

David Jacot created KAFKA-17383: --- Summary: Update upgrade notes about removal of `offsets.commit.required.acks` Key: KAFKA-17383 URL: https://issues.apache.org/jira/browse/KAFKA-17383 Project: Kafka

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #39

See

[jira] [Resolved] (KAFKA-16736) Remove offsets.commit.required.acks in 4.0

[ https://issues.apache.org/jira/browse/KAFKA-16736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16736. Fix Version/s: 4.0.0 Resolution: Fixed > Remove offsets.commit.required.acks in 4.0

[jira] [Created] (KAFKA-17382) cleanup out-of-date configs of config_property

Chia-Ping Tsai created KAFKA-17382: -- Summary: cleanup out-of-date configs of config_property Key: KAFKA-17382 URL: https://issues.apache.org/jira/browse/KAFKA-17382 Project: Kafka Issue Type

Re: [DISCUSS] KIP-1076: Metrics for client applications a KIP-714 extension

Hi Apoorv, Thank you for the discussion! Here are my responses to your follow-up questions: AM2: My apologies for the previous response; I misunderstood the question. When executing the `registerMetricsForSubscription,` it is up to the developer to provide all metrics that could possibly be in a

[jira] [Created] (KAFKA-17381) Reduce log output from checkstyle task

David Arthur created KAFKA-17381: Summary: Reduce log output from checkstyle task Key: KAFKA-17381 URL: https://issues.apache.org/jira/browse/KAFKA-17381 Project: Kafka Issue Type: Task

Re: [DISCUSS] KIP-1076: Metrics for client applications a KIP-714 extension

Hi Bill, Thanks for the answers, some follow ups. AM2: If we will only register subscribed metrics, as per the subscription received from the broker, then are we going to call the `registerMetricsForSubscription` post to GetTelemetrySubscription response from the broker? Also how do we manage the

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #3216

See Changes: -- [...truncated 424516 lines...] [2024-08-20T19:04:03.389Z] Gradle Test Run :core:test > Gradle Test Executor 103 > ZkMigrationIntegrationTest > testMigrateT

Re: [DISCUSS] KIP-1076: Metrics for client applications a KIP-714 extension

Hi Apoorv, Thanks for reading the KIP and commenting. Here are my answers to your comments/questions: AM1: Good point; I'll update the Javadoc in the KIP to be more specific. AM2: I'm not sure I follow, but IIUC, then yes, this method will only subscribe telemetry metrics. AM3: The `registerMe

[jira] [Created] (KAFKA-17380) Kafka Streams few partition stuck in processing - fixed after restart

Rohit Bobade created KAFKA-17380: Summary: Kafka Streams few partition stuck in processing - fixed after restart Key: KAFKA-17380 URL: https://issues.apache.org/jira/browse/KAFKA-17380 Project: Kafka

Re: [DISCUSS] KIP-1076: Metrics for client applications a KIP-714 extension

Hi Bruno, Thanks for the comments! Here are my responses: BC1: Yes, I agree the name could use some work. My original intent was that the user is adding additional metrics to the metrics already reported by the given client. But the name you provided here works, so I'll update the KIP accordin

Re: Question about config.action.reload

Hi Ran, The config.action.reload, subscribe, unsubscribe, and ConfigChangeCallback features are partially-implemented. As far as I can tell if you're using only AK connect-runtime and config providers, none of it is functional. If you have a config provider that implements TTLs, the runtime will

[jira] [Created] (KAFKA-17379) KafkaStreams: Unexpected state transition from ERROR to PENDING_SHUTDOWN

Ao Li created KAFKA-17379: - Summary: KafkaStreams: Unexpected state transition from ERROR to PENDING_SHUTDOWN Key: KAFKA-17379 URL: https://issues.apache.org/jira/browse/KAFKA-17379 Project: Kafka I

Question about config.action.reload

Hi Kafka team, Currently I'm investigating the config.action.reload feature of Kafka Connect. I'm wondering how to enable this feature. E.g. If I use the FileConfigProvider, clients/src/main/java/org/apache/kafka/common/config/provider/FileConfigProvider.java is it enough to set the config.action.

[jira] [Created] (KAFKA-17378) Initial performance testing fixes

Andrew Schofield created KAFKA-17378: Summary: Initial performance testing fixes Key: KAFKA-17378 URL: https://issues.apache.org/jira/browse/KAFKA-17378 Project: Kafka Issue Type: Sub-tas

[jira] [Resolved] (KAFKA-17350) Improve kafka-share-groups.sh --describe output for empty groups

[ https://issues.apache.org/jira/browse/KAFKA-17350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-17350. -- Resolution: Fixed > Improve kafka-share-groups.sh --describe output for empty groups >

Re: [DISCUSS] KIP-1071: Streams Rebalance Protocol

Hi Lucas, Yeah, I agree that it's not ideal to push the burden on users letting them to remember when changes happen (and they need to consider what kind of changes are "sensitive" enough), manually update the ID either from a config or via something else --- mentioned it in your doc and in my fir

Re: [DISCUSS] KIP-1081: Graduation Steps for Features

Hi all, I added a new section in the KIP to specify how to change the graduation levels for a feature. Best! On Mon, Aug 19, 2024 at 4:01 PM Josep Prat wrote: > Hi TengYao and Chia-Ping, > > I updated the KIP page with examples. > > Best, > > On Mon, Aug 19, 2024 at 2:39 PM TengYao Chi wrote:

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #3215

See Changes: -- [...truncated 421266 lines...] [2024-08-20T12:38:02.684Z] Gradle Test Run :core:test > Gradle Test Executor 104 > LiteralAclStoreTest > shouldRoundTripChan

[jira] [Resolved] (KAFKA-16503) getOrMaybeCreateClassicGroup should not thrown GroupIdNotFoundException

[ https://issues.apache.org/jira/browse/KAFKA-16503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16503. - Resolution: Fixed Addressed by https://github.com/apache/kafka/pull/16919. > getOrMaybeCreateCl

[jira] [Resolved] (KAFKA-17325) Clients : Revisit result handling in ShareConsumeRequestManager

[ https://issues.apache.org/jira/browse/KAFKA-17325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shivsundar R resolved KAFKA-17325. -- Resolution: Fixed > Clients : Revisit result handling in ShareConsumeRequestManager >

Question about ResourcePatternFilter

Should a ResourcePatternFilter that has a PatternType of ANY and a name of WILDCARD_RESOURCE not match any Acls? I think this is a bug.I am writing a series of tests to ensure that I have implemented everything correctly in the Trie implementation and this has come up. public boolean matches(Res

[jira] [Created] (KAFKA-17377) Consider using defaultApiTimeoutMs in AsyncKafkaConsumer#unsubscribe

PoAn Yang created KAFKA-17377: - Summary: Consider using defaultApiTimeoutMs in AsyncKafkaConsumer#unsubscribe Key: KAFKA-17377 URL: https://issues.apache.org/jira/browse/KAFKA-17377 Project: Kafka

Re: [DISCUSS] KIP-1076: Metrics for client applications a KIP-714 extension

Hi Bill, Thanks for the KIP and it's great to see a way applications can also send telemetry metrics over the KIP-714 pipeline. A couple of questions: AM1: The Javadoc for the method seems to be a bit vague, it talks about "subscription" but do we need to be a bit more detailed regarding which sub

Re: [DISCUSS] KIP-1076: Metrics for client applications a KIP-714 extension

Hi Bill, Thanks for the KIP! BC1 I find the name registerAdditionalMetrics() not specific enough. It is not clear that the passed-in metrics are made available for subscription. What about registerMetricsForSubscription()? The Additional part is confusing in my opinion: additional to what? B

Re: [DISCUSS] KIP-1071: Streams Rebalance Protocol

Hi Guozhang, I see now that we should have addressed the method for generating topology IDs in the KIP, even if it is somewhat of an implementation detail. We did not include it in the KIP, because it can be changed, and there doesn't seem to be a perfect choice, so we wanted to sidestep a lengthy

[jira] [Created] (KAFKA-17376) Use the new group coordinator by default in 4.0

David Jacot created KAFKA-17376: --- Summary: Use the new group coordinator by default in 4.0 Key: KAFKA-17376 URL: https://issues.apache.org/jira/browse/KAFKA-17376 Project: Kafka Issue Type: Sub

[jira] [Created] (KAFKA-17375) Partition reassignment cannot proceed after segment.bytes change

Tommi Vainikainen created KAFKA-17375: - Summary: Partition reassignment cannot proceed after segment.bytes change Key: KAFKA-17375 URL: https://issues.apache.org/jira/browse/KAFKA-17375 Project: K