You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/01/03 16:56:13 UTC
[jira] [Resolved] (CASSANDRA-5100) Create different log entry if
dropped mutation is a hint
[ https://issues.apache.org/jira/browse/CASSANDRA-5100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-5100.
---------------------------------------
Resolution: Not A Problem
# There is no difference to the recipient to signify that a given Mutation is a hint, nor should there be
# The hint owner will not remove the hint until it is delivered, so there's nothing particularly serious about dropping a hint a second time, or a third. (If anything, the first time is the worst since it forces hint creation; after that, it can be dropped "for free" as far as the rest of the system is concerned.)
> Create different log entry if dropped mutation is a hint
> --------------------------------------------------------
>
> Key: CASSANDRA-5100
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5100
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.2.0
> Reporter: Patrick McFadin
> Priority: Minor
>
> When a mutation is dropped, you see an INFO log line like this:
> MessagingService.java (line 607) 816 MUTATION messages dropped in last 5000ms
> It would be helpful to know that the mutation was a local hint being dropped. Since this is much more severe case of a dropped mutation, I also think it should be a WARN and not an INFO.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira