You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@kafka.apache.org by Otis Gospodnetić <ot...@gmail.com> on 2015/09/12 03:46:35 UTC

Re: Kafka Server JMX Log End Offset Not updating after repartioning

Replying 3 months later.... Sounds like
http://search-hadoop.com/m/uyzND1YlKxr5XZpK , Joe.  No fix yes, as far as I
know.

Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/


On Mon, Jun 8, 2015 at 6:33 PM, joe smith <wa...@yahoo.com.invalid>
wrote:

> Hi,
> Have notice an issue.  We retrieve the
> "kafka.log":type="Log",name="<topic>-<partition>-LogEndOffset" 's
> Attribute: Value and used it to calculate the lag from consumer's offset.
> After we did a partition re-assignment, where partition leaders were
> changed, some of the new leader's  LogEndOffset were not updated and the
> value remain constant.
> Other utilities tools like the GetOffsetShell and ConsumerOffsetChecker
> were giving updated LogEndOffsets.  So it's just the JMX stopped updating.
>
> Can we confirm that this is an issue and Is there a fix?
>
> We are using the 0.8.1.1 and scala 2.10.1
> Thanks
>