Re: request to be added to contribution list

Hi Neil, You're all set now. -Bill On Tue, Jun 1, 2021 at 8:45 PM Neil Buesing wrote: > I am looking to contribute to Apache Kafka. > > To start I have realized that KIP-499 to standardize on command line > arguments has not updated kafka-streams-application-reset, so KAFKA-12878 > is to

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

See Changes: -- [...truncated 472922 lines...] [2021-06-02T03:02:41.302Z] [2021-06-02T03:02:41.302Z] SaslPlainSslEndToEndAuthorizationTest >

[jira] [Created] (KAFKA-12875) Change Log layer segment map mutations to avoid absence of active segment

Kowshik Prakasam created KAFKA-12875: Summary: Change Log layer segment map mutations to avoid absence of active segment Key: KAFKA-12875 URL: https://issues.apache.org/jira/browse/KAFKA-12875

[GitHub] [kafka-site] hachikuji merged pull request #355: Add Axios (https://www.axios.com/) to the list of the "Powered By ❤️"

hachikuji merged pull request #355: URL: https://github.com/apache/kafka-site/pull/355 -- 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. For queries about this service,

[VOTING] KIP-693: Client-side Circuit Breaker for Partition Write Errors

Dear All, We would like to get a vote on this proposal. The implementation is linked to the KIP, and we have ran this in our production setup for a while. https://issues.apache.org/jira/browse/KAFKA-12793 Thanks in advance! //George//

request to be added to contribution list

I am looking to contribute to Apache Kafka. To start I have realized that KIP-499 to standardize on command line arguments has not updated kafka-streams-application-reset, so KAFKA-12878 is to deprecate --bootstrap-servers and use --bootstrap-server. username: nbuesing email: n...@buesing.dev

[jira] [Created] (KAFKA-12876) Log.roll() could forever delete producer state snapshot of empty active segment

Kowshik Prakasam created KAFKA-12876: Summary: Log.roll() could forever delete producer state snapshot of empty active segment Key: KAFKA-12876 URL: https://issues.apache.org/jira/browse/KAFKA-12876

[jira] [Resolved] (KAFKA-12709) Admin API for ListTransactions

