Thanks for the KIP, +1 (binding).
Ismael
On Mon, Nov 16, 2020 at 3:33 AM Rajini Sivaram
wrote:
> Hi all,
>
> I would like to start vote on KIP-684 to support TLS client authentication
> (mTLS) on SASL_SSL listeners:
>
>-
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-684+-+Suppor
[
https://issues.apache.org/jira/browse/KAFKA-10469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-10469.
-
Fix Version/s: 2.8.0
Resolution: Fixed
> Respect logging hierarchy (KIP-
Hi Leonid,
Thanks for looking into this. I think the main question is how
virtual threads would help here. Kafka tends to use a small number of
threads combined with non blocking IO, but there are some exceptions like
disk IO. My understanding is that the latter is still blocking even with
the lat
Thanks for the KIP Rajini. It's a good proposal. One suggestion for
consideration:
1. We could print a warning if the unprefixed `ssl.client.auth` is used and
there is a SASL_SSL listener. Then we could consider removing this
inconsistency in Kafka 4.0 or something like that.
What do you think?
Hi Mickael,
Any updates on this release?
Ismael
On Thu, Oct 1, 2020 at 7:40 AM Mickael Maison
wrote:
> Hi,
>
> I'd like to volunteer to be the release manager for the next bugfix
> release, 2.6.1.
> I created the release plan on the wiki:
> https://cwiki.apache.org/confluence/display/KAFKA/Rel
Congratulations Sophie!
Ismael
On Mon, Oct 19, 2020 at 9:41 AM Matthias J. Sax wrote:
> Hi all,
>
> I am excited to announce that A. Sophie Blee-Goldman has accepted her
> invitation to become an Apache Kafka committer.
>
> Sophie is actively contributing to Kafka since Feb 2019 and has
> accum
Congratulations Chia-Ping!
Ismael
On Mon, Oct 19, 2020 at 10:25 AM Guozhang Wang wrote:
> Hello all,
>
> I'm happy to announce that Chia-Ping Tsai has accepted his invitation to
> become an Apache Kafka committer.
>
> Chia-Ping has been contributing to Kafka since March 2018 and has made 74
> c
Congratulations David!
Ismael
On Fri, Oct 16, 2020 at 9:01 AM Gwen Shapira wrote:
> The PMC for Apache Kafka has invited David Jacot as a committer, and
> we are excited to say that he accepted!
>
> David Jacot has been contributing to Apache Kafka since July 2015 (!)
> and has been very active
Thanks for the KIP, +1 (binding).
On Mon, Jul 27, 2020 at 1:09 AM Dániel Urbán wrote:
> Hello everyone,
>
> I'd like to start a vote on KIP-635. The KIP enhances the GetOffsetShell
> tool by enabling querying multiple topic-partitions, adding new filtering
> options, and adding a config override
Thanks Mickael! +1
Ismael
On Thu, Oct 1, 2020 at 7:40 AM Mickael Maison
wrote:
> Hi,
>
> I'd like to volunteer to be the release manager for the next bugfix
> release, 2.6.1.
> I created the release plan on the wiki:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+2.6.1
>
> Tha
Thanks for proposing this Matthias. A couple of questions:
1. How did you decide where to increase the time?
2. Do you think there's a risk that having more time won't necessarily
help, we will just try to fit more things? I've seen that happen in similar
circumstances.
Ismael
On Tue, Sep 29, 20
> > > > were planning to generate the clusterId.
> > > >
> > > > Thanks,
> > > > Jason
> > > >
> > > >
> > > > On Thu, Sep 24, 2020 at 11:10 AM Jun Rao wrote:
> > > >
> > > > > Hi, Justine,
Also, can we provide more details on how the Partition Metadata file will
be used?
Ismael
On Thu, Sep 24, 2020 at 3:01 AM Ismael Juma wrote:
> Hi Justine,
>
> I think we need to update the "Rejected Alternatives" section to take into
> account that the proposal now remov
Hi Justine,
I think we need to update the "Rejected Alternatives" section to take into
account that the proposal now removes the topic name from the fetch
request. Also, if we are removing it from the Fetch request, does it make
sense not to remove it from similar requests like ListOffsetRequest?
Thanks for the KIP, Dongjin. Have we considered switching to the log4j2
logging config format by default and providing a mechanism to use the old
format? It is likely that we will release 3.0 as the release after 2.7, so
it would provide a good opportunity to move on from the legacy config
format.
[
https://issues.apache.org/jira/browse/KAFKA-10447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-10447.
-
Fix Version/s: 2.7.0
Resolution: Fixed
> Migrate tools module to JUni
Thanks for the KIP. I think the main question is what's the upper bound for
message size you are looking to support. Is it hundreds of MBs, GBs, tens
of GBs, something else? That would inform the options.
Ismael
On Thu, Sep 10, 2020 at 8:03 AM Gwen Shapira wrote:
> There is another option of do
[
https://issues.apache.org/jira/browse/KAFKA-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-10468.
-
Resolution: Duplicate
Duplicate of KAFKA-10403.
> Log4jController.getLoggers serializat
[
https://issues.apache.org/jira/browse/KAFKA-10403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-10403.
-
Fix Version/s: 2.7.0
Resolution: Fixed
> Replace scala collection by java collection
Thanks David! This is very helpful.
Ismael
On Tue, Sep 1, 2020, 3:15 PM David Arthur wrote:
> Following the migration to the new ci-builds.apache.org, our existing PR
> builder jobs stopped working. This was due to the removal of a github
> plugin which we relied on. While looking into how to f
Ismael Juma created KAFKA-10447:
---
Summary: Migrate tools module from JUnit 4 to JUnit 5
Key: KAFKA-10447
URL: https://issues.apache.org/jira/browse/KAFKA-10447
Project: Kafka
Issue Type: Sub
Ismael Juma created KAFKA-10444:
---
Summary: Migrate PR jobs to new Apache Infra Jenkins
Key: KAFKA-10444
URL: https://issues.apache.org/jira/browse/KAFKA-10444
Project: Kafka
Issue Type: Task
+1
On Fri, Aug 14, 2020 at 7:42 AM John Roesler wrote:
> Thanks Nikolay,
>
> No objection. This would be very nice to have.
>
> Thanks,
> John
>
> On Fri, Aug 14, 2020, at 09:18, Nikolay Izhikov wrote:
> > Hello.
> >
> > > If anyone's interested in porting it to Python 3 it would be a good
> cha
Thanks for volunteering Bill. :)
Ismael
On Thu, Aug 13, 2020 at 3:13 PM Bill Bejeck wrote:
> Hi All,
>
> I'd like to volunteer to be the release manager for our next feature
> release, 2.7. If there are no objections, I'll send out the release plan
> soon.
>
> Thanks,
> Bill Bejeck
>
[
https://issues.apache.org/jira/browse/KAFKA-10134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-10134:
-
> High CPU issue during rebalance in Kafka consumer after upgrading to
Thanks for the KIP, +1 (binding). A couple of comments:
1. We have "quorum.voters=1@kafka-1:9092, 2@kafka-2:9092,
3@kafka-3:9092". Could
this be a bit confusing given that the authority part of a url is defined
as "authority = [userinfo@]host[:port]"?
2. With regards to the Quorum State file, do w
in the new CI server. Waiting for Apache Infra to either install
it or to tell us that we need an alternative.
Let me know if you have any questions or if you see anything weird.
Ismael
On Tue, Aug 11, 2020 at 12:50 AM Ismael Juma wrote:
> Hi all,
>
> Looks like we have 4 days to migra
Congratulations John!
Ismael
On Mon, Aug 10, 2020 at 1:11 PM Jun Rao wrote:
> Hi, Everyone,
>
> John Roesler has been a Kafka committer since Nov. 5, 2019. He has remained
> active in the community since becoming a committer. It's my pleasure to
> announce that John is now a member of Kafka PMC
Hi all,
Looks like we have 4 days to migrate all of our Jenkins builds to the new
CI server. I have started the process:
https://ci-builds.apache.org/job/Kafka/
To avoid confusion, I have disabled the equivalent builds in the old CI
server. I will migrate a few more tomorrow.
Ismael
--
[
https://issues.apache.org/jira/browse/KAFKA-9935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9935.
Resolution: Duplicate
Closing as duplicate of KAFKA-9752. Please reopen if reproduced with 2.5.0
[
https://issues.apache.org/jira/browse/KAFKA-10105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-10105.
-
Resolution: Duplicate
Closing as duplicate of KAFKA-9752. Please reopen if reproduced with
[
https://issues.apache.org/jira/browse/KAFKA-10378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-10378:
-
> issue when create producer using j
rles Feduke, Chia-Ping Tsai, Chris
> Egerton, Colin Patrick McCabe, Daniel, Daniel Beskin, David Arthur, David
> Jacot, David Mao, dengziming, Dezhi “Andy” Fang, Dima Reznik, Dominic
> Evans, Ego, Eric Bolinger, Evelyn Bayes, Ewen Cheslack-Postava, fantayeneh,
> feyman2016, Florian Hussonn
+1 (binding), verified signatures, ran the tests on the source archive with
Scala 2.13 and Java 14 and verified the quickstart with the source archive
and Scala 2.13 binary archive.
Thanks,
Ismael
On Tue, Jul 28, 2020, 2:52 PM Randall Hauch wrote:
> Hello Kafka users, developers and client-deve
Congratulations Mickael!
Ismael
On Fri, Jul 31, 2020, 8:15 AM Jun Rao wrote:
> Hi, Everyone,
>
> Mickael Maison has been a Kafka committer since Nov. 5, 2019. He has
> remained active in the community since becoming a committer. It's my
> pleasure to announce that Mickael is now a member of Kaf
+1 (binding), verified signatures, ran the tests on the source archive with
Scala 2.13 and Java 11 and verified the quickstart with the source archive
and Scala 2.13 binary archive.
Ismael
On Thu, Jul 23, 2020 at 7:39 PM John Roesler wrote:
> Hello Kafka users, developers and client-developers,
Hi Chia-Ping,
Thanks for the KIP. It seems like the path chosen here would cause a
massive impact to user code. Are there options with lower impact that still
help us achieve the goal for those who need it? For example, it could be an
opt-in thing instead of forcing the world to change.
Ismael
O
[
https://issues.apache.org/jira/browse/KAFKA-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9996.
Fix Version/s: 2.5.1
2.4.2
2.6.0
Resolution: Fixed
Hi John,
Thanks for reporting the issue. Let's continue the discussion in the PR.
Ismael
On Mon, Jul 6, 2020 at 7:13 PM John Malizia wrote:
> Hi there, about a week ago I submitted an issue report and an associated PR
>
> https://issues.apache.org/jira/browse/KAFKA-10207
> https://github.com/a
Hi Mario,
Thanks for submitting the KIP. With Apache Kafka 3.0 approaching due to
KIP-500, it's a good time to tackle a metrics upgrade that may have
compatibility implications. Having said that, it would be good to avoid
unnecessary breaking changes. Is there a way to avoid changing the metric
na
ome major changes like support for ZK encryption and a few
> > others, I was wondering if we should choose a smaller upgrade in such
> cases
> > as we don't really require the new features in 2.5 and above right now.
> >
> > -
> > Sankalp
> >
> > On Wed,
er
> than trying to find out the best performance possible for the "right"
> number of partitions.
>
> Thanks.
>
>
>
>
>
>
>
>
>
> On Wed, Jun 24, 2020 at 4:07 AM Ismael Juma wrote:
>
> > Thanks for the KIP. A couple of questions:
> &
Hi Sankalp,
Is there a reason why you cannot upgrade to Apache Kafka 2.5.0 instead? We
are working on the 2.5.1 release, which would be the recommended release.
Ismael
On Wed, Jun 24, 2020 at 6:18 AM Sankalp Bhatia
wrote:
> Hi All,
>
> I would like to know if there are any plans to release a 2
nder these
> > four cases.
> > If brokerAutoTopicCreationEnable and producerAutoCreateTopicsPolicy
> > are true: assertTrue(topicCreated)
> > else : intercept[ExecutionException]
> >
> > Looking forward to your feedback and comments. Thanks.
&
Congratulations Boyang!
Ismael
On Mon, Jun 22, 2020 at 4:26 PM Guozhang Wang wrote:
> The PMC for Apache Kafka has invited Boyang Chen as a committer and we are
> pleased to announce that he has accepted!
>
> Boyang has been active in the Kafka community more than two years ago.
> Since then he
Thanks for the KIP. A couple of questions:
1. Have we considered reusing the existing PolicyViolation error code and
renaming it? This would make it simpler to handle on the client.
2. What version was used for the perf section? I think master should do
better than what's described there.
Ismael
ed
it. Adjust new clients to treat POLICY_VIOLATION like AUTHORIZATION_FAILED,
but propagate the custom error message.
Ismael
On Mon, Jun 22, 2020 at 11:00 PM Colin McCabe wrote:
> > > > On Fri, Jun 19, 2020 at 3:18 PM Ismael Juma
> wrote:
> > > >
> > > > >
Thanks for the reply Boyang. Comments inline.
On Mon, Jun 22, 2020 at 9:31 AM Boyang Chen
wrote:
> Thanks for the questions Ismael.
>
> On Fri, Jun 19, 2020 at 3:18 PM Ismael Juma wrote:
>
> > Hi Colin,
> >
> > The KIP states in the Compatibility section (not Fut
Violation
from MetadataRequest. And mention this in the release notes.
Ismael
On Fri, Jun 19, 2020 at 1:02 PM Colin McCabe wrote:
> On Thu, Jun 18, 2020, at 10:20, Ismael Juma wrote:
> > Hi Boyang,
> >
> > Sorry for being late on this. I'm generally in favor of the KIP, b
Hi Boyang,
Sorry for being late on this. I'm generally in favor of the KIP, but it
seems like it has two missing things:
1. It doesn't cover how this new channel will be configured. That's a
critical part of having a KIP that comprises all that is needed to merge
the relevant PR.
2. It doesn't st
[
https://issues.apache.org/jira/browse/KAFKA-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-8864.
Resolution: Duplicate
Given the version, it looks like a duplicate of KAFKA-7709.
> Ka
; https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+2.5.1
> >
> > Thanks,
> > -John
> >
> > On Fri, May 29, 2020, at 13:16, Bill Bejeck wrote:
> > > Thanks for volunteering John, +1.
> > >
> > > On Fri, May 29, 2020 at 1:58 PM Ismael J
Ismael Juma created KAFKA-10116:
---
Summary: GraalVM native-image prototype
Key: KAFKA-10116
URL: https://issues.apache.org/jira/browse/KAFKA-10116
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-10074.
-
Reviewer: Rajini Sivaram
Resolution: Fixed
> Improve performance of `matchingA
Ismael Juma created KAFKA-10074:
---
Summary: Improve performance of `matchingAcls`
Key: KAFKA-10074
URL: https://issues.apache.org/jira/browse/KAFKA-10074
Project: Kafka
Issue Type: Improvement
Thanks for volunteering! +1
Ismael
On Fri, May 29, 2020 at 8:56 AM John Roesler wrote:
> Hello all,
>
> I'd like to volunteer as release manager for the 2.5.1 bugfix release.
>
> Kafka 2.5.0 was released on 15 April 2020, and 40 issues have been fixed
> since then.
>
> The release plan is docum
nd.scala#L299
> >
> > And some tests.
> >
> > What do you think?
> >
> > Thanks
> > Badai
> >
> > On Fri, May 22, 2020 at 6:45 PM Badai Aqrandista
> > wrote:
> >
> > > Voting thread has been posted.
> > >
ess. We create Node instances using
> InetSocketAddress.getHostString(), so that gives us the original bootstrap
> host. And that should ensure we use all IPs for use_all_dns_ips. Have I
> missed something?
>
> Regards,
>
> Rajini
>
> On Tue, May 26, 2020 at 6:51 AM Ismael Jum
Badai,
I was looking at the code and it seems like we should change how the
bootstrap resolution is done as part of this KIP. The way it works at the
moment follows:
1. We create a single InetSocketAddress by calling the constructor with the
host and port. That invokes InetAddress.getByName(host)
Thanks for the KIP, +1 (binding).
Ismael
On Fri, May 22, 2020 at 1:40 AM Badai Aqrandista wrote:
> Hi All,
>
> I would like to start the vote on KIP-602: Change default value for
> client.dns.lookup
>
> For reference, here is the KIP wiki:
>
>
> https://cwiki.apache.org/confluence/display/KAFKA
Badai, would you like to start a vote on this KIP?
Ismael
On Wed, May 20, 2020 at 7:45 AM Rajini Sivaram
wrote:
> Deprecating for removal in 3.0 sounds good.
>
> On Wed, May 20, 2020 at 3:33 PM Ismael Juma wrote:
>
> > Is there any reason to use "use_first_dns_i
Nikolay, you have enough votes and 72 hours have passed, so you can close
this vote as successful whenever you're ready.
Ismael
On Mon, Mar 2, 2020 at 10:55 AM Nikolay Izhikov wrote:
> Hello.
>
> I would like to start vote for KIP-573: Enable TLSv1.3 by default
>
> KIP -
> https://cwiki.apache.
after java8 get TLSv1.3
> support remove it.
> > 2. Or we can wait and enable it after java8 update.
> >
> > What do you think?
> >
> >> 18 мая 2020 г., в 22:51, Ismael Juma написал(а):
> >>
> >> Yeah, agreed. One option is to actually only c
Thanks for the KIP, +1 (binding)
On Mon, Mar 2, 2020 at 10:55 AM Nikolay Izhikov wrote:
> Hello.
>
> I would like to start vote for KIP-573: Enable TLSv1.3 by default
>
> KIP -
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-573%3A+Enable+TLSv1.3+by+default
> Discussion thread -
> https:
, this change will not affect higher level
> > >> protocol like SSL or SASL.
> > >>
> > >> PR coming after this.
> > >>
> > >> Thanks
> > >> Badai
> > >>
> > >> [1]
> > >>
> >
> htt
we are going to remove this
> compatibility hack in the next major release of Kafka? In other words, in
> Kafka 3.0, will we enable TLS 1.3 by default even if the cipher suite is
> specified?
>
> best,
> Colin
>
>
> On Mon, May 18, 2020, at 09:26, Ismael Juma wrote:
&
Hey Colin,
Note that the clients expose "Map metrics()".
So, some things are already exposed. I generally agree that we should be
very clear about the new classes we are exposing as public APIs via this.
Ismael
On Mon, May 18, 2020 at 11:29 AM Colin McCabe wrote:
> KafkaMetrics isn't a public
Hi Jeff,
I think the idea is good, but I have 2 questions/comments:
1. The monitor method is documented to "get" metrics, but it takes a
`Metrics` instance. Either the method name/signature needs to be adjusted
or the documentation.
2. Instead of exposing the Metrics class, which is currently not
ltSslEngineFactory.java#L218
> > [2]
> https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/common/security/ssl/DefaultSslEngineFactory.java#L164
> >
> >> 18 мая 2020 г., в 17:34, Ismael Juma написал(а):
> >>
> >> Nikolay,
&g
/apache/kafka/common/security/ssl/DefaultSslEngineFactory.java#L164
>
> > 18 мая 2020 г., в 17:34, Ismael Juma написал(а):
> >
> > Nikolay,
> >
> > Thanks for the comments. More below:
> >
> > 1. I meant that `ssl.protocol` is TLSv1.2 while `ssl.enabled.pr
.
Ismael
On Mon, May 18, 2020 at 7:34 AM Ismael Juma wrote:
> Nikolay,
>
> Thanks for the comments. More below:
>
> 1. I meant that `ssl.protocol` is TLSv1.2 while `ssl.enabled.protocols` is
> `TLSv1.2, TLSv1.3`. How do these two configs interact?
> 2. My question is not abo
Nikolay,
Thanks for the comments. More below:
1. I meant that `ssl.protocol` is TLSv1.2 while `ssl.enabled.protocols` is
`TLSv1.2, TLSv1.3`. How do these two configs interact?
2. My question is not about obsolete protocols, it is about people using
TLS 1.2 with specified cipher suites. How will t
> already adopted by [2]
>
> [1]
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-573%3A+Enable+TLSv1.3+by+default
> [2]
> https://github.com/apache/kafka/commit/172409c44b8551e2315bd93044a8a95ccda4699f
>
> > 18 мая 2020 г., в 01:34, Ismael Juma написал(а):
[
https://issues.apache.org/jira/browse/KAFKA-9720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9720.
Assignee: Ismael Juma
Resolution: Fixed
> Update gradle to
d behavior and add tests to
verify it.
Ismael
On Thu, Apr 30, 2020 at 9:47 AM Nikolay Izhikov wrote:
> Ticket created:
>
> https://issues.apache.org/jira/browse/KAFKA-9943
>
> I will prepare the PR, shortly.
>
> > 27 апр. 2020 г., в 17:55, Ismael Juma написал(а):
> &
Before we deprecate server side auto topic creation, we should have client
side auto topic creation for the producer:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-487%3A+Client-side+Automatic+Topic+Creation+on+Producer
Ismael
On Mon, May 11, 2020 at 1:41 PM Colin McCabe wrote:
> On Mo
Hi Badai,
I think this is a good change. Can you please address the issues raised
by KIP-235? That was the reason why we did not do it previously.
Ismael
On Mon, Apr 27, 2020 at 5:46 PM Badai Aqrandista wrote:
> Hi everyone
>
> I have opened this KIP to have client.dns.lookup default value cha
Thanks for the KIP. A couple of questions:
1. Is it intended for this method to return null or the broker metrics
instance?
2. Is the Metrics class returned in any public APIs today or this the first
time we are doing it?
Ismael
On Wed, May 6, 2020 at 8:10 AM Rajini Sivaram
wrote:
> Hi Jeff,
>
Hi all,
I would like to share a few recent changes that should make the development
experience a little better:
1. Warning free builds for Scala. We have had this when it comes to Java
code for some time and with Scala 2.13.2's support for warning suppression,
we can finally have it for Scala too
[
https://issues.apache.org/jira/browse/KAFKA-9731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9731.
Resolution: Fixed
> Increased fetch request rate with leader selector due to HW propagat
[
https://issues.apache.org/jira/browse/KAFKA-9932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9932.
Resolution: Fixed
> First LeaderAndIsrRequest can take long due to unnecessary ZK r
[
https://issues.apache.org/jira/browse/KAFKA-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9652.
Fix Version/s: 2.6.0
Resolution: Fixed
> Throttle time metric needs to be updated for
Ismael Juma created KAFKA-9932:
--
Summary: First LeaderAndIsrRequest can take long due to
unnecessary ZK read
Key: KAFKA-9932
URL: https://issues.apache.org/jira/browse/KAFKA-9932
Project: Kafka
Yes, a PR would be great.
Ismael
On Mon, Apr 27, 2020, 2:10 AM Nikolay Izhikov wrote:
> Hello, Ismael.
>
> AFAIK we don’t run tests with the TLSv1.3, by default.
> Are you suggesting to do it?
> I can create a PR for it.
>
> > 24 апр. 2020 г., в 17:34, Ismael Juma н
; Do we have resources to run system tests periodically?
>
> When I did the testing I used servers my employer gave me.
>
> > 24 апр. 2020 г., в 08:05, Ismael Juma написал(а):
> >
> > Hi Nikolay,
> >
> > Seems like we have been able to run the system tests with
Hi Nikolay,
Seems like we have been able to run the system tests with TLS 1.3. Do we
run them nightly?
Ismael
On Fri, Feb 14, 2020 at 4:17 AM Nikolay Izhikov wrote:
> Hello, Kafka team.
>
> I ran system tests that use SSL for the TLSv1.3.
> You can find the results of the tests in the Jira tic
[
https://issues.apache.org/jira/browse/KAFKA-9907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9907.
Resolution: Fixed
> Switch default build to Scala 2
Ismael Juma created KAFKA-9907:
--
Summary: Switch default build to Scala 2.13
Key: KAFKA-9907
URL: https://issues.apache.org/jira/browse/KAFKA-9907
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-9894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9894.
Resolution: Fixed
Fixed via [https://github.com/apache/kafka/pull/8519.
|https://github.com
Ismael Juma created KAFKA-9894:
--
Summary: Support Java 14
Key: KAFKA-9894
URL: https://issues.apache.org/jira/browse/KAFKA-9894
Project: Kafka
Issue Type: Improvement
Reporter
Hi all,
There have been 3 releases since Java 11, so we are halfway to the next
long-term support release (Java 17). It's a good time for Apache Kafka to
start testing with post Java 11 JDKs.
In order to do that, we need to upgrade to Gradle 6.3 which requires some
changes to how we run build com
[
https://issues.apache.org/jira/browse/KAFKA-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9309.
Resolution: Fixed
> Add the ability to translate Message classes to and from J
Hi Colin,
The read/modify/write is protected by the zk version, right?
Ismael
On Fri, Apr 17, 2020 at 12:53 PM Colin McCabe wrote:
> On Thu, Apr 16, 2020, at 08:51, Ismael Juma wrote:
> > I don't think these requests are necessarily infrequent under multi
> tenant
> &
c configurations, and changing quotas.
>
> best,
> Colin
>
>
> On Wed, Apr 15, 2020, at 15:25, Ismael Juma wrote:
> > Hi Boyang,
> >
> > Thanks for the KIP. Have we considered that this reduces availability for
> > these operations since we have a single Co
Hi Boyang,
Thanks for the KIP. Have we considered that this reduces availability for
these operations since we have a single Controller instead of the ZK quorum?
Ismael
On Fri, Apr 3, 2020 at 4:45 PM Boyang Chen
wrote:
> Hey all,
>
> I would like to start off the discussion for KIP-590, a foll
[
https://issues.apache.org/jira/browse/KAFKA-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9820.
Resolution: Fixed
> validateMessagesAndAssignOffsetsCompressed allocates batch iterator which
The internal config was meant to be internal, right? That is, no
compatibility guarantees are offered? The current discussion implies we are
considering it a public config.
Ismael
On Sat, Apr 4, 2020 at 9:31 AM Boyang Chen wrote:
> For Gary's case, I think the internal config should be a sort o
I commented in the discussion thread. I think the rejected alternative of
validating during topic creation seems better.
On Tue, Mar 31, 2020 at 6:17 AM Paolo Moriello
wrote:
> Hello,
>
> Thanks to everybody who has given feedback. I've incorporated the
> suggestions and think that this is now r
Hi Paolo,
Thanks for the KIP. Why would one want to set min.isr to be higher than
replication factor even in that case? Mickael's suggestion seems better to
me.
Ismael
On Fri, Mar 13, 2020 at 10:28 AM Paolo Moriello
wrote:
> Hi Mickael,
>
> Thanks for your interest in this. The main motivation
I'm a bit puzzled. We added this feature because we thought it was useful.
And now we are saying that you don't know if you can rely on it since the
downgrade happens silently. Can you provide more context on the OffsetFetch
downgrade? What is the implication of that?
Ismael
On Fri, Mar 27, 2020
501 - 600 of 5488 matches
Mail list logo
