[jira] [Created] (KAFKA-14366) Kafka consumer rebalance issue, offsets points back to very old committed offset

Chetan created KAFKA-14366: -- Summary: Kafka consumer rebalance issue, offsets points back to very old committed offset Key: KAFKA-14366 URL: https://issues.apache.org/jira/browse/KAFKA-14366 Project: Kafka

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

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #1343

See

Re: [DISCUSS] KIP-878: Autoscaling for Statically Partitioned Streams

Thanks for the KIP Sophie. Seems there is a lively discussion going on. I tried to read up on the history and I hope I don't repeat what was already discussed. And sorry for the quite long email... (1) Stateless vs Stateful I agree that stateless apps should be supported, even if I am not

Re: [DISCUSS] KIP-852 Optimize calculation of size for log in remote tier

Hi, Divij, Thanks for the KIP. Sorry for the late reply. The motivation of the KIP is to improve the efficiency of size based retention. I am not sure the proposed changes are enough. For example, if the size exceeds the retention size, we need to determine the subset of segments to delete to

Re: Regarding Producer Metric - "request-latency-avg"

So request-latency-avg is the time after drain? Can you try to share a elaborated explanation of this metric calculation that is being done. On Tue, 8 Nov 2022 at 1:30 AM, Philip Nee wrote: > Hey Amrit, > > Actually, I think the confluent guide is correct because it seems like the > request is

Re: Regarding Producer Metric - "request-latency-avg"

Hey Amrit, Actually, I think the confluent guide is correct because it seems like the request is created here . and the queue time

Re: Regarding Producer Metric - "request-latency-avg"

Bumping On Mon, 7 Nov 2022 at 12:45 PM, Amrit Gupta wrote: > Hi Philip, > > >> the latency measures the time difference between the *time the > request was created* and the response received > >> I believe it is *between the time send() was called*, and the time > the producer receives the

[jira] [Created] (KAFKA-14365) Refactor Fetcher to allow different implementations

Kirk True created KAFKA-14365: - Summary: Refactor Fetcher to allow different implementations Key: KAFKA-14365 URL: https://issues.apache.org/jira/browse/KAFKA-14365 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-14364) Support evolving serde with Foreign Key Join

John Roesler created KAFKA-14364: Summary: Support evolving serde with Foreign Key Join Key: KAFKA-14364 URL: https://issues.apache.org/jira/browse/KAFKA-14364 Project: Kafka Issue Type:

[DISCUSS] KIP-877: Mechanism for plugins and connectors to register metrics

Hi, I have opened KIP-877 to make it easy for plugins and connectors to register their own metrics: https://cwiki.apache.org/confluence/display/KAFKA/KIP-877%3A+Mechanism+for+plugins+and+connectors+to+register+metrics Let me know if you have any feedback or suggestions. Thanks, Mickael

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

See Changes: -- [...truncated 510890 lines...] [2022-11-07T15:38:42.739Z] [2022-11-07T15:38:42.739Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 167

[jira] [Resolved] (KAFKA-14346) Remove static methods from internal Connect APIs for easier testing

[ https://issues.apache.org/jira/browse/KAFKA-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-14346. --- Fix Version/s: 3.4.0 Resolution: Fixed > Remove static methods from internal Connect

[jira] [Created] (KAFKA-14363) Add new `coordinator` module

David Jacot created KAFKA-14363: --- Summary: Add new `coordinator` module Key: KAFKA-14363 URL: https://issues.apache.org/jira/browse/KAFKA-14363 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-14362) Same message consumed by two consumers in the same group after client restart

Mikael created KAFKA-14362: -- Summary: Same message consumed by two consumers in the same group after client restart Key: KAFKA-14362 URL: https://issues.apache.org/jira/browse/KAFKA-14362 Project: Kafka

Re: [DISCUSS] KIP-872: Add Serializer#serializeToByteBuffer() to reduce memory copying

Apologies for the late reply. I will be more proactive on this thead moving ahead. 3. Understood. Perhaps, `ByteBuffer#asReadOnlyBuffer()` is not the right solution and I acknowledge that the current API modifies the offsets of the user provided input when it calls flip(). I still believe that we

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

See

[jira] [Resolved] (KAFKA-14344) Improve MM2 integration test by building EmbeddedKafkaCluster with common configs used for all clients

[ https://issues.apache.org/jira/browse/KAFKA-14344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-14344. Fix Version/s: 3.4.0 Resolution: Fixed > Improve MM2 integration test by building

Re: Re: [DISCUSS] KIP-710: Full support for distributed mode in dedicated MirrorMaker 2.0 clusters

Hi Daniel, Thanks for the KIP. It would be nice to expose more of the REST API as some endpoints are really useful, for example /admin or /connectors//tasks-config. However as dedicated mode is currently unusable, I think the approach of "just fixing it" by exposing the internal endpoints is

[jira] [Resolved] (KAFKA-13887) Running multiple instance of same stateful KafkaStreams application on single host raise Exception

[ https://issues.apache.org/jira/browse/KAFKA-13887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-13887. --- Resolution: Not A Problem > Running multiple instance of same stateful KafkaStreams