[
https://issues.apache.org/jira/browse/KAFKA-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972139#comment-13972139
]
Jay Kreps commented on KAFKA-1359:
----------------------------------
My motivation was that I was under the impression that nanoTime was faster and
more appropriate for timing things which is essentially what we are doing. Both
the rate and window boundary cases are about ellapsed time, right? That said, I
had no idea that linux gave such an odd result.
> Add topic/broker metrics once new topic/broker is discovered
> ------------------------------------------------------------
>
> Key: KAFKA-1359
> URL: https://issues.apache.org/jira/browse/KAFKA-1359
> Project: Kafka
> Issue Type: Sub-task
> Components: producer
> Reporter: Guozhang Wang
> Assignee: Guozhang Wang
> Fix For: 0.8.2
>
> Attachments: KAFKA-1359.patch, KAFKA-1359_2014-04-10_10:11:40.patch,
> KAFKA-1359_2014-04-11_14:20:45.patch, KAFKA-1359_2014-04-16_09:53:55.patch
>
>
> Today some topic/broker level metrics are only added the first time such an
> event (record-retry, record-error, etc) happens. This has a potential issue
> for customized mbean reporter which needs to register all the sensors at the
> time the new broker/topic is discovered. It is better to add such metrics at
> the very beginning when new topic/brokers are discovered.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
