You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Dave DeMaagd (Created) (JIRA)" <ji...@apache.org> on 2012/03/21 17:51:40 UTC
[jira] [Created] (KAFKA-312) Add 'reset' operation for
AsyncProducerDroppedEvents
Add 'reset' operation for AsyncProducerDroppedEvents
----------------------------------------------------
Key: KAFKA-312
URL: https://issues.apache.org/jira/browse/KAFKA-312
Project: Kafka
Issue Type: Improvement
Reporter: Dave DeMaagd
Priority: Minor
Currently no functionality exists to reset AsyncProducerDroppedEvents data, which can create problems with monitoring/alerting based off of this value (depending on what system you are using and how it has been implemented). Diff attached.
Impacted files:
core/src/main/scala/kafka/producer/async/AsyncProducerStats.scala
core/src/main/scala/kafka/producer/async/AsyncProducerStatsMBean.scala
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (KAFKA-312) Add 'reset' operation for
AsyncProducerDroppedEvents
Posted by "Neha Narkhede (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234489#comment-13234489 ]
Neha Narkhede commented on KAFKA-312:
-------------------------------------
+1. This is useful
> Add 'reset' operation for AsyncProducerDroppedEvents
> ----------------------------------------------------
>
> Key: KAFKA-312
> URL: https://issues.apache.org/jira/browse/KAFKA-312
> Project: Kafka
> Issue Type: Improvement
> Reporter: Dave DeMaagd
> Priority: Minor
> Labels: patch
> Attachments: KAFKA-312-2012032100.diff
>
>
> Currently no functionality exists to reset AsyncProducerDroppedEvents data, which can create problems with monitoring/alerting based off of this value (depending on what system you are using and how it has been implemented). Diff attached.
> Impacted files:
> core/src/main/scala/kafka/producer/async/AsyncProducerStats.scala
> core/src/main/scala/kafka/producer/async/AsyncProducerStatsMBean.scala
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-312) Add 'reset' operation for
AsyncProducerDroppedEvents
Posted by "Dave DeMaagd (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave DeMaagd updated KAFKA-312:
-------------------------------
Attachment: KAFKA-312-2012032100.diff
> Add 'reset' operation for AsyncProducerDroppedEvents
> ----------------------------------------------------
>
> Key: KAFKA-312
> URL: https://issues.apache.org/jira/browse/KAFKA-312
> Project: Kafka
> Issue Type: Improvement
> Reporter: Dave DeMaagd
> Priority: Minor
> Labels: patch
> Attachments: KAFKA-312-2012032100.diff
>
>
> Currently no functionality exists to reset AsyncProducerDroppedEvents data, which can create problems with monitoring/alerting based off of this value (depending on what system you are using and how it has been implemented). Diff attached.
> Impacted files:
> core/src/main/scala/kafka/producer/async/AsyncProducerStats.scala
> core/src/main/scala/kafka/producer/async/AsyncProducerStatsMBean.scala
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira