You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremiah Jordan (JIRA)" <ji...@apache.org> on 2015/05/11 23:21:00 UTC
[jira] [Comment Edited] (CASSANDRA-9029) Add utility class to
support for rate limiting a given log statement
[ https://issues.apache.org/jira/browse/CASSANDRA-9029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538666#comment-14538666 ]
Jeremiah Jordan edited comment on CASSANDRA-9029 at 5/11/15 9:20 PM:
---------------------------------------------------------------------
Can we change the description in CHANGES.txt?
bq. "Add support for rate limiting log messages (CASSANDRA-9029)"
This sounds like we added some option that users can put in their logback.xml. Which is what got me looking at this, and that is not at all what this is.
was (Author: jjordan):
Can we change the description in CHANGES.txt?
bq. "Add support for rate limiting log messages (CASSANDRA-9029)"
This sounds like we added some option that users can put in their logbook.xml. Which is what got me looking at this, and that is not at all what this is.
> Add utility class to support for rate limiting a given log statement
> --------------------------------------------------------------------
>
> Key: CASSANDRA-9029
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9029
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Fix For: 2.2 beta 1, 2.1.6
>
>
> Add a utility class that can be used in the code to rate limit a given log statement. This can be used when the log statement is coming from a performance sensitive place or someplace hit often, and you don't want it to spam the logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)