kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajini Sivaram (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-6164) ClientQuotaManager threads prevent shutdown when encountering an error loading logs
Date Thu, 09 Nov 2017 19:24:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajini Sivaram resolved KAFKA-6164.
-----------------------------------
    Resolution: Fixed

Issue resolved by pull request 4199
[https://github.com/apache/kafka/pull/4199]

> ClientQuotaManager threads prevent shutdown when encountering an error loading logs
> -----------------------------------------------------------------------------------
>
>                 Key: KAFKA-6164
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6164
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.11.0.0, 1.0.0
>            Reporter: Xavier Léauté
>            Assignee: Rajini Sivaram
>             Fix For: 1.1.0, 1.0.1
>
>
> While diagnosing KAFKA-6163, we noticed that when the broker initiates a shutdown sequence
in response to an error loading the logs, the process never exits. The JVM appears to be waiting
indefinitely for several non-deamon threads to terminate.
> The threads in question are {{ThrottledRequestReaper-Request}}, {{ThrottledRequestReaper-Produce}},
and {{ThrottledRequestReaper-Fetch}}, so it appears we don't properly shutdown {{ClientQuotaManager}}
in this situation.
> QuotaManager shutdown is currently handled by KafkaApis, however KafkaApis will never
be instantiated in the first place if we encounter an error loading the logs, so quotamangers
are left dangling in that case.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message