[
https://issues.apache.org/jira/browse/CASSANDRA-5026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512059#comment-13512059
]
Sylvain Lebresne commented on CASSANDRA-5026:
---------------------------------------------
That wouldn't be crazy but where else do you propose to set it to true? I
suppose we could avoid to turn it off each time, but at the same time it's not
like it's costing anything and it has the vague advantages that we can control
which operation actually triggers it (for instance the patch don't trigger it
with validation compaction (that don't "repair" the shard either)).
> 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
