[
https://issues.apache.org/jira/browse/KAFKA-16354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829950#comment-17829950
]
Greg Harris commented on KAFKA-16354:
-------------------------------------
Hi [~yangpoan] Thank you for looking into it more, it sounds like it's more
complicated than I thought.
Since it would require changes to the ZkMetadataCache which is due for removal
in 4.0, I don't think this is worth pursuing at this time. I'll close this as
wont-do.
> FinalizedFeatureChangeListenerTest should use mocked latches
> ------------------------------------------------------------
>
> Key: KAFKA-16354
> URL: https://issues.apache.org/jira/browse/KAFKA-16354
> Project: Kafka
> Issue Type: Test
> Components: core
> Affects Versions: 3.7.0
> Reporter: Greg Harris
> Priority: Trivial
> Labels: newbie
>
> testCacheUpdateWaitFailsForUnreachableVersion takes 30 seconds, and
> testInitFailureDueToFeatureIncompatibility takes 5 seconds. This appears to
> be caused by FeatureCacheUpdater#awaitUpdateOrThrow waiting for a real
> CountDownLatch with a real-time timeout.
> Instead, a mocked latch should be used to exit the await immediately.
> This should be done both for CPU-independence, and for test execution speed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
