cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5026) Reduce log spam from counter shard warnings
Date Wed, 05 Dec 2012 09:42:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510380#comment-13510380
] 

Sylvain Lebresne commented on CASSANDRA-5026:
---------------------------------------------

bq. only logging it during compaction

Agreed that it's the best option. It'll also make the message more true in the sense that
the message says "will pick highest to self-heal", but we only "self-heal" things on compaction.

Patch attached for that.
                
> Reduce log spam from counter shard warnings
> -------------------------------------------
>
>                 Key: CASSANDRA-5026
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5026
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.1.8
>
>         Attachments: 5026.txt
>
>
> The invalid counter shard warning we can get after unclean shutdown in periodic commitlog
mode or after node movement (CASSANDRA-4071) can spam the log hard since it is logged once
per read until compaction merges it away.

--
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

Mime
View raw message