You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Gian Merlino (JIRA)" <ji...@apache.org> on 2015/01/15 23:32:34 UTC

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

Gian Merlino created KAFKA-1866:
-----------------------------------

             Summary: LogStartOffset gauge throws exceptions after log.delete()
                 Key: KAFKA-1866
                 URL: https://issues.apache.org/jira/browse/KAFKA-1866
             Project: Kafka
          Issue Type: Bug
            Reporter: Gian Merlino


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)