I *think* it will work. The steps in the blog post to change the compaction strategy before RING_DELAY expires is to ensure no sstables are created before the strategy is changed.But I think you will be venturing into unchartered territory where their might be dragons. And not the fun Disney kind.While it may be more work I personally would use one node in write survey to test LCSCheersOn 20/02/2013, at 6:28 AM, Henrik Schröder <firstname.lastname@example.org> wrote:/HenrikWell, that answer didn't really help. I know how to make a survey node, and I know how to simulate reads to it, it's just that that's a lot of work, and I wouldn't be sure that the simulated load is the same as the production load.So, is it possible to modify org.apache.cassandra.db.[keyspace].[column family].CompactionStrategyClass through jmx on a production server without any ill effects? Or is this only possible to do on a survey node while it is in a specific state?
We gather a lot of metrics from our production servers, so we know exactly how they perform over long periods of time. Changing a single server to run a different compaction strategy would allow us to know in detail how a different strategy would impact the cluster.
On Tue, Feb 19, 2013 at 3:09 PM, Viktor Jevdokimov <Viktor.Jevdokimov@adform.com> wrote:
Just turn off dynamic snitch on survey node and make read requests from it directly with CL.ONE, watch histograms, compare.
Regarding switching compaction strategy there’re a lot of info already.
Best regards / PagarbiaiViktor JevdokimovSenior Developer
Email: Viktor.Jevdokimov@adform.comJ. Jasinskio 16C, LT-01112 Vilnius, LithuaniaFollow us on Twitter: @adforminsiderTake a ride with Adform's Rich Media Suite
Disclaimer: The information contained in this message and attachments is intended solely for the attention and use of the named addressee and may be confidential. If you are not the intended recipient, you are reminded that the information remains the property of the sender. You must not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this message in error, please contact the sender immediately and irrevocably delete this message and any copies.