You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ismael Juma (JIRA)" <ji...@apache.org> on 2016/12/05 12:44:59 UTC
[jira] [Updated] (KAFKA-2158) Close all fetchers in
AbstractFetcherManager without blocking
[ https://issues.apache.org/jira/browse/KAFKA-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismael Juma updated KAFKA-2158:
-------------------------------
Resolution: Duplicate
Status: Resolved (was: Patch Available)
Duplicate of KAFKA-4319.
> Close all fetchers in AbstractFetcherManager without blocking
> -------------------------------------------------------------
>
> Key: KAFKA-2158
> URL: https://issues.apache.org/jira/browse/KAFKA-2158
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Affects Versions: 0.8.2.0
> Reporter: Jiasheng Wang
> Attachments: KAFKA-2158.patch
>
>
> def closeAllFetchers() {
> mapLock synchronized {
> for ( (_, fetcher) <- fetcherThreadMap) {
> fetcher.shutdown()
> }
> fetcherThreadMap.clear()
> }
> }
> It is time consuming for closeAllFetchers() in AbstractFetcherManager.scala because each time a fetcher calls shutdown method it will block until awaitShutdown() returns. As a result it will slow down the restart of kafka service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)