[
https://issues.apache.org/jira/browse/CASSANDRA-7978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141244#comment-14141244
]
Jason Brown commented on CASSANDRA-7978:
----------------------------------------
>> bq. rolling restart seem reasonable
I don't completely agree with this. In some situations/organizations, rolling
restarts are not as willy nilly as one might wish. Further, what if you have
1000s of nodes in the cluster? Rolling restart might take a day or two,
depending on your tolerance for inflicting pain on users :).
bq. we could add code to reopen all the readers when this setting is changed
I don't think we need to go far, but maybe just visit all the open readers and
update the local copy of the compression settings there should be sufficient,
perhaps?
> 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
>
>
> 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)
