Hi Ismael, On Wed, Feb 26, 2025 at 7:51 AM Ismael Juma <m...@ismaeljuma.com> wrote: > > Hi Jose, > > Is it a low risk change? If not, I would suggest giving it a bit of > stabilization time before cherry-picking to older branches including 4.0 > and 3.9. I don't think it's necessary to backport to other older branches > given that it's not a regression and I don't believe there are any cases of > users running into it.
We do have users that have encountered this issue in KRaft. I documented two cases in the Jira. Since this is not a regression, I am okay not including this in the 4.0.0 release. We should include it in the 4.0.1 release. I updated the Jira so that the fixed version is 4.0.1. Thanks, -- -José
