[
https://issues.apache.org/jira/browse/KAFKA-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar Reddy resolved KAFKA-2233.
------------------------------------
Resolution: Duplicate
Fix Version/s: 0.8.3
This got fixed in KAFKA-1866
> Log deletion is not removing log metrics
> ----------------------------------------
>
> Key: KAFKA-2233
> URL: https://issues.apache.org/jira/browse/KAFKA-2233
> Project: Kafka
> Issue Type: Bug
> Components: log
> Affects Versions: 0.8.2.1
> Reporter: Stevo Slavic
> Assignee: Jay Kreps
> Priority: Minor
> Labels: newbie
> Fix For: 0.8.3
>
>
> Topic deletion does not remove associated metrics. Any configured kafka
> metric reporter that gets triggered after a topic is deleted, when polling
> for log metrics for such deleted logs it will throw something like:
> {noformat}
> java.util.NoSuchElementException
> at
> java.util.concurrent.ConcurrentSkipListMap$Iter.advance(ConcurrentSkipListMap.java:2299)
> at
> java.util.concurrent.ConcurrentSkipListMap$ValueIterator.next(ConcurrentSkipListMap.java:2326)
> at
> scala.collection.convert.Wrappers$JIteratorWrapper.next(Wrappers.scala:43)
> at scala.collection.IterableLike$class.head(IterableLike.scala:107)
> at scala.collection.AbstractIterable.head(Iterable.scala:54)
> at kafka.log.Log.logStartOffset(Log.scala:502)
> at kafka.log.Log$$anon$2.value(Log.scala:86)
> at kafka.log.Log$$anon$2.value(Log.scala:85)
> {noformat}
> since on log deletion, {{Log}} segments collection get cleared, so
> logSegments {{Iterable}} has no (next) elements.
> Known workaround is to restart broker - as metric registry is in memory, not
> persisted, on restart it will be recreated with metrics for
> existing/non-deleted topics only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
