[jira] [Created] (KAFKA-13133) Replace EasyMock and PowerMock with Mockito for AbstractHerderTest

[YI-CHEN WANG (Jira)]

YI-CHEN WANG created KAFKA-13133:


 Summary: Replace EasyMock and PowerMock with Mockito for 
AbstractHerderTest
 Key: KAFKA-13133
 URL: https://issues.apache.org/jira/browse/KAFKA-13133
 Project: Kafka
  Issue Type: Sub-task
Reporter: YI-CHEN WANG
Assignee: YI-CHEN WANG






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (KAFKA-13134) Heartbeat Request high lock contention

[David Mao (Jira)]

David Mao created KAFKA-13134:
-

 Summary: Heartbeat Request high lock contention
 Key: KAFKA-13134
 URL: https://issues.apache.org/jira/browse/KAFKA-13134
 Project: Kafka
  Issue Type: Improvement
  Components: core
Reporter: David Mao
Assignee: David Mao


On a cluster with high heartbeat rate, a lock profile showed high contention 
for the GroupMetadata lock.

We can significantly reduce this by invoking the response callback outside of 
the group metadata lock.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[GitHub] [kafka-site] omkreddy merged pull request #363: MINOR: Publish web site via .asf.yaml

[GitBox]

omkreddy merged pull request #363:
URL: https://github.com/apache/kafka-site/pull/363


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #363

[Apache Jenkins Server]

See 

[jira] [Created] (KAFKA-13135) Reduce GroupMetadata lock contention for offset commit requests

[David Mao (Jira)]

David Mao created KAFKA-13135:
-

 Summary: Reduce GroupMetadata lock contention for offset commit 
requests
 Key: KAFKA-13135
 URL: https://issues.apache.org/jira/browse/KAFKA-13135
 Project: Kafka
  Issue Type: Improvement
Reporter: David Mao


as suggested by [~lbradstreet], we can look for similar optimizations to 
https://issues.apache.org/jira/browse/KAFKA-13134 in the offset commit path.

It looks like there are some straightforward optimizations possible for the 
error path.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] Apache Kafka 3.0.0 release plan with new updated dates

[Justine Olshan]

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 in 3.0, in some upgrade scenarios, topic IDs for
existing topics will not be assigned to the logs. For topics affected with
the issue, we will not be able to check the topic ID. We could potentially
handle partitions with inconsistent topic IDs incorrectly.

I believe this should be considered a blocker for 3.0. JIRA is here
 and PR to fix the issue
here .

Thanks,
Justine

On Fri, Jul 23, 2021 at 10:51 AM Konstantine Karantasis <
kkaranta...@apache.org> wrote:

> 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 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 PR,
> > it's technically touching on a few things that aren't just docs, but only
> > to add a handful of checks
> > that already existed on the old APIs and just got missed on the new APIs.
> > Anything beyond that
> > I left as a TODO to follow up on after 3.0.
> >
> > KAFKA-13021  ---
> > https://github.com/apache/kafka/pull/4
> >
> > I think we should be able to get it merged by tomorrow. Assuming we do,
> can
> > I promote it back
> > to blocker status and pick the fix to the 3.0 branch?
> >
> > Thanks!
> > Sophie
> >
> > On Thu, Jul 22, 2021 at 4:29 PM Konstantine Karantasis
> >  wrote:
> >
> > > 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 expected.
> > > So, I agree with you that this is not an RC generation blocker per se
> but
> > > it's a release blocker overall.
> > >
> > > Konstantine
> > >
> > >
> > > On Thu, Jul 22, 2021 at 4:21 PM John Roesler 
> > wrote:
> > >
> > > > 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 3.0.
> > > >
> > > > I'm sorry for the oversight. For what it's worth, I think we
> > > > could proceed with a release candidate while we continue to
> > > > address the missing system test.
> > > >
> > > > Thanks,
> > > > -John
> > > >
> > > > https://issues.apache.org/jira/browse/KAFKA-12724
> > > >
> > > > On Wed, 2021-07-21 at 14:00 -0700, Konstantine Karantasis
> > > > wrote:
> > > > > 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
> > sense
> > > to
> > > > > me.
> > > > >
> > > > > Konstantine
> > > > >
> > > > >
> > > > > On Wed, Jul 21, 2021 at 11:46 AM Colin McCabe 
> > > > wrote:
> > > > >
> > > > > > 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: Flaky Test
> > > > > > RaftEventSimulationTest.canMakeProgressIfMajorityIsReachable
> > > > > >
> > > > > > There are two subtasks for #1 which we are working on. We suspect
> > > that
> > > > #3
> > > > > > has been fixed by a previous fix we made... we're looking into
> it.
> > > > > >
> > > > > > best,
> > > > > > Colin
> > > > > >
> > > > > > On Mon, Jul 19, 2021, at 20:23, Konstantine Karantasis wrote:
> > > > > > > Hi all,
> > > > > > >
> > > > > > > Since last week, we have reached the stage of Code Freeze for
> the
> > > > 3.0.0
> > > > > > > Apache Kaf