cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7978) CrcCheckChance should not be stored as part of an sstable
Date Mon, 22 Sep 2014 20:44:35 GMT

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

Jason Brown commented on CASSANDRA-7978:
----------------------------------------

I just found this ticket, #CASSANDRA-5053, which exposes CFS.setCrcCheckChance() as an mbean
value (configurable at runtime). Would that be sufficient for [~kohlisankalp]'s needs, of
being able to adjust the CRC check chance dynamically (without restart/upgradesstables/etc)?

 

> CrcCheckChance should not be stored as part of an sstable
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-7978
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7978
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: sankalp kohli
>            Assignee: T Jake Luciani
>            Priority: Minor
>             Fix For: 2.0.11
>
>         Attachments: 7978.txt, 7978v2.txt
>
>
> CrcCheckChance is stored with compression parameters in the sstable. The only way to
change it is to do upgrade sstable. I don't see why it should not be a hot property. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message