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

See

Re: Request to Contribute

Hi Guozhang, Thank you for adding me to JIRA. Best regards, Tomonari 2022年1月28日 3:56 +0900、Guozhang Wang のメール: > Hello, > > Thanks for your interests in contributing, I've added you to JIRA. > > Guozhang > > On Thu, Jan 27, 2022 at 4:54 AM Tomonari Yamashita > wrote: > > > Hi Apache Kafka

[jira] [Created] (KAFKA-13624) Add Metric for Store Cache Size

Sagar Rao created KAFKA-13624: - Summary: Add Metric for Store Cache Size Key: KAFKA-13624 URL: https://issues.apache.org/jira/browse/KAFKA-13624 Project: Kafka Issue Type: Improvement

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

See

Re: [VOTE] KIP-801: Implement an Authorizer that stores metadata in __cluster_metadata

> My intention here was to avoid exposing Kafka clients to AUTHORIZER_NOT_READY_ERROR. If this error is only ever returned to internal components (such as the broker) then things are a lot simpler. Keep in mind there are external management systems that assume that if the broker ports accept

Re: [VOTE] KIP-801: Implement an Authorizer that stores metadata in __cluster_metadata

On Thu, Jan 27, 2022, at 15:52, Jason Gustafson wrote: > Hey Colin, > > If we allow the `Authorizer` to raise `AUTHORIZER_NOT_READY_ERROR`, then > would we need `early.start.listeners`? This would give the `Authorizer` a > way to support partial startup, but it would be up to the implementation to

Re: [VOTE] KIP-801: Implement an Authorizer that stores metadata in __cluster_metadata

Hey Colin, If we allow the `Authorizer` to raise `AUTHORIZER_NOT_READY_ERROR`, then would we need `early.start.listeners`? This would give the `Authorizer` a way to support partial startup, but it would be up to the implementation to decide whether to use it. For an `Authorizer` which depends

[jira] [Resolved] (KAFKA-13603) empty active segment can trigger recovery after clean shutdown and restart

[ https://issues.apache.org/jira/browse/KAFKA-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-13603. - Fix Version/s: 3.2.0 Resolution: Fixed merged the PR to trunk. > empty active segment can

Re: [DISCUSS] KIP-704: Send a hint to broker if it is an unclean leader

Hi Jason, Jason wrote: > Thanks for the updates. I noticed that `LeaderRecoveryState` is marked as > ignorable in the `AlterPartition` request. It would be helpful to > understand the motivation for that. I think it is fine for this property to be marked as ignorable because the property is

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

See

Re: KIP-769: Connect API to retrieve connector configuration definitions

To be honest I'm very sceptical that you can evolve (without breaking compatibility) from a situation of having a large number of plugins which have already implemented version() to return whatever they please, to a situation where you can rely on it as the basis for some feature to support

Re: [DISCUSS] KIP-714: Client metrics and observability

Hi, Magnus, Thanks for updating the KIP. The overall approach makes sense to me. A few more detailed comments below. 20. ClientTelemetry: Should it be extending configurable and closable? 21. Compression of the metrics on the client: what's the default? 22. "Client metrics plugin / extending

Re: Request to Contribute

Hello, Thanks for your interests in contributing, I've added you to JIRA. Guozhang On Thu, Jan 27, 2022 at 4:54 AM Tomonari Yamashita wrote: > Hi Apache Kafka team, > > Request to Contribute > > Could you add me to the contributor list? > > I’ve found a issue: "[#KAFKA-13619]

Re: KIP-769: Connect API to retrieve connector configuration definitions

Hi Mickael, +1 for the warning at startup, it'd be great if we could get everyone to start versioning all of their components. Although given the current state of WARN-level logging in Connect (see https://issues.apache.org/jira/browse/KAFKA-7509) there might be too much noise for most people to

[jira] [Resolved] (KAFKA-13348) Allow Source Tasks to Handle Producer Exceptions

[ https://issues.apache.org/jira/browse/KAFKA-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-13348. Fix Version/s: 3.2.0 Resolution: Fixed > Allow Source Tasks to Handle Producer

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

See Changes: -- [...truncated 511357 lines...] [2022-01-27T17:26:45.491Z] MessageGenerator: processed 1 Kafka message JSON files(s). [2022-01-27T17:26:45.491Z]

Re: Request to Contribute

Hi Tomonari, You're all set now (contributor in Jira and KIP creation permissions on the Wiki). Thanks for your interest in Apache Kafka. -Bill On Thu, Jan 27, 2022 at 10:53 AM Tomonari Yamashita wrote: > Hi Apache Kafka team, > > Request to Contribute > > Could you add me to the contributor

[jira] [Created] (KAFKA-13623) Memory leak with multiple poll

Emanuel Velzi created KAFKA-13623: - Summary: Memory leak with multiple poll Key: KAFKA-13623 URL: https://issues.apache.org/jira/browse/KAFKA-13623 Project: Kafka Issue Type: Bug

Request to Contribute

Hi Apache Kafka team, Request to Contribute Could you add me to the contributor list? I’ve found a issue: "[#KAFKA-13619] zookeeper.sync.time.ms is no longer used” And I’ve also created a pull request for that. JIRA username: tyamashi-oss   (Tomonari Yamashita) Wiki username:  [same as the

[GitHub] [kafka-site] dajac merged pull request #394: MINOR: Change 3.0, 2.7.2 and 2.6.3 downloads to use archives

dajac merged pull request #394: URL: https://github.com/apache/kafka-site/pull/394 -- 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:

Request to Contribute

Hi Apache Kafka team, Request to Contribute Could you add me to the contributor list? I’ve found a issue: "[#KAFKA-13619] zookeeper.sync.time.ms is no longer used” And I’ve also created a pull request for that. JIRA username: tyamashi-oss   (Tomonari Yamashita) Wiki username:  [same as the

Re: KIP-769: Connect API to retrieve connector configuration definitions

Hi Chris, Thanks for taking another look! That's a good point which I should have mentioned in the KIP. I think we can have a PossiblyVersioned interface that extends Versioned and has the default implementation. I'd like to also print a warning at startup if a plugin does not override

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

See