[
https://issues.apache.org/jira/browse/KAFKA-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-3292:
---------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Issue resolved by pull request 977
[https://github.com/apache/kafka/pull/977]
> ClientQuotaManager.getOrCreateQuotaSensors() may return a null
> ClientSensors.throttleTimeSensor
> -----------------------------------------------------------------------------------------------
>
> Key: KAFKA-3292
> URL: https://issues.apache.org/jira/browse/KAFKA-3292
> Project: Kafka
> Issue Type: Bug
> Reporter: Jun Rao
> Assignee: Ismael Juma
> Fix For: 0.10.0.0
>
>
> It seems that the following situation is possible. Two threads try to call
> getOrCreateQuotaSensors() at the same time. Initially, quotaSensor is not
> registered, then both threads try to get the write lock to register
> quotaSensor. Thread 1 grabs the write lock and registers both quotaSensor and
> throttleTimeSensor, and then releases the lock. Thread 2 grabs the write lock
> again and reads a non-null quotaSensor. It then skips the logic to register
> throttleTimeSensor and returns. However, the returned throttleTimeSensor will
> be null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
