Thanks for the brief discussion Matthias and Israel.
Since there's no option but to merge a change, at this late stage in the
release process I'd agree with Matthias's suggestion to move forward with a
partial reversion of changes, which seems to be the safest of the two
options. I'll port the
Hi Konstantine. A potential 3.0 blocker was discovered today,
https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13219. The
BrokerState metric is not working for KRaft clusters -- it always indicates
that the broker is in the "not running" state. A PR is available at
Given the discussed upgrade path from the current join semantics to the
improved join semantics, I think it's best to partly revert KIP-633 for
3.0 release.
I prepared a PR for it: https://github.com/apache/kafka/pull/11233
The idea is to stay on `JoinWindows.of().grace()` and not add
Konstantine,
After a brief chat with Sophie, I just updated the name for KIP-633 to be
more descriptive of what is actually happening in the implementation
It is changed on the KIP page and the JIRA task title is also updated to be
more descriptive
https://cwiki.apache.org/confluence/x/Ho2NCg
Hi Matthias, it is possible to still deprecate JoinWindows.of(size) even
though the new join semantics is disabled.
I just pre-recorded a talk for Kafka Summit Americas where I am
recommending a switch to the new APIs instead of the deprecated one
starting from 3.0
I would love to be involved in
Hi,
we discovered a potential blocker for 3.0.0 today:
https://issues.apache.org/jira/browse/KAFKA-13216
We are still evaluating a potential fix. If we cannot fix it quickly,
the fall-back would be to partially roll-back KIP-633, to disable the
new join semantics such that people cannot hit this
Hi Rajini.
Approved, given its low risk and the lack of convenient workarounds.
Konstantine
On Tue, Aug 17, 2021 at 11:00 AM Rajini Sivaram
wrote:
> Hi Konstantine,
>
> We found an issue with replication with IBP 2.7:
> https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small and
Hi Konstantine,
We found an issue with replication with IBP 2.7:
https://issues.apache.org/jira/browse/KAFKA-13207. The fix is small and low
risk and has been merged to trunk. Can we include this in 3.0 branch since
it can result in IllegalStateException during replication?
Thank you,
Rajini
Jose, thanks for the heads up on the 3 new blocker candidates.
I read the tickets and they have clear descriptions and implementation
details.
However, at this stage to be able to make a call and approve new blockers
I'd appreciate it if we could get some insight regarding the risk and the
Thanks for reporting this new issue Ryan,
It's important and this issue seems to have clearly regressed dynamic
default configs in the 3.0 branch.
So, it's approved.
Konstantine
On Wed, Aug 4, 2021 at 4:34 PM José Armando García Sancio
wrote:
> Hey all,
>
> For the KIP-500 work for 3.0 we
Hey all,
For the KIP-500 work for 3.0 we would like to propose the following
Jiras as blockers:
1. https://issues.apache.org/jira/browse/KAFKA-13168
2. https://issues.apache.org/jira/browse/KAFKA-13165
3. https://issues.apache.org/jira/browse/KAFKA-13161
The description for each Jira should
Hi Konstantine,
I would like to report another bug in KRaft.
The ConfigHandler that processes dynamic broker config deltas in KRaft
expects that the default resource name for dynamic broker configs is the
old default entity name used in ZK: "". Since dynamic default
broker configs are persisted
Thanks Ryan,
Approved. Seems also like a low risk fix.
With that opportunity, let's make sure there are no other configs that
would need a similar validation.
Konstantine
On Fri, Jul 30, 2021 at 8:33 AM Ryan Dielhenn
wrote:
> Hey Konstantine,
>
> Thanks for the question. If these configs are
Hey Konstantine,
Thanks for the question. If these configs are not validated the user's
experience will be affected and upgrades from 3.0 will be harder.
Best,
Ryan Dielhenn
On Thu, Jul 29, 2021 at 3:59 PM Konstantine Karantasis <
kkaranta...@apache.org> wrote:
> Thanks for reporting this
Thanks for reporting this issue Ryan.
I believe what you mention corresponds to the ticket you created here:
https://issues.apache.org/jira/projects/KAFKA/issues/KAFKA-13151
What happens if the configurations are present but the broker doesn't fail
at startup when configured to run in KRaft
Hi,
Disregard log.clean.policy being included in this blocker.
Best,
Ryan Dielhenn
On Thu, Jul 29, 2021 at 2:38 PM Ryan Dielhenn
wrote:
> Hey Konstantine,
>
> I'd like to report another bug in KRaft.
>
> log.cleanup.policy, alter.config.policy.class.name, and
> create.topic.policy.class.name
Hey Konstantine,
I'd like to report another bug in KRaft.
log.cleanup.policy, alter.config.policy.class.name, and
create.topic.policy.class.name are all unsupported by KRaft but KRaft
servers allow them to be configured. I believe this should be considered a
blocker and that KRaft servers should
Thanks Ryan and Ron for reporting these new issues.
KAFKA-13142 is approved as an issue with no good workaround (and keeping in
mind that we have a few open blockers still) and
KAFKA-13137 is approved as a blocker because it's a regression.
Konstantine
On Tue, Jul 27, 2021 at 5:22 PM Ron
Hi Konstantine. I've opened KAFKA-13137 as a potential blocker. An
approved PR is available at
https://github.com/apache/kafka/pull/11131. The kafka.controller
metrics that the KRaft controllers expose have the wrong MBean names.
Ron
> On Jul 27, 2021, at 8:13 PM, Ryan Dielhenn
> wrote:
>
>
Hello,
I would like to report a bug in KRaft.
Dynamic broker configs are not being validated on the brokers before being
forwarded to the controller and persisted in the metadata quorum. This is a
blocker because a core requirement of KRaft mode in 3.0 is that it should
support upgrades from
Hi all,
I'd like to report a bug for Connect this time.
System test runs revealed an issue when restarting a connector but not the
tasks.
You may find a description in:
https://issues.apache.org/jira/browse/KAFKA-13139
The underlying issue is related to the implementation of KIP-745.
This makes
Hi Justine,
Thanks for reporting this issue. Sounds like a regression in 3.0.
Therefore, it would make sense to try to address it before we release
3.0.0.
I marked the jira issue as a Blocker targeting 3.0. Hopefully your PR will
fix the issue but let me know if we need to make further
Hi Konstantine,
I've discovered a bug with topic IDs that can be encountered when upgrading
from IBP versions below 2.8.
Since 2.8, when handling leader and isr requests, the request topic IDs are
compared to the log IDs and partitions with inconsistent IDs are skipped.
With a change introduced
Thanks for the PR and the follow up Sophie.
We can still get this in and there's no risk to do so, given the proposed
changes.
Therefore, I agree to cherry-pick to 3.0 since the PR is about to get
merged.
Konstantine
On Thu, Jul 22, 2021 at 9:12 PM Sophie Blee-Goldman
wrote:
> Hey
Hey Konstantine,
A javadocs ticket of ours was demoted to a non-blocker earlier this week
due to lack of action,
but I now have a PR ready and under review. It's picking up some essential
followup that was
missed during the implementation of KIP-633 and is pretty essential. I
tagged you on the
Thanks for raising this John.
While we are working to eliminate the existing blockers I think it would be
great to use this time in order to test the upgrade path that you mention.
Before we approve a release candidate (once such a RC is generated) we
should confirm that the upgrade works as
Hello Konstantine,
Someone just called to my attention that KAFKA-12724 had not
been marked as a 3.0 blocker. We never added 2.8 to the
Streams upgrade system test suite. This isn't a blocker in
that it is a problem, but we should make sure that Streams
is actually upgradable before releasing
Thanks for the heads up Colin.
KAFKA-13112 seems important and of course relevant to what we ship with
3.0.
Same for the test failures captured by KAFKA-13095 and KAFKA-12851. Fixing
those will increase the stability of our builds.
Therefore, considering these tickets as blockers currently makes
Hi Konstantine,
Thanks for your work on this release! We discovered three blocker bugs which
are worth bringing up here:
1. KAFKA-13112: Controller's committed offset get out of sync with raft client
listener context
2. KAFKA-13095: TransactionsTest is failing in kraft mode
3. KAFKA-12851:
Hi all,
Since last week, we have reached the stage of Code Freeze for the 3.0.0
Apache Kafka release.
>From this point forward and until the official release of 3.0.0, only
critical fixes for blocker issues should be merged to the 3.0 release
branch.
The release plan currently includes ten (10)
Hi all,
This is a reminder that Code Freeze for Apache Kafka 3.0 is coming up this
week and is set to take place by the end of day Wednesday, July 14th.
Currently in the project we have 22 blocker issues for 3.0, out of 41 total
tickets targeting 3.0.
You may find the list of open issues in the
Thanks for the update Levani,
KIP-708 is now on the list of postponed KIPs.
Konstantine
On Thu, Jul 1, 2021 at 10:48 PM Levani Kokhreidze
wrote:
> Hi Konstantine,
>
> FYI, I don’t think we will be able to have KIP-708 ready on time.
> Feel free to remove it from the release plan.
>
> Best,
>
Hi Konstantine,
FYI, I don’t think we will be able to have KIP-708 ready on time.
Feel free to remove it from the release plan.
Best,
Levani
> On 1. Jul 2021, at 01:27, Konstantine Karantasis
> wrote:
>
> Hi all,
>
> Today we have reached the Feature Freeze milestone for Apache Kafka 3.0.
>
Hi all,
Today we have reached the Feature Freeze milestone for Apache Kafka 3.0.
Exciting!
I'm going to allow for any pending changes to settle within the next couple
of days.
I trust that we all approve and merge adopted features and changes which we
consider to be in good shape for 3.0.
Given
Done. Thanks Luke!
On Tue, Jun 29, 2021 at 6:39 PM Luke Chen wrote:
> Hi Konstantine,
> We've decided that the KIP-726 will be released in V3.1, not V3.0.
> KIP-726: Make the "cooperative-sticky, range" as the default assignor
>
> Could you please remove this KIP from the 3.0 release plan wiki
Hi Konstantine,
We've decided that the KIP-726 will be released in V3.1, not V3.0.
KIP-726: Make the "cooperative-sticky, range" as the default assignor
Could you please remove this KIP from the 3.0 release plan wiki page?
Thank you.
Luke
On Wed, Jun 30, 2021 at 8:23 AM Konstantine Karantasis
Thanks for the update Colin.
They are now both in the release plan.
Best,
Konstantine
On Tue, Jun 29, 2021 at 2:55 PM Colin McCabe wrote:
> Hi Konstantine,
>
> Can you please add two KIPs to the 3.0 release plan wiki page?
>
> I'm thinking of:
> KIP-630: Kafka Raft Snapshots
> KIP-746:
Hi Konstantine,
Can you please add two KIPs to the 3.0 release plan wiki page?
I'm thinking of:
KIP-630: Kafka Raft Snapshots
KIP-746: Revise KRaft Metadata Records
These are marked as 3.0 on the KIP page but I guess we don't have them on the
page yet.
Many thanks.
Colin
On Tue, Jun
Hi there,
As the feature freeze date is approaching, I just wanted to kindly ask for
some reviews on the already submitted PR (
https://github.com/apache/kafka/pull/10840) that implements the approved
KIP-744 (https://cwiki.apache.org/confluence/x/XIrOCg). The PR has been
ready for review for 2
Thanks for the update Bruno.
I've moved KIP-698 to the list of postponed KIPs in the plan.
Konstantine
On Mon, Jun 21, 2021 at 2:30 AM Bruno Cadonna wrote:
> Hi Konstantine,
>
> The implementation of
>
> KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
> Streams
>
> will
Hi Konstantine,
The implementation of
KIP-698: Add Explicit User Initialization of Broker-side State to Kafka
Streams
will not be ready for 3.0, so you can remove it from the list.
Best,
Bruno
On 15.06.21 07:33, Konstantine Karantasis wrote:
Done. Moved it into the table of Adopted KIPs
Done. Moved it into the table of Adopted KIPs targeting 3.0.0 and to the
release plan of course.
Thanks for catching this Israel.
Best,
Konstantine
On Mon, Jun 14, 2021 at 7:40 PM Israel Ekpo wrote:
> Konstantine,
>
> One of mine is missing from this list
>
> KIP-633: Drop 24 hour default of
Konstantine,
One of mine is missing from this list
KIP-633: Drop 24 hour default of grace period in Streams
Please could you include it?
Voting has already concluded a long time ago
On Mon, Jun 14, 2021 at 6:08 PM Konstantine Karantasis
wrote:
> Hi all.
>
> KIP Freeze for the next major
Hi all.
KIP Freeze for the next major release of Apache Kafka was reached last
week.
As of now, 36 KIPs have concluded their voting process and have been
adopted.
These KIPs are targeting 3.0 (unless it's noted otherwise in the release
plan) and their inclusion as new features will be finalized
Hi all,
Just a quick reminder that KIP Freeze is next Wednesday, June 9th.
A vote thread needs to be open for at least 72 hours, so to everyone that
is working hard on proposals targeting 3.0.0, please make sure that your
[VOTE] threads are started on time.
Best,
Konstantine
On Wed, May 26,
+1 on the new schedule.
On Wed, May 26, 2021 at 8:14 PM Sophie Blee-Goldman
wrote:
> Ah ok, thanks Konstantine. I won't bug you about every new KIP that comes
> in between now and KIP Freeze :P
>
> +1 on the scheduling changes as well
>
> On Wed, May 26, 2021 at 4:00 PM David Arthur wrote:
>
>
Ah ok, thanks Konstantine. I won't bug you about every new KIP that comes
in between now and KIP Freeze :P
+1 on the scheduling changes as well
On Wed, May 26, 2021 at 4:00 PM David Arthur wrote:
> The new schedule looks good to me, +1
>
> On Wed, May 26, 2021 at 6:29 PM Ismael Juma wrote:
>
The new schedule looks good to me, +1
On Wed, May 26, 2021 at 6:29 PM Ismael Juma wrote:
> Thanks Konstantine, +1 from me.
>
> Ismael
>
> On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
> wrote:
>
> > Hi all,
> >
> > Please find below the updated release plan for the Apache Kafka 3.0.0
anyone instruct me how to unsubscribe from this mail list, please!!
> dev-unsubscr...@kafka.apache.org doesn’t work.
>
>
> From: Ismael Juma
> Sent: Wednesday, May 26, 2021 5:29:03 PM
> To: dev
> Subject: EXTERNAL: Re: [DISCUSS] Apache Kafka
Can anyone instruct me how to unsubscribe from this mail list, please!!
dev-unsubscr...@kafka.apache.org doesn’t work.
From: Ismael Juma
Sent: Wednesday, May 26, 2021 5:29:03 PM
To: dev
Subject: EXTERNAL: Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new
Thanks Konstantine, +1 from me.
Ismael
On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis
wrote:
> Hi all,
>
> Please find below the updated release plan for the Apache Kafka 3.0.0
> release.
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466
>
> New suggested
Thanks Sophie.
I'm also tracking the updates on the main KIP page and the Adopted KIPs
table periodically, moving newly adopted KIPs to the release plan.
But we'll definitely use the mailing list more as we approach KIP Freeze
and make sure we include everything that is ready by the time we hit
Hey Konstantine, I did a quick skim over the Streams KIPs and found two
more which had not
been moved to the "Adopted" section on the main KIP page and are missing
from the release
notes. These are:
- KIP-466: Add support for List serialization and deserialization
53 matches
Mail list logo
