incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Viktor Jevdokimov <Viktor.Jevdoki...@adform.com>
Subject RE: Testing compaction strategies on a single production server?
Date Tue, 19 Feb 2013 14:09:36 GMT
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 / Pagarbiai
Viktor Jevdokimov
Senior Developer

Email: Viktor.Jevdokimov@adform.com<mailto:Viktor.Jevdokimov@adform.com>
Phone: +370 5 212 3063, Fax +370 5 261 0453
J. Jasinskio 16C, LT-01112 Vilnius, Lithuania
Follow us on Twitter: @adforminsider<http://twitter.com/#!/adforminsider>
Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>

[Adform News] <http://www.adform.com>
[Adform awarded the Best Employer 2012] <http://www.adform.com/site/blog/adform/adform-takes-top-spot-in-best-employer-survey/>


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.

From: Henrik Schröder [mailto:skrolle@gmail.com]
Sent: Tuesday, February 19, 2013 15:57
To: user
Subject: Testing compaction strategies on a single production server?

Hey,

Version 1.1 of Cassandra introduced live traffic sampling, which allows you to measure the
performance of a node without it really joining the cluster: http://www.datastax.com/dev/blog/whats-new-in-cassandra-1-1-live-traffic-sampling
That page mentions that you can change the compaction strategy through jmx if you want to
test out a different strategy on your survey node.

That's great, but it doesn't give you a complete view of how your performance would change,
since you're not doing reads from the survey node. But what would happen if you used jmx to
change the compaction strategy of a column family on a single *production* node? Would that
be a safe way to test it out or are there side-effects of doing that live?

And if you do that, would running a major compaction transform the entire column family to
the new format?
Finally, if the test was a success, how do you proceed from there? Just change the schema?

/Henrik

Mime
View raw message