[jira] [Created] (KAFKA-15453) Enable `testFencingOnTransactionExpiration` in TransactionsWithTieredStoreTest

Satish Duggana created KAFKA-15453: -- Summary: Enable `testFencingOnTransactionExpiration` in TransactionsWithTieredStoreTest Key: KAFKA-15453 URL: https://issues.apache.org/jira/browse/KAFKA-15453

[jira] [Resolved] (KAFKA-15352) Ensure consistency while deleting the remote log segments

[ https://issues.apache.org/jira/browse/KAFKA-15352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Satish Duggana resolved KAFKA-15352. Resolution: Fixed > Ensure consistency while deleting the remote log segments >

[jira] [Created] (KAFKA-15452) Custom Principal Builders Can't Access SslPrincipalMapper

Raghu Baddam created KAFKA-15452: Summary: Custom Principal Builders Can't Access SslPrincipalMapper Key: KAFKA-15452 URL: https://issues.apache.org/jira/browse/KAFKA-15452 Project: Kafka

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

See

Re: Apache Kafka 3.6.0 release

Hey Satish, We just discovered a gap in KIP-890 part 1. We currently don't verify on txn offset commits, so it is still possible to have hanging transactions on the consumer offsets partitions. I've opened a jira to wire the verification in that request.

[jira] [Created] (KAFKA-15451) Include offline dirs in BrokerHeartbeatRequest

Igor Soarez created KAFKA-15451: --- Summary: Include offline dirs in BrokerHeartbeatRequest Key: KAFKA-15451 URL: https://issues.apache.org/jira/browse/KAFKA-15451 Project: Kafka Issue Type:

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

See

Re: Apache Kafka 3.6.0 release

Another (small) ZK migration issue was identified. This one isn't a regression (it has existed since 3.4), but I think it's reasonable to include. It's a small configuration check that could potentially save end users from some headaches down the line.

[jira] [Created] (KAFKA-15450) Disable ZK migration when JBOD configured

David Arthur created KAFKA-15450: Summary: Disable ZK migration when JBOD configured Key: KAFKA-15450 URL: https://issues.apache.org/jira/browse/KAFKA-15450 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-960: Support interactive queries (IQv2) for versioned state stores

Thanks for the KIP Alieh! I don't have anything to add to the 960 discussion right now as it seems rather straightforward. I think after you address Bruno's comments we can bring it to a vote. I'll review the two spawned KIPs separately. Keep it up, Walker On Wed, Sep 6, 2023 at 5:11 AM Bruno

[jira] [Resolved] (KAFKA-14499) Implement OffsetFetch/OffsetCommit APIs

[ https://issues.apache.org/jira/browse/KAFKA-14499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-14499. - Fix Version/s: 3.7.0 Resolution: Fixed > Implement OffsetFetch/OffsetCommit APIs >

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

See

Re: Complete Kafka replication protocol description

Hi all, I agree that we should have the protocol description and specification in the Kafka repository. I have two other specifications to contribute including the KRaft implementation of Raft and the next gen consumer group protocol (WIP). I also have a formal prose description of the Kafka

[jira] [Resolved] (KAFKA-15380) Try complete actions after callback

[ https://issues.apache.org/jira/browse/KAFKA-15380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-15380. Resolution: Fixed > Try complete actions after callback >

[jira] [Resolved] (KAFKA-15424) Make verification a dynamic configuration

[ https://issues.apache.org/jira/browse/KAFKA-15424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-15424. Resolution: Fixed > Make verification a dynamic configuration >

[jira] [Created] (KAFKA-15449) Verify Offset Commits too

Justine Olshan created KAFKA-15449: -- Summary: Verify Offset Commits too Key: KAFKA-15449 URL: https://issues.apache.org/jira/browse/KAFKA-15449 Project: Kafka Issue Type: Sub-task

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

See

Re: Requesting permission to contribute

Hi Nikhil, My bad, I might have forgotten to save the right permissions. Now you are good to go. Best, On Mon, Sep 11, 2023 at 4:16 PM Nikhil Ramakrishnan < ramakrishnan.nik...@gmail.com> wrote: > Hello Josep, > > Thanks for the quick response! However, I am still unable to edit/create >

Re: Requesting permission to contribute

Hello Josep, Thanks for the quick response! However, I am still unable to edit/create documents in the Kafka space on the Confluence wiki (my username is nikrmk). Do I need to do anything else to enable this? Thanks, Nikhil On Thu, Sep 7, 2023 at 4:23 PM Josep Prat wrote: > Hi Nikhil, > >

RE: [VOTE] KIP-942: Add Power(ppc64le) support

Hi Colin Can we continue the voting process now? Thanks Vaibhav Nazare -Original Message- From: Divij Vaidya Sent: Monday, August 28, 2023 1:43 PM To: dev@kafka.apache.org Subject: [EXTERNAL] Re: [VOTE] KIP-942: Add Power(ppc64le) support Hey Colin I suggested running tests on

[jira] [Created] (KAFKA-15448) Streams StandbyTaskUpdateListener

Colt McNealy created KAFKA-15448: Summary: Streams StandbyTaskUpdateListener Key: KAFKA-15448 URL: https://issues.apache.org/jira/browse/KAFKA-15448 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-12473) Make the "cooperative-sticky, range" as the default assignor

[ https://issues.apache.org/jira/browse/KAFKA-12473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-12473. - Resolution: Won't Do Given that KIP-848 is on the way, I believe that we should not do this

Re: [DISCUSS] KIP-892: Transactional Semantics for StateStores

Nick, Thanks for the response. >Can you clarify how much state was restored in those 11 seconds? That was a full restoration of ~650MB of state after I wiped the state directory. The restoration after a crash with your branch is nearly instantaneous, whereas with plain Kafka 3.5.0 a crash

Re: Complete Kafka replication protocol description

This is very useful Jack! 1. We are missing a replication protocol specification in our project. Ideally it should be a living document and adding what you wrote to the docs/design would be a great start towards that goal. 2. I have also been building on top of some existing TLA+ to add changes

Re: [DISCUSS] KIP-977: Partition-Level Throughput Metrics

Thank you for the proposal Qichao. I agree with the motivation here and understand the tradeoff here between observability vs. increased metric dimensions (metric fan-out as you say in the KIP). High level comments: 1. I would urge you to consider the extensibility of the proposal for other

[jira] [Resolved] (KAFKA-15315) Use getOrDefault rather than get

[ https://issues.apache.org/jira/browse/KAFKA-15315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15315. - Resolution: Fixed > Use getOrDefault rather than get > > >

Re: [DISCUSS] KIP-892: Transactional Semantics for StateStores

Hi Colt, Thanks for taking the time to run your benchmarks on this, that's incredibly helpful. > With KIP 892, I verified that unclean shutdown does not cause a fresh > restore (). I got the following benchmark results: > - Benchmark took 216 seconds > - 1,401 tasks per second on one

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

See

[jira] [Resolved] (KAFKA-14975) Make TopicBasedRemoteLogMetadataManager methods wait for initialize to complete

[ https://issues.apache.org/jira/browse/KAFKA-14975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew de Detrich resolved KAFKA-14975. Resolution: Won't Fix Closing issue since the core problem was solved in another

[jira] [Reopened] (KAFKA-15397) Deserializing produce requests may cause memory leaks when exceptions occur

[ https://issues.apache.org/jira/browse/KAFKA-15397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hudeqi reopened KAFKA-15397: > Deserializing produce requests may cause memory leaks when exceptions occur >