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

Jason Gustafson updated KAFKA-5624:
-----------------------------------
    Description: 
Seems a couple unhandled cases following sensor expiration:

1. Static sensors (such as {{ClientQuotaManager.delayQueueSensor}}) can be 
expired due to inactivity, but the references will remain valid and usable. 
Probably a good idea to either ensure we use a "get or create" pattern when 
accessing the sensor or add a new static registration option which makes the 
sensor ineligible for expiration.
2. It is possible to register metrics through the sensor even after it is 
expired. We should probably raise an exception instead.

  was:
Seems a couple unhandled cases following sensor expiration:

1. Static sensors (such as {{ClientQuotaManager.}}) can be expired due to 
inactivity, but the references will remain valid and usable. Probably a good 
idea to either ensure we use a "get or create" pattern when accessing the 
sensor or add a new static registration option which makes the sensor 
ineligible for expiration.
2. It is possible to register metrics through the sensor even after it is 
expired. We should probably raise an exception instead.


> Unsafe use of expired sensors
> -----------------------------
>
>                 Key: KAFKA-5624
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5624
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>
> Seems a couple unhandled cases following sensor expiration:
> 1. Static sensors (such as {{ClientQuotaManager.delayQueueSensor}}) can be 
> expired due to inactivity, but the references will remain valid and usable. 
> Probably a good idea to either ensure we use a "get or create" pattern when 
> accessing the sensor or add a new static registration option which makes the 
> sensor ineligible for expiration.
> 2. It is possible to register metrics through the sensor even after it is 
> expired. We should probably raise an exception instead.



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

Reply via email to