[KAFKA-1866] LogStartOffset gauge throws exceptions after log.delete()

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.8.2.1
• Fix Version/s: 0.9.0.0
• Assignee: Harsha
• Reporter: Gian Merlino
• Created: 15/Jan/15 22:32
• Updated: 20/Apr/16 11:34
• Resolved: 28/Feb/15 00:11

Description

The LogStartOffset gauge does "logSegments.head.baseOffset", which throws NoSuchElementException on an empty list, which can occur after a delete() of the log. This makes life harder for custom MetricsReporters, since they have to deal with .value() possibly throwing an exception.

Locally we're dealing with this by having Log.delete() also call removeMetric on all the gauges. That also has the benefit of not having a bunch of metrics floating around for logs that the broker is not actually handling.

Issue Links

• duplicates: KAFKA-3572 Metrics of topics still exist when they have been deleted
• relates to: KAFKA-2233 Log deletion is not removing log metrics