[ https://issues.apache.org/jira/browse/KAFKA-12709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-12709. - Fix Version/s: 3.0.0 Resolution: Fixed > Admin API for ListTransactions >

[jira] [Created] (KAFKA-12878) Support --bootstrap-server kafka-streams-application-reset

Neil Buesing created KAFKA-12878: Summary: Support --bootstrap-server kafka-streams-application-reset Key: KAFKA-12878 URL: https://issues.apache.org/jira/browse/KAFKA-12878 Project: Kafka

[jira] [Created] (KAFKA-12877) Fix KRPC files with missing flexibleVersions annotation

Colin McCabe created KAFKA-12877: Summary: Fix KRPC files with missing flexibleVersions annotation Key: KAFKA-12877 URL: https://issues.apache.org/jira/browse/KAFKA-12877 Project: Kafka

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

See

[jira] [Created] (KAFKA-12870) RecordAccumulator stuck in a flushing state

Niclas Lockner created KAFKA-12870: -- Summary: RecordAccumulator stuck in a flushing state Key: KAFKA-12870 URL: https://issues.apache.org/jira/browse/KAFKA-12870 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-739: Block Less on KafkaProducer#send

On Tue, Jun 1, 2021, at 07:00, Nakamura wrote: > Hi Colin, > > Sorry, I still don't follow. > > Right now `KafkaProducer#send` seems to trigger a metadata fetch. Today, > we block on that before returning. Is your proposal that we move the > metadata fetch out of `KafkaProducer#send` entirely?

[GitHub] [kafka-site] orchome opened a new pull request #357: Update powered-by.html

orchome opened a new pull request #357: URL: https://github.com/apache/kafka-site/pull/357 Added information about OrcHome Inc. to powerd-by.html -- 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

Re: [DISCUSS] KIP-744: Migrate TaskMetadata to interface with internal implementation

Hi Josep, Thank you for the KIP! Specifying TaskMetadata as an interface lifts the guarantee that equals() and hashCode() on the TaskMetadata return consistent values for the same content. Note that the current TaskMetadata implements both methods, so theoretically users might already rely

[jira] [Resolved] (KAFKA-12866) Kafka requires ZK root access even when using a chroot

[ https://issues.apache.org/jira/browse/KAFKA-12866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-12866. --- Resolution: Fixed > Kafka requires ZK root access even when using a chroot >

[jira] [Created] (KAFKA-12871) Kafka-connect : rest api connect config, fields are not ordered

raphael auv created KAFKA-12871: --- Summary: Kafka-connect : rest api connect config, fields are not ordered Key: KAFKA-12871 URL: https://issues.apache.org/jira/browse/KAFKA-12871 Project: Kafka

Re: [DISCUSS] KIP-744: Migrate TaskMetadata to interface with internal implementation

Hi Bruno, Thanks for your feedback. I think it makes sense to add the hasCode() and equals() definitions with its guarantees on the interface level. I'm also inclined to add the ThreadMetadata conversion to an interface into this KIP. Implementation-wise is not that different. And on API level

[jira] [Resolved] (KAFKA-12519) Consider Removing Streams Old Built-in Metrics Version

[ https://issues.apache.org/jira/browse/KAFKA-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-12519. --- Resolution: Fixed > Consider Removing Streams Old Built-in Metrics Version >

[jira] [Created] (KAFKA-12872) KIP-724: Drop support for message formats v0 and v1

Ismael Juma created KAFKA-12872: --- Summary: KIP-724: Drop support for message formats v0 and v1 Key: KAFKA-12872 URL: https://issues.apache.org/jira/browse/KAFKA-12872 Project: Kafka Issue

Re: [DISCUSS] KIP-739: Block Less on KafkaProducer#send

Hi Colin, Sorry, I still don't follow. Right now `KafkaProducer#send` seems to trigger a metadata fetch. Today, we block on that before returning. Is your proposal that we move the metadata fetch out of `KafkaProducer#send` entirely? Even if the metadata fetch moves to be non-blocking, I

[jira] [Reopened] (KAFKA-12598) Remove deprecated --zookeeper in ConfigCommand

[ https://issues.apache.org/jira/browse/KAFKA-12598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-12598: - > Remove deprecated --zookeeper in ConfigCommand > -- >

[DISCUSS] KIP-724: Drop support for message formats v0 and v1

Hi all, It's time to start the process of sunsetting message formats v0 and v1 in order to establish a new baseline in terms of supported client/broker behavior and to improve maintainability & supportability of Kafka. Please take a look at the proposal:

Re: [DISCUSS] KIP-618: Atomic commit of source connector records and offsets

Hi Gunnar, Thanks for taking a look! I've addressed the low-hanging fruit in the KIP; responses to other comments inline here: > * TransactionContext: What's the use case for the methods accepting a source record (commitTransaction(SourceRecord record), abortTransaction(SourceRecord record))?

Re: [DISCUSS] KIP-744: Migrate TaskMetadata to interface with internal implementation

Hi all, I managed to update the KIP to include the changes Bruno proposed and also extended it to include the migration of ThreadMetadata to an interface plus internal implementation. Please share any feedback or problems you might see with this approach. As the deadline for KIPs approaches, I

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

See Changes: -- [...truncated 472401 lines...] [2021-06-01T16:36:26.926Z] [INFO] Parameter: package, Value: myapps [2021-06-01T16:36:26.926Z] [INFO] Parameter:

[jira] [Created] (KAFKA-12873) Log truncation due to divergence should also remove snapshots

Jose Armando Garcia Sancio created KAFKA-12873: -- Summary: Log truncation due to divergence should also remove snapshots Key: KAFKA-12873 URL: https://issues.apache.org/jira/browse/KAFKA-12873

Re: [DISCUSS] KIP-739: Block Less on KafkaProducer#send

Colin, the issue for me isn't so much whether non-blocking I/O is used or not, but the fact that the caller observes a long time between calling send() and receiving the returned future. This behavior can be considered "blocking" whether or not I/O is involved. > How are the ordering semantics of

Re: [DISCUSS] KIP-739: Block Less on KafkaProducer#send

Hi Colin, > KafkaProducer#send is supposed to initiate non-blocking I/O, but not wait for it to complete. > > There's more information about non-blocking I/O in Java here: > https://en.wikipedia.org/wiki/Non-blocking_I/O_%28Java%29 I think we're talking past each other a bit. I know about

[jira] [Resolved] (KAFKA-7749) confluent does not provide option to set consumer properties at connector level

[ https://issues.apache.org/jira/browse/KAFKA-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-7749. -- Fix Version/s: 2.3.0 Resolution: Fixed

[jira] [Created] (KAFKA-12874) Increase default consumer session timeout to 40s (KIP-735)

Jason Gustafson created KAFKA-12874: --- Summary: Increase default consumer session timeout to 40s (KIP-735) Key: KAFKA-12874 URL: https://issues.apache.org/jira/browse/KAFKA-12874 Project: Kafka