Well, we have had some problems when a compactation was kicking into the system under heavy load on version 0.6.3. This caused some nodes to respond slow and caused some application instability.
What we do, playing with compactation strategy, was to move the major compactation to a fixed hour of the day when we know there won't be heavy traffic. But all this was posible because we had enough disk space to continue holding new SSTables storage without problem. Hope this information throw some light on my recommendation. On Sat, Feb 12, 2011 at 3:47 PM, mcasandra <mohitanch...@gmail.com> wrote: > > > Javier Canillas wrote: > > > > > > On the other hand, if your application will use heavily cassandra i > > recommend making a calcularon of the data volumen that will handle and > > using a partition that is actually 3 to 5 times bigger. Doing so you > > will be able to play around with compactation strategy to avoid > > latency when your application is under heavy load. > > > > > > Can you please explain with an example? I just started reading about > Cassandra, all I know is that Cassandra partitions based on the hash space > and divides equally among all the nodes. The tokens (keys) are then > distributed equally accross N replica nodes. > > -- > View this message in context: > http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Indexes-and-hard-disk-tp6018234p6019297.html > Sent from the cassandra-u...@incubator.apache.org mailing list archive at > Nabble.com. >
