Hi Bill,
we encountered the following bug in our soak testing cluster.
https://issues.apache.org/jira/browse/KAFKA-10631
I classified the bug as a blocker because it caused the death of a
stream thread. It does not seem to be a regression, though.
I opened a PR to fix the bug here:
https://github.com/apache/kafka/pull/9479
Feel free to downgrade the priority to "Major" if you think it is not a
blocker.
Best,
Bruno
On 22.10.20 17:49, Bill Bejeck wrote:
Hi All,
We've hit code freeze. The current status for cutting an RC is there is
one blocker issue. It looks like there is a fix in the works, so
hopefully, it will get merged early next week.
At that point, if there are no other blockers, I proceed with the RC
process.
Thanks,
Bill
On Wed, Oct 7, 2020 at 12:10 PM Bill Bejeck <bbej...@gmail.com> wrote:
Hi Anna,
I've updated the table to only show KAFKA-10023 as going into 2.7
Thanks,
Bill
On Tue, Oct 6, 2020 at 6:51 PM Anna Povzner <a...@confluent.io> wrote:
Hi Bill,
Regarding KIP-612, only the first half of the KIP will get into 2.7
release: Broker-wide and per-listener connection rate limits, including
corresponding configs and metric (KAFKA-10023). I see that the table in
the
release plan tags KAFKA-10023 as "old", not sure what it refers to.
Note
that while KIP-612 was approved prior to 2.6 release, none of the
implementation went into 2.6 release.
The second half of the KIP that adds per-IP connection rate limiting
will
need to be postponed (KAFKA-10024) till the following release.
Thanks,
Anna
On Tue, Oct 6, 2020 at 2:30 PM Bill Bejeck <bbej...@gmail.com> wrote:
Hi Kowshik,
Given that the new feature is contained in the PR and the tooling is
follow-on work (minor work, but that's part of the submitted PR), I
think
this is fine.
Thanks,
BIll
On Tue, Oct 6, 2020 at 5:00 PM Kowshik Prakasam <
kpraka...@confluent.io
wrote:
Hey Bill,
For KIP-584 <https://issues.apache.org/jira/browse/KIP-584>, we are
in
the
process of reviewing/merging the write path PR into AK trunk:
https://github.com/apache/kafka/pull/9001 . As far as the KIP goes,
this
PR
is a major milestone. The PR merge will hopefully be done before EOD
tomorrow in time for the feature freeze. Beyond this PR, couple
things
are
left to be completed for this KIP: (1) tooling support and (2)
implementing
support for feature version deprecation in the broker . In
particular,
(1)
is important for this KIP and the code changes are external to the
broker
(since it is a separate tool we intend to build). As of now, we won't
be
able to merge the tooling changes before feature freeze date. Would
it be
ok to merge the tooling changes before code freeze on 10/22? The
tooling
requirements are explained here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-584
<https://issues.apache.org/jira/browse/KIP-584>
%3A+Versioning+scheme+for+features#KIP584:Versioningschemeforfeatures-Toolingsupport
I would love to hear thoughts from Boyang and Jun as well.
Thanks,
Kowshik
On Mon, Oct 5, 2020 at 3:29 PM Bill Bejeck <bbej...@gmail.com>
wrote:
Hi John,
I've updated the list of expected KIPs for 2.7.0 with KIP-478.
Thanks,
Bill
On Mon, Oct 5, 2020 at 11:26 AM John Roesler <vvcep...@apache.org>
wrote:
Hi Bill,
Sorry about this, but I've just noticed that KIP-478 is
missing from the list. The url is:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-478+-+Strongly+typed+Processor+API
The KIP was accepted a long time ago, and the implementation
has been trickling in since 2.6 branch cut. However, most of
the public API implementation is done now, so I think at
this point, we can call it "released in 2.7.0". I'll make
sure it's done by feature freeze.
Thanks,
-John
On Thu, 2020-10-01 at 13:49 -0400, Bill Bejeck wrote:
All,
With the KIP acceptance deadline passing yesterday, I've updated
the
planned KIP content section of the 2.7.0 release plan
<
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158872629
.
Removed proposed KIPs for 2.7.0 not getting approval
1. KIP-653
<
https://cwiki.apache.org/confluence/display/KAFKA/KIP-653%3A+Upgrade+log4j+to+log4j2
2. KIP-608
<
https://cwiki.apache.org/confluence/display/KAFKA/KIP-608+-+Expose+Kafka+Metrics+in+Authorizer
3. KIP-508
<
https://cwiki.apache.org/confluence/display/KAFKA/KIP-508%3A+Make+Suppression+State+Queriable
KIPs added
1. KIP-671
<
https://cwiki.apache.org/confluence/display/KAFKA/KIP-671%3A+Introduce+Kafka+Streams+Specific+Uncaught+Exception+Handler
Please let me know if I've missed anything.
Thanks,
Bill
On Thu, Sep 24, 2020 at 1:47 PM Bill Bejeck <bbej...@gmail.com>
wrote:
Hi All,
Just a reminder that the KIP freeze is next Wednesday,
September
30th.
Any KIP aiming to go in the 2.7.0 release needs to be
accepted by
this
date.
Thanks,
BIll
On Tue, Sep 22, 2020 at 12:11 PM Bill Bejeck <
bbej...@gmail.com>
wrote:
Boyan,
Done. Thanks for the heads up.
-Bill
On Mon, Sep 21, 2020 at 6:36 PM Boyang Chen <
reluctanthero...@gmail.com>
wrote:
Hey Bill,
unfortunately KIP-590 will not be in 2.7 release, could
you
move
it to
postponed KIPs?
Best,
Boyang
On Thu, Sep 10, 2020 at 2:41 PM Bill Bejeck <
bbej...@gmail.com
wrote:
Hi Gary,
It's been added.
Regards,
Bill
On Thu, Sep 10, 2020 at 4:14 PM Gary Russell <
gruss...@vmware.com>
wrote:
Can someone add a link to the release plan page [1] to
the
Future
Releases
page [2]?
I have the latter bookmarked.
Thanks.
[1]:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158872629
[2]:
https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan
________________________________
From: Bill Bejeck <bbej...@gmail.com>
Sent: Wednesday, September 9, 2020 4:35 PM
To: dev <dev@kafka.apache.org>
Subject: Re: [DISCUSS] Apache Kafka 2.7.0 release
Hi Dongjin,
I've moved both KIPs to the release plan.
Keep in mind the cutoff for KIP acceptance is
September
30th.
If the
KIP
discussions are completed, I'd recommend starting a
vote
for
them.
Regards,
Bill
On Wed, Sep 9, 2020 at 8:39 AM Dongjin Lee <
dong...@apache.org
wrote:
Hi Bill,
Could you add the following KIPs to the plan?
- KIP-508: Make Suppression State Queriable
<
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FKAFKA%2FKIP-508%253A%2BMake%2BSuppression%2BState%2BQueriable&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378806436&sdata=CkJill9%2FuBqp2HdVQrIjElj2z1nMgQXRaUyWrvY94dk%3D&reserved=0
- KIP-653: Upgrade log4j to log4j2
<
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FKAFKA%2FKIP-653%253A%2BUpgrade%2Blog4j%2Bto%2Blog4j2&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378806436&sdata=nHbw6WiQpkWT3KgPfanEtDCh3sWcL0O%2By8Fu0Bl4ivc%3D&reserved=0
Both KIPs are completely implemented with passing
all
tests,
but
not
got
reviewed by the committers. Could anyone have a
look?
Thanks,
Dongjin
On Wed, Sep 9, 2020 at 8:38 AM Leah Thomas <
ltho...@confluent.io>
wrote:
Hi Bill,
Could you also add KIP-450 to the release plan?
It's
been
merged.
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FKAFKA%2FKIP-450%253A%2BSliding%2BWindow%2BAggregations%2Bin%2Bthe%2BDSL&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378806436&sdata=1KbAPyL7NKWQSZWBKItUTpAJF5SY6%2FMCj8Rn%2Fw2qO20%3D&reserved=0
Cheers,
Leah
On Tue, Sep 8, 2020 at 9:32 AM Bill Bejeck <
bbej...@gmail.com>
wrote:
Hi Bruno,
Thanks for letting me know, I've added KIP-662
to
the
release
plan.
-Bill
On Mon, Sep 7, 2020 at 11:33 AM Bruno Cadonna <
br...@confluent.io>
wrote:
Hi Bill,
Could you add KIP-662 [1] to the release plan.
The
KIP
has
been
already
implemented.
Best,
Bruno
[1]
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fdisplay%2FKAFKA%2FKIP-662%253A%2BThrow%2BException%2Bwhen%2BSource%2BTopics%2Bof%2Ba%2BStreams%2BApp%2Bare%2BDeleted&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378806436&sdata=cxbyU9BJuJkM2JJ6yqfr5dHXrg7Mfr1%2BOKxCy%2FJQiCw%3D&reserved=0
On 26.08.20 16:54, Bill Bejeck wrote:
Greetings All!
I've published a release plan at
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwiki.apache.org%2Fconfluence%2Fpages%2Fviewpage.action%3FpageId%3D158872629&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378806436&sdata=iXp0nfkEK5gcuIJcIaZQthfnPR9cJ%2F8x2vBpQR942zA%3D&reserved=0
.
I have included all of the KIPs that are
currently
approved,
but
I'm
happy
to make any adjustments as necessary.
The KIP freeze is on September 30 with a
target
release
date of
November
6.
Let me know if there are any objections.
Thanks,
Bill Bejeck
On Fri, Aug 14, 2020 at 4:01 PM John
Roesler <
vvcep...@apache.org>
wrote:
Thanks, Bill!
-John
On Thu, 2020-08-13 at 15:19 -0700, Ismael
Juma
wrote:
Thanks for volunteering Bill. :)
Ismael
On Thu, Aug 13, 2020 at 3:13 PM Bill
Bejeck <
bbej...@apache.org>
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
--
*Dongjin Lee*
*A hitchhiker in the mathematical world.*
*github: <http://goog_969573159/>
github.com/dongjinleekr
<
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdongjinleekr&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378816433&sdata=6Y66FE5w9ZsUORcuiNsRJYZbRUI35N%2BnRV7nOwSxGtw%3D&reserved=0
keybase:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkeybase.io%2Fdongjinleekr&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378816433&sdata=UaZMCtaW86lfG4%2Bnm5pGJ0it9lDZohfRLMWRjfcyvnY%3D&reserved=0
<
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkeybase.io%2Fdongjinleekr&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378816433&sdata=UaZMCtaW86lfG4%2Bnm5pGJ0it9lDZohfRLMWRjfcyvnY%3D&reserved=0
linkedin:
kr.linkedin.com/in/dongjinleekr
<
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkr.linkedin.com%2Fin%2Fdongjinleekr&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378816433&sdata=r44oSW4w8Pgj9L%2FBHed2BsNGU4VS6TFT0aUNL0juSkA%3D&reserved=0
speakerdeck:
speakerdeck.com/dongjin
<
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fspeakerdeck.com%2Fdongjin&data=02%7C01%7Cgrussell%40vmware.com%7Cf9f4193557084c2f746508d854ffe7d2%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637352805378816433&sdata=tRBTpHkAGOK8Abn8OZsPLBGZZM5fr4yj6ZVOZZL72bI%3D&reserved=0
*
