Build failed in Jenkins: kafka-2.4-jdk8 #27

See Changes: [matthias] MINOR: fix typo in TestInputTopic.getTimestampAndAdvance (#7553) -- [...truncated 5.11 MB...] kafka.server.MetadataCacheTest >

[jira] [Reopened] (KAFKA-4996) Fix findbugs multithreaded correctness warnings for streams

[ https://issues.apache.org/jira/browse/KAFKA-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reopened KAFKA-4996: Thanks for pointing out [~ableegoldman] – we should address it – I was assuming that the

Build failed in Jenkins: kafka-trunk-jdk11 #893

See Changes: [matthias] MINOR: fix typo in TestInputTopic.getTimestampAndAdvance (#7553) -- [...truncated 2.94 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [DISCUSS] KIP-539: Implement mechanism to flush out records in low volume suppression buffers

Hi Bill, Thanks for the input! TBH, I am think that suppression buffers are not used *in response *to low traffic conditions. Rather, we are trying to fix the situation when low traffic conditions occur in a suppression buffer (for example, previously, the same suppression buffer had a decent

[jira] [Resolved] (KAFKA-8994) Streams should expose standby replication information & allow stale reads of state store

[ https://issues.apache.org/jira/browse/KAFKA-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar resolved KAFKA-8994. --- Resolution: Duplicate > Streams should expose standby replication information & allow stale

[jira] [Reopened] (KAFKA-8994) Streams should expose standby replication information & allow stale reads of state store

[ https://issues.apache.org/jira/browse/KAFKA-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar reopened KAFKA-8994: --- > Streams should expose standby replication information & allow stale reads of > state store >

Re: KAFKA-8584: Support of ByteBuffer for bytes field implemented[Convert Kafka RPCs to use automatically generated code]

Hi Nikolay, Sorry that I haven't had more bandwidth to review this recently. I will take a look today. In the future, can you please rebase your changes on top of trunk, rather than merging trunk into your branch? It is difficult to follow which changes are yours and which come from the

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Hi all, Seeing that we got all out votes needed with 3 binding votes and 0 nonbinding. I consider this KIP passed. Cheers, Richard On Fri, Oct 18, 2019 at 9:17 AM Guozhang Wang wrote: > Thanks Richard, I'm +1 on the KIP > > On Thu, Oct 17, 2019 at 3:51 PM Richard Yu > wrote: > > > Hi

Re: [DISCUSS] KIP-539: Implement mechanism to flush out records in low volume suppression buffers

Hi Richard, Thanks for the KIP proposal. I understand the situation you are describing. But in my mind, if there is a low traffic condition and you need to keep records going downstream at regular intervals, I'm wondering if using suppression is the correct approach. IMHO it seems it would be

[jira] [Resolved] (KAFKA-3534) Deserialize on demand when default time extractor used

[ https://issues.apache.org/jira/browse/KAFKA-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3534. Resolution: Fixed > Deserialize on demand when default time extractor used >

[jira] [Resolved] (KAFKA-4996) Fix findbugs multithreaded correctness warnings for streams

[ https://issues.apache.org/jira/browse/KAFKA-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-4996. Resolution: Fixed The corresponding PR was merged. Closing this ticket. > Fix findbugs

[jira] [Resolved] (KAFKA-7424) State stores restoring from changelog topic not the source topic

[ https://issues.apache.org/jira/browse/KAFKA-7424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7424. Resolution: Fixed [~jhay], [~vvcephei]: I am closing this ticket as it seems to be covered

[jira] [Resolved] (KAFKA-8297) Kafka Streams ConsumerRecordFactory yields difficult compiler error about generics

[ https://issues.apache.org/jira/browse/KAFKA-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-8297. Resolution: Fixed Closing this ticket because the factory class was deprecated via 

Build failed in Jenkins: kafka-trunk-jdk8 #3979

See Changes: [jason] KAFKA-8834; Add reassignment metrics and distinguish URPs (KIP-352) [jason] KAFKA-8962; Use least loaded node for AdminClient#describeTopics (#7421)

[jira] [Resolved] (KAFKA-8994) Streams should expose standby replication information & allow stale reads of state store

[ https://issues.apache.org/jira/browse/KAFKA-8994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinoth Chandar resolved KAFKA-8994. --- Resolution: Fixed > Streams should expose standby replication information & allow stale

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

Thanks Richard, I'm +1 on the KIP On Thu, Oct 17, 2019 at 3:51 PM Richard Yu wrote: > Hi Guozhang, Jason, > > I've updated the KIP to include this warning as well. > If there is anything else that we need for it, let me know. :) > Otherwise, we should vote this KIP in. > > Cheers, > Richard > >

Re: [VOTE] KIP-534: Retain tombstones for approximately delete.retention.ms milliseconds

It's true that the size of the tombstone or the control marker could increase after a round of cleaning. This can already happen with re-compression. We already have the logic in the log cleaner to auto grow the read/write buffer during cleaning and can accommodate for an oversized message. The

Jenkins build is back to normal : kafka-2.3-jdk8 #131

See

[jira] [Created] (KAFKA-9067) BigDecimal conversion unnecessarily enforces the scale

Piotr Smolinski created KAFKA-9067: -- Summary: BigDecimal conversion unnecessarily enforces the scale Key: KAFKA-9067 URL: https://issues.apache.org/jira/browse/KAFKA-9067 Project: Kafka

[jira] [Created] (KAFKA-9066) Kafka Connect JMX : source & sink task metrics missing for tasks in failed state

Mikołaj Stefaniak created KAFKA-9066: Summary: Kafka Connect JMX : source & sink task metrics missing for tasks in failed state Key: KAFKA-9066 URL: https://issues.apache.org/jira/browse/KAFKA-9066

[VOTE] 2.3.1 RC2

We found a few more critical issues and so have decided to do one more RC for 2.3.1. Please review the release notes: https://home.apache.org/~davidarthur/kafka-2.3.1-rc2/RELEASE_NOTES.html *** Please download, test and vote by Tuesday, October 22, 9pm PDT Kafka's KEYS file containing PGP keys

Build failed in Jenkins: kafka-2.4-jdk8 #26

See Changes: [jason] KAFKA-8962; Use least loaded node for AdminClient#describeTopics (#7421) -- [...truncated 2.69 MB...] org.apache.kafka.streams.test.OutputVerifierTest

Build failed in Jenkins: kafka-trunk-jdk11 #892

See Changes: [jason] KAFKA-8834; Add reassignment metrics and distinguish URPs (KIP-352) [jason] KAFKA-8962; Use least loaded node for AdminClient#describeTopics (#7421)

[jira] [Created] (KAFKA-9065) Loading offsets and group metadata loops forever

David Jacot created KAFKA-9065: -- Summary: Loading offsets and group metadata loops forever Key: KAFKA-9065 URL: https://issues.apache.org/jira/browse/KAFKA-9065 Project: Kafka Issue Type: Bug

Build failed in Jenkins: kafka-trunk-jdk8 #3978

See Changes: [rajinisivaram] KAKFA-8950: Fix KafkaConsumer Fetcher breaking on concurrent disconnect [github] MINOR: AbstractRequestResponse should be an interface (#7513) [jason] KAFKA-9004; Prevent older

[jira] [Resolved] (KAFKA-8962) KafkaAdminClient#describeTopics always goes through the controller

[ https://issues.apache.org/jira/browse/KAFKA-8962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8962. Fix Version/s: 2.4.0 Resolution: Fixed > KafkaAdminClient#describeTopics always