[jira] [Created] (KAFKA-13229) KIP-761: implement a total blocked time metric in Kafka Streams

Rohan Desai created KAFKA-13229: --- Summary: KIP-761: implement a total blocked time metric in Kafka Streams Key: KAFKA-13229 URL: https://issues.apache.org/jira/browse/KAFKA-13229 Project: Kafka

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

See Changes: -- [...truncated 488291 lines...] [2021-08-26T04:19:49.657Z] > Task :raft:testClasses UP-TO-DATE [2021-08-26T04:19:49.657Z] > Task :connect:json:testJar

Jenkins build became unstable: Kafka » Kafka Branch Builder » 3.0 #119

See

Re: [DISCUSS] KIP-768: Extend SASL/OAUTHBEARER with Support for OIDC

Thanks for the reply, Can we also update the KIP about the testing approach? Thanks, On Wed, Aug 25, 2021 at 12:01 AM Kirk True wrote: > Hi Manikumar! > > On Mon, Aug 23, 2021, at 12:59 PM, Manikumar wrote: > > Hi Kirk, > > Thanks for the KIP! > > 1. Do we want to support validating issuers

[jira] [Resolved] (KAFKA-12929) KIP-750: Deprecate support for Java 8 in Kafka 3.0

[ https://issues.apache.org/jira/browse/KAFKA-12929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis resolved KAFKA-12929. Resolution: Fixed Resolving to unblock the RC for 3.0.0 and will keep a

[jira] [Resolved] (KAFKA-12930) KIP-751: Deprecate support for Scala 2.12 in Kafka 3.0

[ https://issues.apache.org/jira/browse/KAFKA-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis resolved KAFKA-12930. Resolution: Fixed Resolving to unblock the RC for 3.0.0 and will keep a

[jira] [Created] (KAFKA-13228) ApiVersionRequest are not correctly handled in kraft mode

dengziming created KAFKA-13228: -- Summary: ApiVersionRequest are not correctly handled in kraft mode Key: KAFKA-13228 URL: https://issues.apache.org/jira/browse/KAFKA-13228 Project: Kafka Issue

[jira] [Resolved] (KAFKA-8734) Remove PartitionAssignorAdapter and deprecated PartitionAssignor interface

[ https://issues.apache.org/jira/browse/KAFKA-8734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-8734. --- Fix Version/s: 3.0.0 Resolution: Fixed > Remove

Re: [VOTE] KIP-748: Add Broker Count Metrics (restarted)

+1 (non-binding) Thanks for the KIP! Thank you. Luke On Wed, Aug 25, 2021 at 4:55 AM Jason Gustafson wrote: > Thanks Colin! +1 > > On Mon, Aug 23, 2021 at 1:37 PM David Arthur wrote: > > > Thanks, Colin. Looks good to me! > > > > +1 binding > > > > -David > > > > On Mon, Aug 16, 2021 at 3:37

[GitHub] [kafka-site] Dougoc opened a new pull request #368: MINOR: Update powered-by.html used by globo

Dougoc opened a new pull request #368: URL: https://github.com/apache/kafka-site/pull/368 Globo have amazing experience with Kafka and it's a really big pleasure share this information! -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[DISCUSS] KIP-736: Report the true end to end fetch latency

Hi All, I'd like to open up the discussion on a KIP-736. This is to report the "real" fetch latency by removing the effects of waiting due to replica.fetch.wait.max.ms or fetch.min.bytes. Please give it a look over and let me know what you think.

Re: Ensuring that Kafka message is persisted after acknowledgement

You can control fsync with two properties: https://kafka.apache.org/documentation/#topicconfigs_flush.messages https://kafka.apache.org/documentation/#topicconfigs_flush.ms On Wed, Aug 25, 2021 at 10:39 AM Kunal Goyal wrote: > Hello, > > We are exploring using Kafka for our application. Our

[jira] [Created] (KAFKA-13227) Cancel pending AlterIsr requests after receiving LeaderAndIsr

Jason Gustafson created KAFKA-13227: --- Summary: Cancel pending AlterIsr requests after receiving LeaderAndIsr Key: KAFKA-13227 URL: https://issues.apache.org/jira/browse/KAFKA-13227 Project: Kafka

Ensuring that Kafka message is persisted after acknowledgement

Hello, We are exploring using Kafka for our application. Our requirement is that once we write some messages to Kafka, it should be guaranteed that the messages are persisted to disk. We found this article which

[jira] [Created] (KAFKA-13226) Partition expansion may cause uneven distribution

shizhenzhen created KAFKA-13226: --- Summary: Partition expansion may cause uneven distribution Key: KAFKA-13226 URL: https://issues.apache.org/jira/browse/KAFKA-13226 Project: Kafka Issue Type:

[GitHub] [kafka-site] cadonna commented on pull request #364: Add p3r (https://www.p3r.one/) to the list of the "Powered By ❤️"

cadonna commented on pull request #364: URL: https://github.com/apache/kafka-site/pull/364#issuecomment-905251532 ping @miguno -- 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

[GitHub] [kafka-site] cadonna commented on pull request #364: Add p3r (https://www.p3r.one/) to the list of the "Powered By ❤️"

cadonna commented on pull request #364: URL: https://github.com/apache/kafka-site/pull/364#issuecomment-905251113 Thank you for the PR @hrittikhere! Did you test your changes with a local Apache server similar to

Re: Stuck build

Hi Christo, I stopped the build and restarted it. Hopefully, this time it will not get stuck. Best, Bruno On 25.08.21 08:14, Josep Prat wrote: Hi Christo, The easiest two ways to re-trigger the builds that I found are: — Close and open the Pull Request. Jenkins should pick this event up —

[GitHub] [kafka-site] hrittikhere commented on pull request #364: Add p3r (https://www.p3r.one/) to the list of the "Powered By ❤️"

hrittikhere commented on pull request #364: URL: https://github.com/apache/kafka-site/pull/364#issuecomment-905244617 @cadonna can you please review? -- 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

[GitHub] [kafka-site] hrittikhere removed a comment on pull request #364: Add p3r (https://www.p3r.one/) to the list of the "Powered By ❤️"

hrittikhere removed a comment on pull request #364: URL: https://github.com/apache/kafka-site/pull/364#issuecomment-901422630 @rhauch / @kkonstantine can you please give this a look? Thanks :) -- This is an automated message from the Apache Git Service. To respond to the message,

Re: Stuck build

Hi Christo, The easiest two ways to re-trigger the builds that I found are: — Close and open the Pull Request. Jenkins should pick this event up — Add another commit, or force push again I would also love to hear other means. But as far as I can tell only maintainers can trigger actions in