[jira] [Resolved] (KAFKA-8984) Improve tagged fields documentation

[ https://issues.apache.org/jira/browse/KAFKA-8984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8984. -- Fix Version/s: 2.4.0 Resolution: Fixed Issue resolved by pull request 7477 [https://github.com/a

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

See Changes: [github] MINOR: Return null in key mapping of committed (#7659) [github] KAFKA-8677: Simplify the best-effort network client poll to never throw -- [...trun

[jira] [Resolved] (KAFKA-9133) LogCleaner thread dies with: currentLog cannot be empty on an unexpected exception

[ https://issues.apache.org/jira/browse/KAFKA-9133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9133. Resolution: Fixed > LogCleaner thread dies with: currentLog cannot be empty on an unexpecte

Re: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

This would be great. Maintaining Scala 2.11 support is reasonably painful. Dropping support in 2.5 sounds good to me. On Thu, 7 Nov 2019 at 17:35, Ismael Juma wrote: > Hi all, > > I think it's time to simplify our development environment by dropping > support for Scala 2.11. Please take a look a

Re: Subject: [VOTE] 2.2.2 RC2

+1 (non-binding) - Ran testAll/releaseTarGzAll successfully with no failures. - Ran through quickstart of core/streams on builds generated from 2.3.0-rc2 tag. - Ran a few internal apps with ~2500 topic-partitions on 5 a node cluster. Thanks, Satish. On Sat, Nov 9, 2019 at 4:41 AM Bill Bejeck wr

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

See Changes: [wangguoz] MINOR: Return null in key mapping of committed (#7659) [wangguoz] KAFKA-8677: Simplify the best-effort network client poll to never throw -- [...tru

Re: [ANNOUNCE] New committer: Mickael Maison

Congratulations Mickael :) On Fri, Nov 8, 2019 at 12:28 PM Ankit Kumar wrote: > Congratulations Mickael!! > > *Best regards,* > *Ankit Kumar.* > > > On Fri, Nov 8, 2019 at 9:08 PM Viktor Somogyi-Vass < > viktorsomo...@gmail.com> > wrote: > > > Congrats Mickael!! :) > > > > On Fri, Nov 8, 2019 at

Re: Subject: [VOTE] 2.2.2 RC2

- verified signatures - built it from source - ran unit tests +1 (non-binding) Thanks for running the release, Randall! -Bill On Fri, Nov 8, 2019 at 4:40 PM David Arthur wrote: > * Glanced through docs, release notes > * Downloaded RC2 binaries, verified signatures > * Ran through qu

Re: [VOTE] KIP-543: Expand ConfigCommand's non-ZK functionality

Thanks everyone. Unless there's any additional input or issues raised, I'll close the vote Monday morning approx 10 am PST. Brian On Thu, Nov 7, 2019 at 10:32 PM Jason Gustafson wrote: > +1 Looking forward to this. I love the quality-of-life changes. > > On Thu, Nov 7, 2019 at 7:00 PM Manikumar

Re: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

Thanks for the KIP Ismael. +1 for me. -Bill On Fri, Nov 8, 2019 at 11:52 AM Ismael Juma wrote: > I was hoping we'd get the documentation update in the 2.4 release notes so > that it's not a surprise for 2.5 users. > > Ismael > > On Fri, Nov 8, 2019 at 8:40 AM Jose Armando Garcia Sancio < > jsan

Re: Subject: [VOTE] 2.2.2 RC2

* Glanced through docs, release notes * Downloaded RC2 binaries, verified signatures * Ran through quickstart +1 binding Thanks for managing this release, Randall! -David On Wed, Nov 6, 2019 at 7:39 PM Eric Lalonde wrote: > Hello, > > In an effort to assist in the verification of release cand

[jira] [Resolved] (KAFKA-8520) TimeoutException in client side doesn't have stack trace

[ https://issues.apache.org/jira/browse/KAFKA-8520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8520. -- Resolution: Duplicate > TimeoutException in client side doesn't have stack trace >

[jira] [Created] (KAFKA-9165) Fix jersey warnings in Trogdor

Colin McCabe created KAFKA-9165: --- Summary: Fix jersey warnings in Trogdor Key: KAFKA-9165 URL: https://issues.apache.org/jira/browse/KAFKA-9165 Project: Kafka Issue Type: Bug Report

Re: [DISCUSS] KIP-544: Make metrics exposed via JMX configurable

Hello, This can be very handy when dealing with large numbers of partitions on a broker. I was recently experimenting with a third-party monitoring framework which provides a JMX collector [1] with the same mechanism to filter out the JMX beans retrieved from Kafka. When running a couple of tests

Re: [VOTE] KIP-544: Make metrics exposed via JMX configurable

Thanks for the KIP, +1 (binding). -Bill On Fri, Nov 8, 2019 at 1:28 PM Gwen Shapira wrote: > +1 (binding) > > On Thu, Nov 7, 2019 at 11:17 AM Xavier Léauté wrote: > > > > Hi everyone, > > > > I'd like to open up the vote for KIP-544 on making exposed JMX metrics > more > > configurable. > > >

[jira] [Resolved] (KAFKA-9016) Warn when log dir stopped serving replicas

[ https://issues.apache.org/jira/browse/KAFKA-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-9016. - Resolution: Fixed > Warn when log dir stopped serving replicas >

Re: [VOTE] KIP-544: Make metrics exposed via JMX configurable

+1 (binding) On Thu, Nov 7, 2019 at 11:17 AM Xavier Léauté wrote: > > Hi everyone, > > I'd like to open up the vote for KIP-544 on making exposed JMX metrics more > configurable. > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-544%3A+Make+metrics+exposed+via+JMX+configurable > > Thank y

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

See Changes: [github] MINOR: Fix version range check in MessageTest (#7663) -- [...truncated 8.31 MB...] org.apache.kafka.streams.test.TestRecordTest > testToString STAR

[jira] [Created] (KAFKA-9164) Don't evict active topics' metadata from the producer's cache

Brian Byrne created KAFKA-9164: -- Summary: Don't evict active topics' metadata from the producer's cache Key: KAFKA-9164 URL: https://issues.apache.org/jira/browse/KAFKA-9164 Project: Kafka Issu

Re: [VOTE] KIP-544: Make metrics exposed via JMX configurable

+1 (binding), thanks! Guozhang On Thu, Nov 7, 2019 at 11:17 AM Xavier Léauté wrote: > Hi everyone, > > I'd like to open up the vote for KIP-544 on making exposed JMX metrics more > configurable. > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-544%3A+Make+metrics+exposed+via+JMX+conf

Re: [DISCUSS] KIP-544: Make metrics exposed via JMX configurable

Sounds good, thanks. Guozhang On Fri, Nov 8, 2019 at 9:26 AM Xavier Léauté wrote: > > > > 1. I do feel there're similar needs for clients make JMX configurable. > Some > > context: in modules like Connect and Streams we have added / refactored a > > large number of metrics so far [0, 1], and al

Re: [ANNOUNCE] New committer: Mickael Maison

Congratulations Mickael!! *Best regards,* *Ankit Kumar.* On Fri, Nov 8, 2019 at 9:08 PM Viktor Somogyi-Vass wrote: > Congrats Mickael!! :) > > On Fri, Nov 8, 2019 at 1:24 PM Satish Duggana > wrote: > > > Congratulations Mickael!! > > > > On Fri, Nov 8, 2019 at 2:50 PM Rajini Sivaram > > wrot

Re: [DISCUSS] KIP-544: Make metrics exposed via JMX configurable

> > 1. I do feel there're similar needs for clients make JMX configurable. Some > context: in modules like Connect and Streams we have added / refactored a > large number of metrics so far [0, 1], and although we've added a reporting > level config [2] to clients, this is statically defined at code

[jira] [Resolved] (KAFKA-8677) Flakey test GroupEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-8677. -- Assignee: Guozhang Wang Resolution: Fixed > Flakey test > GroupEndToEndAuthorizationTest#testNoD

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

I think this KIP affects when we block which is actually user visible behavior. Right? Ismael On Fri, Nov 8, 2019, 8:50 AM Brian Byrne wrote: > Hi Guozhang, > > Regarding metadata expiry, no access times other than the initial lookup[1] > are used for determining when to expire producer metadat

Re: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

I was hoping we'd get the documentation update in the 2.4 release notes so that it's not a surprise for 2.5 users. Ismael On Fri, Nov 8, 2019 at 8:40 AM Jose Armando Garcia Sancio < jsan...@confluent.io> wrote: > Hi Ismael, > > Thanks for the KIP. The KIP LGTM in general. In the KIP you mentione

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Hi Guozhang, Regarding metadata expiry, no access times other than the initial lookup[1] are used for determining when to expire producer metadata. Therefore, frequently used topics' metadata will be aged out and subsequently refreshed (in a blocking manner) every five minutes, and infrequently us

Re: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

Hi Ismael, Thanks for the KIP. The KIP LGTM in general. In the KIP you mentioned: > Deprecate Scala 2.11 build in Kafka 2.4. Kafka 2.4 is in the RC process should we change this to 2.5? -Jose

Re: [ANNOUNCE] New committer: Mickael Maison

Congrats Mickael!! :) On Fri, Nov 8, 2019 at 1:24 PM Satish Duggana wrote: > Congratulations Mickael!! > > On Fri, Nov 8, 2019 at 2:50 PM Rajini Sivaram > wrote: > > > > Congratulations, Mickael, well deserved!! > > > > Regards, > > > > Rajini > > > > On Fri, Nov 8, 2019 at 9:08 AM David Jacot

Re: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

Hi Charly, Java versions have a much bigger impact. The Scala version for the Kafka broker is mostly an implementation detail. The Kafka Streams library for Scala is not as clear, but this is a recent library and I don't think it makes sense to bump the major version for the whole project, we shou

Re: [DISCUSS] KIP-535: Allow state stores to serve stale reads during rebalance

Thanks, Guozhang for going through it again. - 1.1 & 1.2: The main point of adding topicPartition in KeyQueryMetadata is not topicName, but the partition number. I agree changelog topicNames and store names will have 1-1 mapping but we also need the partition number of the changelog for w

Re: [ANNOUNCE] New committer: Mickael Maison

Congratulations Mickael!! On Fri, Nov 8, 2019 at 2:50 PM Rajini Sivaram wrote: > > Congratulations, Mickael, well deserved!! > > Regards, > > Rajini > > On Fri, Nov 8, 2019 at 9:08 AM David Jacot wrote: > > > Congrats Mickeal, well deserved! > > > > On Fri, Nov 8, 2019 at 8:56 AM Tom Bentley wr

Re: Kafka SSH Tunnel Connection without editing hostfile

Hi On Fri, 8 Nov 2019 at 11:13, Akshay Das wrote: > Hi Team, > > I'm trying to consume from a kafka cluster using java client, but the kafka > server can only be accessed via jumphost/ssh tunnel. But even after > creating ssh tunnel we are not able to read because once consumer fetches > metadata

Kafka SSH Tunnel Connection without editing hostfile

Hi Team, I'm trying to consume from a kafka cluster using java client, but the kafka server can only be accessed via jumphost/ssh tunnel. But even after creating ssh tunnel we are not able to read because once consumer fetches metadata it uses original hosts to connect to broker. Is it possible to

Re: [ANNOUNCE] New committer: Mickael Maison

Congratulations, Mickael, well deserved!! Regards, Rajini On Fri, Nov 8, 2019 at 9:08 AM David Jacot wrote: > Congrats Mickeal, well deserved! > > On Fri, Nov 8, 2019 at 8:56 AM Tom Bentley wrote: > > > Congratulations Mickael! > > > > On Fri, Nov 8, 2019 at 6:41 AM Vahid Hashemian < > vahid.

Re: [ANNOUNCE] New committer: Mickael Maison

Congrats Mickeal, well deserved! On Fri, Nov 8, 2019 at 8:56 AM Tom Bentley wrote: > Congratulations Mickael! > > On Fri, Nov 8, 2019 at 6:41 AM Vahid Hashemian > wrote: > > > Congrats Mickael, > > > > Well deserved! > > > > --Vahid > > > > On Thu, Nov 7, 2019 at 9:10 PM Maulin Vasavada < > mau

Re: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

Thanks for the KIP. It is a big +1 from me. David On Fri, Nov 8, 2019 at 2:56 AM Gwen Shapira wrote: > About time :) Let's do it. > > On Thu, Nov 7, 2019 at 5:35 PM Ismael Juma wrote: > > > > Hi all, > > > > I think it's time to simplify our development environment by dropping > > support for

Re: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

This makes sense but as this is a breaking change shouldn’t it be happening in a major version? I believe that’s what was done with java7 support isn’t it? On Fri, 8 Nov 2019 at 01:56, Gwen Shapira wrote: > About time :) Let's do it. > > On Thu, Nov 7, 2019 at 5:35 PM Ismael Juma wrote: > > > >

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

See Changes: [github] KAFKA-9101: Create a fetch.max.bytes configuration for the broker -- [...truncated 5.54 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Re: [DISCUSS] KIP-405: Kafka Tiered Storage

Thanks for those insights Ying. On Thu, Nov 7, 2019 at 9:26 PM Ying Zheng wrote: > > > > > > > > Thanks, I missed that point. However, there's still a point at which the > > consumer fetches start getting served from remote storage (even if that > > point isn't as soon as the local log retention