[jira] [Resolved] (KAFKA-9373) Improve shutdown performance via lazy accessing the offset and time indices.

[ https://issues.apache.org/jira/browse/KAFKA-9373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9373. Fix Version/s: 2.6.0 Resolution: Fixed > Improve shutdown performance via lazy access

Re: [VOTE] KIP-570: Add leader epoch in StopReplicaRequest

Is it really true that the controller always sends two requests? Aren't the operations different (stop replica with delete versus stop replica without)? On Wed, Mar 25, 2020, 9:59 AM David Jacot wrote: > Hi all, > > I'd like to inform you that I have slightly changed the schema which was > propo

Re: [VOTE] 2.5.0 RC2

Hi Boyang, Is this a regression? Ismael On Fri, Mar 20, 2020, 5:43 PM Boyang Chen wrote: > Hey David, > > I would like to raise https://issues.apache.org/jira/browse/KAFKA-9701 as > a > 2.5 blocker. The impact of this bug is that it could throw fatal exception > and kill a stream thread on Kaf

[jira] [Resolved] (KAFKA-9723) Consumers ignore fetched records "since it no longer has valid position"

[ https://issues.apache.org/jira/browse/KAFKA-9723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9723. Resolution: Duplicate Duplicate of KAFKA-9724 > Consumers ignore fetched records "sin

[jira] [Resolved] (KAFKA-9677) Low consume bandwidth quota may cause consumer not being able to fetch data

[ https://issues.apache.org/jira/browse/KAFKA-9677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9677. Fix Version/s: 2.6.0 Resolution: Fixed > Low consume bandwidth quota may cause consumer

[jira] [Resolved] (KAFKA-9404) Use ArrayList instead of LinkedList in Sensor Class

[ https://issues.apache.org/jira/browse/KAFKA-9404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9404. Fix Version/s: 2.6.0 Resolution: Fixed > Use ArrayList instead of LinkedList in Sen

[jira] [Resolved] (KAFKA-3702) SslTransportLayer.close() does not shutdown gracefully

[ https://issues.apache.org/jira/browse/KAFKA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3702. Fix Version/s: 2.0.0 Resolution: Fixed > SslTransportLayer.close() does not shutd

Re: Subject: [VOTE] 2.4.1 RC0

Is this a blocker given that it's been like this for months and no-one noticed? 2.4.1 seemingly has all the votes needed for the release. Why not go ahead with it. When KAFKA-9675 is merged, it can be included in the next release. Ismael On Mon, Mar 9, 2020 at 8:43 PM Bill Bejeck wrote: > Thank

Re: [DISCUSS] Apache Kafka 2.5.0 release

Hi Bruno, 2.4.0 has been out for months. If this was not noticed since then, I don't think it qualifies as a blocker for 2.5.0. Ismael On Mon, Mar 9, 2020 at 8:44 PM Bruno Cadonna wrote: > Hi David, > > A bug report was filed that can be considered a blocker. Basically, > with this bug all Roc

[jira] [Resolved] (KAFKA-8245) Flaky Test DeleteConsumerGroupsTest#testDeleteCmdAllGroups

[ https://issues.apache.org/jira/browse/KAFKA-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8245. Resolution: Fixed > Flaky Test DeleteConsumerGroupsTest#testDeleteCmdAllGro

Re: [VOTE] 2.5.0 RC0

Thanks David! Note that support for Scala 2.11 was removed, not deprecated. On Fri, Feb 28, 2020, 7:47 PM David Arthur wrote: > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of Apache Kafka 2.5.0. > > This is a major release of Kafka which inclu

[jira] [Resolved] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

[ https://issues.apache.org/jira/browse/KAFKA-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9515. Resolution: Fixed > Upgrade ZooKeeper to 3.

[jira] [Created] (KAFKA-9515) Upgrade ZooKeeper to 3.5.7

Ismael Juma created KAFKA-9515: -- Summary: Upgrade ZooKeeper to 3.5.7 Key: KAFKA-9515 URL: https://issues.apache.org/jira/browse/KAFKA-9515 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-8164) Improve test passing rate by rerunning flaky tests

[ https://issues.apache.org/jira/browse/KAFKA-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8164. Fix Version/s: 2.6.0 Resolution: Fixed > Improve test passing rate by rerunning flaky te

[jira] [Reopened] (KAFKA-9491) Fast election during reassignment can lead to replica fetcher failures

[ https://issues.apache.org/jira/browse/KAFKA-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-9491: Reopening as we are still considering a cherry-pick to 2.3. > Fast election during reassignment

[jira] [Resolved] (KAFKA-9491) Fast election during reassignment can lead to replica fetcher failures

[ https://issues.apache.org/jira/browse/KAFKA-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9491. Fix Version/s: 2.4.1 2.5.0 Resolution: Fixed > Fast election dur

Re: [DISCUSS] 2.4.1 Bug Fix Release

Thanks for volunteering, +1. On Mon, Feb 3, 2020, 5:27 PM Bill Bejeck wrote: > Hi All, > > I'd like to volunteer for the release manager of the 2.4.1 bug fix release. > > Kafka 2.4.0 was released on December 16, 2019, and so far 19 issues have > been fixed since then. > > Here is a complete list

[jira] [Resolved] (KAFKA-9027) Replace CreateAcls request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9027. Fix Version/s: 2.5.0 Assignee: Ismael Juma (was: Mickael Maison) Resolution: Fixed

[jira] [Resolved] (KAFKA-9028) Replace DeleteAcls request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9028. Fix Version/s: 2.5.0 Assignee: Ismael Juma (was: Mickael Maison) Resolution: Fixed

[jira] [Resolved] (KAFKA-9408) Use StandardCharsets UTF-8 instead of UTF-8 Name

[ https://issues.apache.org/jira/browse/KAFKA-9408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9408. Fix Version/s: 2.5.0 Resolution: Fixed > Use StandardCharsets UTF-8 instead of UTF-8 N

[jira] [Resolved] (KAFKA-9474) Kafka RPC protocol should support type 'double'

[ https://issues.apache.org/jira/browse/KAFKA-9474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9474. Resolution: Fixed > Kafka RPC protocol should support type 

[jira] [Resolved] (KAFKA-9405) Use Map API computeIfAbsent Where Applicable

[ https://issues.apache.org/jira/browse/KAFKA-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9405. Fix Version/s: 2.5.0 Resolution: Fixed > Use Map API computeIfAbsent Where Applica

[jira] [Resolved] (KAFKA-9426) OffsetsForLeaderEpochClient Use Switch Statement

[ https://issues.apache.org/jira/browse/KAFKA-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9426. Fix Version/s: 2.5.0 Resolution: Fixed > OffsetsForLeaderEpochClient Use Switch Statem

[jira] [Resolved] (KAFKA-9026) Replace DescribeAcls request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-9026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9026. Fix Version/s: 2.5.0 Resolution: Fixed > Replace DescribeAcls request/response w

[jira] [Resolved] (KAFKA-7854) Behavior change in controller picking up partition reassignment tasks since 1.1.0

[ https://issues.apache.org/jira/browse/KAFKA-7854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7854. Resolution: Won't Fix I'm marking this as "Won't fix" since KIP-455 in

Re: CompletableFuture?

Good question. I have a draft KIP for the producer change: https://cwiki.apache.org/confluence/display/KAFKA/KIP-XXX%3A+Return+CompletableFuture+from+KafkaProducer.send I was still debating which was the best path forward (i.e. what should be in rejected alternatives versus the actual proposal).

Re: [ANNOUNCE] New Kafka PMC Members: Colin, Vahid and Manikumar

Congratulations Colin, Vahid and Manikumar! Ismael On Tue, Jan 14, 2020 at 9:30 AM Gwen Shapira wrote: > Hi everyone, > > I'm happy to announce that Colin McCabe, Vahid Hashemian and Manikumar > Reddy are now members of Apache Kafka PMC. > > Colin and Manikumar became committers on Sept 2018 an

[jira] [Resolved] (KAFKA-8786) Deprecated Gradle features making it incompatible with Gradle 6.0.

[ https://issues.apache.org/jira/browse/KAFKA-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8786. Fix Version/s: 2.5.0 Resolution: Fixed > Deprecated Gradle features making it incompati

[jira] [Resolved] (KAFKA-8959) Update Guava to 24 (or newer) or remove dependency

[ https://issues.apache.org/jira/browse/KAFKA-8959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8959. Resolution: Duplicate Marking this as a duplicate of KAFKA-3061 since the newest version of

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

Bejeck * John Roesler * Mickael Maison * Ewen Cheslack-Postava * Colin McCabe * Ismael Juma Non-binding +1s: * Ivan Yurchenko * Satish Duggana * Sean Glover * M. Manna Ismael On Mon, Nov 18, 2019 at 1:19 PM Ismael Juma wrote: > Hi all, > > People seemed supportive in general, so I'd l

[jira] [Created] (KAFKA-9333) Shim `core` module that targets default scala version (KIP-531)

Ismael Juma created KAFKA-9333: -- Summary: Shim `core` module that targets default scala version (KIP-531) Key: KAFKA-9333 URL: https://issues.apache.org/jira/browse/KAFKA-9333 Project: Kafka

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

the Streams Scala DSL nicely. It will > > also > > > affect 2.11 users of embedded-kafka. Are there any other non-broker > > > dependencies that could be affected? > > > > > > Sean > > > > > > On Mon, Nov 18, 2019 at 10:43 AM Ismael Juma > wro

[jira] [Created] (KAFKA-9324) Drop support for Scala 2.11 (KIP-531)

Ismael Juma created KAFKA-9324: -- Summary: Drop support for Scala 2.11 (KIP-531) Key: KAFKA-9324 URL: https://issues.apache.org/jira/browse/KAFKA-9324 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] Apache Kafka 2.5.0 release

+1 Thanks for volunteering David! Ismael On Fri, Dec 20, 2019, 7:00 PM David Arthur wrote: > Greetings! > > I'd like to volunteer to be release manager for the next time-based feature > release which will be 2.5. If there are no objections, I'll send out the > release plan in the next few day

Re: [RESULTS] [VOTE] Release Kafka version 2.4.0

Thanks for driving the release Manikumar! Ismael On Fri, Dec 13, 2019, 5:42 PM Manikumar wrote: > This vote passes with 6 +1 votes (3 bindings) and no 0 or -1 votes. > > +1 votes > PMC Members: > * Gwen Shapira > * Jun Rao > * Guozhang Wang > > Committers: > * Mickael Maison > > Community: > *

[jira] [Resolved] (KAFKA-9212) Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetRequest

[ https://issues.apache.org/jira/browse/KAFKA-9212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9212. Resolution: Fixed > Keep receiving FENCED_LEADER_EPOCH while sending ListOffsetRequ

Re: Broker Interceptors

x27;m > really asking is "how should I have known this?" > > Tom > > On Fri, Dec 6, 2019 at 4:12 PM Ismael Juma wrote: > > > AbstractRequest and AbstractResponse are currently internal classes. > > > > Ismael > > > > On Fri, Dec 6, 2019 at 1

Re: [DISCUSS] KIP-542: Partition Reassignment Throttling

t technically not a reassignment but an > alter-replica-dir event but it's still done with the reassignment tool, so > I'd keep the current functionality of the > --replica-alter-log-dirs-throttle. > Is this aligned with your thinking? > > Viktor > > On Wed, Dec 4,

Re: Broker Interceptors

gt; > vast number of internal classes with general interceptor framework. A > > less > > > general solution more along the lines of the producer/consumer > > > interceptors on the client would satisfy the majority of use cases. If > we > > > are smart, we sh

[jira] [Resolved] (KAFKA-9265) kafka.log.Log instances are leaking on log delete

[ https://issues.apache.org/jira/browse/KAFKA-9265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9265. Fix Version/s: 2.3.2 2.4.0 Resolution: Fixed > kafka.log.Log instan

Re: [DISCUSS] KIP-542: Partition Reassignment Throttling

gt; Viktor > > On Tue, Dec 3, 2019 at 3:28 PM Ismael Juma wrote: > > > Hi Viktor, > > > > The KIP states: > > > > "KIP-73 > > < > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-73+Replication+Quotas > > > > >

Re: Broker Interceptors

The main challenge is doing this without exposing a bunch of internal classes. I haven't seen a proposal that handles that aspect well so far. Ismael On Tue, Dec 3, 2019 at 7:21 AM Sönke Liebau wrote: > Hi Thomas, > > I think that idea is worth looking at. As you say, if no interceptor is > con

Re: [DISCUSS] KIP-542: Partition Reassignment Throttling

Hi Viktor, The KIP states: "KIP-73 added quotas for replication but it doesn't separate normal replication traffic from reassignment. So a user is able to specify the partition and the throttle rate but it will be appli

Re: [VOTE] 2.4.0 RC2

We have a pull request for KAFKA-9156, which fixes a critical regression introduced in 2.3.0. I think we should include this in the next (and hopefully final) 2.4.0 RC. Ismael On Sat, Nov 30, 2019 at 12:31 PM John Roesler wrote: > Hello all, > > I hate to do this, but I've been running a soak t

[jira] [Resolved] (KAFKA-9213) BufferOverflowException on rolling new segment after upgrading Kafka from 1.1.0 to 2.3.1

[ https://issues.apache.org/jira/browse/KAFKA-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9213. Resolution: Duplicate Duplicate of KAFKA-9156. > BufferOverflowException on rolling new segm

Re: Preliminary blog post about the Apache Kafka 2.4.0 release

Manikumar, One thing I had previously missed, should we mention the upgrade to ZK 3.5? Ismael On Thu, Nov 14, 2019 at 10:41 AM Manikumar wrote: > Hi all, > > I've prepared a preliminary blog post about the upcoming Apache Kafka 2.4.0 > release. > Please take a look and let me know if you want

Re: [VOTE] KIP-533: Add default api timeout to AdminClient

+1 (binding) Note that the documentation of the various Options methods will have to be updated as it currently mentions "request timeout". An example from CreateTopicsOptions: "Set the request timeout in milliseconds for this operation or {@code null} if the default request timeout for the Admin

Re: Preliminary blog post about the Apache Kafka 2.4.0 release

That makes sense to me. Ismael On Mon, Nov 18, 2019 at 8:40 AM Sean Glover wrote: > Hi Manikumar, > > I'm putting together an akka.io blog post regarding [KAFKA-7548] - > KafkaConsumer should not throw away already fetched data for paused > partitions. Since it doesn't change any user-facing A

Re: [DISCUSS] KIP-536: Propagate broker timestamp to Admin API

Hi Noa, I understand the desire for batching. However, once you do that, you either need request forwarding or broker metadata propagation. It's worth exploring, but I suspect you will end up with most of the changes needed by the original proposal, in that case. Ismael On Mon, Nov 18, 2019 at 7

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

ide? > > If so, then +1 from me. > > Ivan > > > On Mon, 18 Nov 2019 at 15:19, Ismael Juma wrote: > > > Hi all, > > > > People seemed supportive in general, so I'd like to start a vote on > > KIP-531: > > > > > > > https:

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

Hi all, People seemed supportive in general, so I'd like to start a vote on KIP-531: https://cwiki.apache.org/confluence/display/KAFKA/KIP-531%3A+Drop+support+for+Scala+2.11+in+Kafka+2.5 Ismael

[jira] [Resolved] (KAFKA-9200) ListOffsetRequest missing error response for v5

[ https://issues.apache.org/jira/browse/KAFKA-9200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9200. Fix Version/s: 2.3.2 2.2.3 2.4.0 Resolution: Fixed

[jira] [Resolved] (KAFKA-9196) Records exposed before advancement of high watermark after segment roll

[ https://issues.apache.org/jira/browse/KAFKA-9196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9196. Resolution: Fixed > Records exposed before advancement of high watermark after segment r

[jira] [Resolved] (KAFKA-3096) Leader is not set to -1 when it is shutdown if followers are down

[ https://issues.apache.org/jira/browse/KAFKA-3096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-3096. Resolution: Fixed > Leader is not set to -1 when it is shutdown if followers are d

Re: [DISCUSS] Apache Kafka 2.4.0 release

ki.apache.org/confluence/display/KAFKA/KIP-517%3A+Add+consumer+metrics+to+observe+user+poll+behavior > > > > > >>>> >>>>> > > > > > >>>> >>>> > > > > > >>>> >>>> - KIP-511: Collect and Exp

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

This is not a bug fix, in my opinion. The existing behavior may be confusing, but it was documented, so I assume it was intended. Ismael On Mon, Nov 11, 2019, 2:47 PM Guozhang Wang wrote: > Thanks for the update Brian, I think I agree with Colin that we should > clarify on whether / how the blo

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: [DISCUSS] KIP-531: Drop support for Scala 2.11 in Kafka 2.5

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: > > > > > > Hi all, > > > > > > I think it's time to simplify our development environment by

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

Hi all, I think it's time to simplify our development environment by dropping support for Scala 2.11. Please take a look at the proposal and provide feedback: https://cwiki.apache.org/confluence/display/KAFKA/KIP-531%3A+Drop+support+for+Scala+2.11+in+Kafka+2.5 Ismael

Re: [VOTE] KIP-514 Add a bounded flush() API to Kafka Producer

+1 (binding) On Thu, Oct 24, 2019 at 9:33 PM radai wrote: > Hello, > > I'd like to initiate a vote on KIP-514. > > links: > the kip - > https://cwiki.apache.org/confluence/display/KAFKA/KIP-514%3A+Add+a+bounded+flush%28%29+API+to+Kafka+Producer > the PR - https://github.com/apache/kafka/pull/756

[jira] [Created] (KAFKA-9110) Improve efficiency of disk reads when TLS is enabled

Ismael Juma created KAFKA-9110: -- Summary: Improve efficiency of disk reads when TLS is enabled Key: KAFKA-9110 URL: https://issues.apache.org/jira/browse/KAFKA-9110 Project: Kafka Issue Type

Re: [VOTE] KIP-541: Create a fetch.max.bytes configuration for the broker

+1 (binding) On Thu, Oct 24, 2019, 4:56 PM Colin McCabe wrote: > Hi all, > > I'd like to start the vote on KIP-541: Create a fetch.max.bytes > configuration for the broker. > > KIP: https://cwiki.apache.org/confluence/x/4g73Bw > > Discussion thread: > https://lists.apache.org/thread.html/9d9dde9

Re: [VOTE] KIP-538: Add a metric tracking the number of open connections with a given SSL cipher type

Awesome, +1. Ismael On Wed, Oct 23, 2019 at 3:37 PM Colin McCabe wrote: > Hi Ismael, > > That's a good idea! I added it to the KIP. > > best, > Colin > > > On Wed, Oct 23, 2019, at 12:59, Ismael Juma wrote: > > Hi Colin, > > > > Thanks for t

Re: [VOTE] KIP-538: Add a metric tracking the number of open connections with a given SSL cipher type

Hi Colin, Thanks for the KIP. Would it make sense to have a tag with the TLS version as well? Ismael On Mon, Oct 21, 2019 at 3:43 PM Colin McCabe wrote: > Hi all, > > I'd like to start the vote on KIP-538: Add a metric tracking the number of > open connections with a given SSL cipher type. > >

Re: [DISCUSS] KIP-541: Create a fetch.max.bytes configuration for the broker

Hi Colin, Thanks for the KIP. This is definitely needed. Have we considered having a lower max limit by default? 75 MB is pretty high. Did we consider something like 55 MB, which is 10% above the default for consumers? Ismael On Mon, Oct 21, 2019 at 2:57 PM Colin McCabe wrote: > Hi all, > > I

Re: [VOTE] KIP-537: Increase default zookeeper session timeout

+1 (binding) On Mon, Oct 21, 2019, 5:28 PM Jason Gustafson wrote: > I'd like to start a vote for KIP-537: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-537%3A+Increase+default+zookeeper+session+timeout > . > > +1 from me > > Thanks, > Jason >

Re: [DISCUSS] KIP-533: Add default api timeout to AdminClient

Thanks for the KIP, this makes sense to me. It will be good to align the AdminClient better with the consumer and producer when it comes to timeouts. Ismael On Wed, Oct 9, 2019 at 12:06 PM Jason Gustafson wrote: > Hi All, > > I wrote a short KIP to address a longstanding issue with timeout beha

Re: [VOTE] KIP-352: Distinguish URPs caused by reassignment

reassignment. > > If the broker that died was in the set of new replicas being added, its > death will not add a new under-replicated partition. Otherwise, it will > add a new URP. > > best, > Colin > > > On Wed, Oct 16, 2019, at 11:26, Ismael Juma wrote: > > If a brok

Re: [VOTE] KIP-352: Distinguish URPs caused by reassignment

If a broker dies and loses the disk, is it replication or reassignment? Ismael On Thu, Oct 10, 2019 at 3:30 AM Viktor Somogyi-Vass wrote: > Hi All, > > During the code review it came up that we shouldn't count replication bytes > together with reassignment bytes so they count to a different met

Re: [DISCUSS] KIP-537: Increase default zookeeper session timeout

Thanks for the KIP, +1 (binding). Ismael On Tue, Oct 15, 2019 at 4:41 PM Jason Gustafson wrote: > Hi All, > > I have a short KIP to raise the default zk session timeout: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-537%3A+Increase+default+zookeeper+session+timeout > . > Please take

Re: [DISCUSS] Apache Kafka 2.4.0 release

-progress PRs. > > Please ensure that all major features have been merged and that any minor > > features have PRs by EOD Friday. > > We will be cutting the 2.4 release branch early on Monday morning. > > > > Thanks, > > Manikumar > > > > On Thu, Sep 26

[jira] [Created] (KAFKA-8991) Enable scalac optimizer

Ismael Juma created KAFKA-8991: -- Summary: Enable scalac optimizer Key: KAFKA-8991 URL: https://issues.apache.org/jira/browse/KAFKA-8991 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-8952) Vulnerabilities found for jackson-databind-2.9.9

[ https://issues.apache.org/jira/browse/KAFKA-8952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8952. Fix Version/s: 2.4.0 2.2.2 Resolution: Fixed > Vulnerabilities found

[jira] [Created] (KAFKA-8959) Update Guava to 24 (or newer) or remove dependency

Ismael Juma created KAFKA-8959: -- Summary: Update Guava to 24 (or newer) or remove dependency Key: KAFKA-8959 URL: https://issues.apache.org/jira/browse/KAFKA-8959 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-8956) Refactor DelayedCreatePartitions#updateWaiting to avoid modifying collection in foreach

[ https://issues.apache.org/jira/browse/KAFKA-8956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8956. Fix Version/s: 2.4.0 Reviewer: Colin McCabe Assignee: Ismael Juma (was: Colin

[jira] [Resolved] (KAFKA-8471) Replace control requests/responses with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-8471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8471. Fix Version/s: 2.4.0 Reviewer: Colin McCabe Resolution: Fixed > Replace cont

Re: [DISCUSS] Apache Kafka 2.4.0 release

>> Thanks > > > > > > >> > > > >> > > > > > > >> > > > >> On Mon, Sep 16, 2019 at 10:56 AM Manikumar < > > > > > > >> > manikumar.re...@gmail.com > > > > > > >> > > > >

Re: [DISCUSS] Streams-Broker compatibility regression in 2.2.1 release

+1 to the proposal. Let's also highlight this in the release notes for 2.2.2 and 2.3.0 please. Ismael On Wed, Sep 11, 2019 at 10:23 AM Matthias J. Sax wrote: > Hi, > > recently a user reported an issue upgrading a Kafka Streams application > from 2.2.0 to 2.2.1 (cf > https://mail-archives.apach

Re: [VOTE] KIP-500: Replace ZooKeeper with a Self-Managed Metadata Quorum

Thanks for the KIP, +1 (binding). Ismael On Mon, Sep 9, 2019, 8:28 AM Colin McCabe wrote: > Hi all, > > I'd like to start the vote for KIP-500: Replace ZooKeeper with a > Self-Managed Metadata Quorum. > > The DISCUSS thread from the mailing list is here: > > https://lists.apache.org/thread.html

Re: [DISCUSS] KIP-504 - Add new Java Authorizer Interface

Hi Jun, As you say, even though the average number of operations may be low, the request rate can be high in bursts. This can overwhelm the request queue and cause an outage for no good reason. Or the backing storage system may be slow for a period of time, causing a similar issue. I've seen seve

Re: [DISCUSS] KIP-504 - Add new Java Authorizer Interface

he KIP to > make *createAcls()* and *deleteAcls()* asynchronous. Also added a section > under `*Rejected Alternatives*` for async *authorize()*, which we can > revisit in future if requirement arises. > > Regards, > > Rajini > > > On Fri, Sep 6, 2019 at 9:17 PM Ismael J

Re: [DISCUSS] KIP-504 - Add new Java Authorizer Interface

At least in Apache Ranger implementation, we would > be okay using sync operation. I am not sure if any other plugin > implementation would benefit from async implementation. > > Thanks > > Bosco > > On 9/6/19, 8:45 AM, "Ismael Juma" wrote: > > One more thi

Re: [DISCUSS] KIP-504 - Add new Java Authorizer Interface

a bit ugly). What about the other methods, is there consensus that they should be updated to return CompletionStage? Ismael On Fri, Sep 6, 2019, 8:32 AM Ismael Juma wrote: > I'm on the move, but what Rajini said seems reasonable. I don't think > using SSDs solves the issue. Th

Re: [DISCUSS] KIP-504 - Add new Java Authorizer Interface

feels weird that all the logic of request > > handling post authorize() is now handled by external threads inside a > > plugin. It's not clear how we can configure and monitor them, and how > > throttling would work. Perhaps we can provide a bit more detail on the > new >

Re: [DISCUSS] 2.3.1 Bug Fix Release

Thanks for volunteering David, +1. On Thu, Sep 5, 2019, 3:50 PM David Arthur wrote: > Hey everyone, > > I'd like to volunteer for the Kafka 2.3.1 bug fix release. Kafka 2.3.0 was > released last month on August 6 and a number of issues have been fixed > since then including several critical and

Re: [DISCUSS] KIP-504 - Add new Java Authorizer Interface

Hi Jun, I think it's important to discuss the pluggable API versus the calling implementation as two separate points. >From an API perspective, are you suggesting that we should tell users that they cannot block in authorize? Or are you saying that it's OK to block on authorize on occasion and th

Re: [DISCUSS] KIP-515: Enable ZK client to use the new TLS supported authentication

Hi Pere, Thanks for the KIP. With regards to the CLI tools, most of them support direct access to ZK for compatibility reasons and we encourage usage of the Kafka protocol instead. I am not sure we should be extending them as described in the KIP. What are your thoughts on that? Ismael On Thu, A

[jira] [Resolved] (KAFKA-8837) Several integration tests incorrectly use verifyNonDaemonThreadsStatus

[ https://issues.apache.org/jira/browse/KAFKA-8837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8837. Fix Version/s: 2.4.0 Resolution: Fixed > Several integration tests incorrectly

[jira] [Resolved] (KAFKA-7553) Jenkins PR tests hung

[ https://issues.apache.org/jira/browse/KAFKA-7553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7553. Resolution: Fixed I'm going to mark this as fixed since this is pretty old. I have seen

[jira] [Resolved] (KAFKA-7937) Flaky Test ResetConsumerGroupOffsetTest.testResetOffsetsNotExistingGroup

[ https://issues.apache.org/jira/browse/KAFKA-7937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-7937. Resolution: Fixed Assignee: Bob Barrett (was: Gwen Shapira) Should be fixed by [https

[jira] [Resolved] (KAFKA-8798) SaslOAuthBearerSslEndToEndAuthorizationTest.testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8798. Resolution: Duplicate Duplicate of KAFKA-8800

[jira] [Resolved] (KAFKA-8772) Flaky Test kafka.api.DelegationTokenEndToEndAuthorizationTest.testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8772. Resolution: Duplicate Duplicate of KAFKA-8800. > Flaky T

[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 ] Ismael Juma resolved KAFKA-8677. Resolution: Duplicate Duplicate of KAFKA-8800. > Flakey test > GroupEndToEndAuthorizati

[jira] [Resolved] (KAFKA-8692) Transient failure in kafka.api.SaslScramSslEndToEndAuthorizationTest.testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8692. Resolution: Duplicate Duplicate of KAFKA-8800. > Transient failure

[jira] [Resolved] (KAFKA-8783) SaslOAuthBearerSslEndToEndAuthorizationTest.testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8783. Resolution: Duplicate Duplicate of KAFKA-8800

[jira] [Resolved] (KAFKA-8800) Flaky Test SaslScramSslEndToEndAuthorizationTest#testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-8800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-8800. Resolution: Fixed Fix Version/s: 2.3.1 2.4.0 > Flaky T

Re: [DISCUSS] Apache Kafka 2.4.0 release

Thanks for volunteering Manikumar. +1 Ismael On Mon, Aug 12, 2019 at 7:54 AM Manikumar wrote: > Hi all, > > I would like to volunteer to be the release manager for our next time-based > feature release (v2.4.0). > > If that sounds good, I'll post the release plan over the next few days. > > Tha

[jira] [Created] (KAFKA-8788) Optimize client metadata handling with a large number of partitions

Ismael Juma created KAFKA-8788: -- Summary: Optimize client metadata handling with a large number of partitions Key: KAFKA-8788 URL: https://issues.apache.org/jira/browse/KAFKA-8788 Project: Kafka

Re: [DISCUSS] KIP-487: Automatic Topic Creation on Producer

day to block this accidental > creation > > > and > > > > > allowing clients to take control. > > > > > > > > > > Again, I hope I'm not misinterpreting, but I don't see how this can > > be > > > > > turned o

<    2   3   4   5   6   7   8   9   10   11   >