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

["Stevo Slavic (JIRA)" <ji...@apache.org>]

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

Stevo Slavic updated KAFKA-1866:
--------------------------------
    Affects Version/s: 0.8.2.1

> LogStartOffset gauge throws exceptions after log.delete()
> ---------------------------------------------------------
>
>                 Key: KAFKA-1866
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1866
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.8.2.1
>            Reporter: Gian Merlino
>            Assignee: Sriharsha Chintalapani
>             Fix For: 0.8.3
>
>         Attachments: KAFKA-1866.patch, KAFKA-1866_2015-02-10_22:50:09.patch, KAFKA-1866_2015-02-11_09:25:33.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)