Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "GettingStarted" page has been changed by MakiWatanabe: http://wiki.apache.org/cassandra/GettingStarted?action=diff&rev1=60&rev2=61 Comment: fix remaining reference to SVN checkout == Step 2: Running a single node == Cassandra is meant to run on a cluster of nodes, but will run equally well on a single machine. This is a handy way of getting familiar with the software while avoiding the complexities of a larger system. - Since there isn't currently an installation method per se, the easiest solution is to simply run Cassandra from an extracted archive<<FootNote(Users of Debian or Debian-based derivatives can install the latest stable release in package form, see DebianPackaging for details.)>><<FootNote(Users of RPM-based distributions can get packages from [[http://www.datastax.com/blog/announcing-rpms-cassandra|Datastax]])>> or SVN checkout (see: [[#picking_a_version|Picking a version]]). Also, unless you've downloaded a binary distribution, you'll need to compile the software by invoking `ant` from the top-level directory. + Since there isn't currently an installation method per se, the easiest solution is to simply run Cassandra from an extracted archive<<FootNote(Users of Debian or Debian-based derivatives can install the latest stable release in package form, see DebianPackaging for details.)>><<FootNote(Users of RPM-based distributions can get packages from [[http://www.datastax.com/blog/announcing-rpms-cassandra|Datastax]])>> or Git checkout (see: [[#picking_a_version|Picking a version]]). Also, unless you've downloaded a binary distribution, you'll need to compile the software by invoking `ant` from the top-level directory. The distribution's sample configuration `conf/cassandra.yaml` contains reasonable defaults for single node operation, but you will need to make sure that the paths exist for `data_file_directories`, `commitlog_directory`, and `saved_caches_directory`. Additionally, take a minute now to look over the logging configuration in `conf/log4j.properties` and make sure that directories exist for the configured log file(s) as well.
