You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2012/12/19 09:27:12 UTC

[jira] [Comment Edited] (CASSANDRA-5053) not possible to change crc_check_chance

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

Aleksey Yeschenko edited comment on CASSANDRA-5053 at 12/19/12 8:25 AM:
------------------------------------------------------------------------

No idea. But all other setters in that mbean start with 'set'. Are they not exposed either?
                
      was (Author: iamaleksey):
    No idea. But all other setters in that mbean start with 'set'. Are they not exposes either?
                  
> not possible to change crc_check_chance
> ---------------------------------------
>
>                 Key: CASSANDRA-5053
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5053
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.1.1
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 1.1.9
>
>         Attachments: 0001-CASSANDRA-5053-make-it-possible-to-change-crc_check_.patch, 0001-fix-CASSANDRA-5053-not-possible-to-change-crc_check_.patch, 5053-v2.txt
>
>
> It is not possible to change crc_check_chance using a schema modification after CASSANDRA-4266
> This patch fixes that and moves the setting out into a configuration parameter instead, you dont want to upgrade/scrub/.. all your sstables to change the crc_check_chance.

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