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 Fri, 07 Dec 2012 14:45:21 GMT

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

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

I'm good with v2, though as said before it sets the flag for anything that is executed by
the compactionExecutor (validation, cleanup, scrub, ...) not just actual compaction, so maybe
we can rename it from "isCompacting"?
                
> 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, 5026-v2.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