You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by Apache Wiki <wi...@apache.org> on 2010/02/27 21:36:15 UTC

[Cassandra Wiki] Update of "StorageConfiguration" by AntonBelyaev

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "StorageConfiguration" page has been changed by AntonBelyaev.
http://wiki.apache.org/cassandra/StorageConfiguration?action=diff&rev1=10&rev2=11

--------------------------------------------------

  }}}
  Cassandra uses MD5 hash internally to hash the keys to place on the ring in a {{{RandomPartitioner}}}. So it makes sense to divide the hash space equally by the number of machines available using {{{InitialToken}}} ie, If there are 10 machines, each will handle 1/10th of maximum hash value) and expect that the machines will get a reasonably equal load.
  
+ With {{{OrderPreservingPartitioner}}} the keys themselves are used to place on the ring. One of the potential drawback of this approach is that if rows are inserted with sequential keys, all the write load will go to the same node.
+ 
  == Directories ==
  Directories: Specify where Cassandra should store different data on disk.  Keep the data disks and the {{{CommitLog}}} disks separate for best performance. See also [[FAQ#what_kind_of_hardware_should_i_use|what kind of hardware should I use?]]