cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Update of "GettingStarted2" by EricEvans
Date Wed, 23 Sep 2009 19:24:04 GMT
Dear Wiki user,

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

The "GettingStarted2" page has been changed by EricEvans:
http://wiki.apache.org/cassandra/GettingStarted2?action=diff&rev1=9&rev2=10

  == 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 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)>>
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.
  
  The distribution's sample configuration `conf/storage-conf.xml` contains reasonable defaults
for single node operation, but you will need to make sure that the paths exist for `CommitLogDirectory`,
`DataFileDirectories`, `CalloutLocation`, `BootstrapFileDirectory`, and `StagingFileDirectory`.
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.
  
- And now for the moment of truth, start up Cassandra by invoking `bin/cassandra -f` from
the command line. The service should start in the foreground and log gratuitously to standard-out.
Assuming you don't see messages with scary words like "error", or "fatal", or anything that
looks like a Java stack trace, then chances are you've succeeded. To be certain though, take
some time to try out the examples in CassandraCli and ThriftInterface before moving on. Also,
if you run into problems, Don't Panic, calmly proceed to [[#if_something_goes_wrong|If Something
Goes Wrong]].
+ And now for the moment of truth, start up Cassandra by invoking `bin/cassandra -f` from
the command line<<FootNote(For more information on how to control startup behavior,
see RunningCassandra)>>. The service should start in the foreground and log gratuitously
to standard-out. Assuming you don't see messages with scary words like "error", or "fatal",
or anything that looks like a Java stack trace, then chances are you've succeeded. To be certain
though, take some time to try out the examples in CassandraCli and ThriftInterface before
moving on. Also, if you run into problems, Don't Panic, calmly proceed to [[#if_something_goes_wrong|If
Something Goes Wrong]].
  
  == Step 3: Running a cluster ==
  Setting up a Cassandra cluster is ''almost'' as simple as repeating [[#running_a_single_node|Step
2]] for each node in your cluster. There are a few minor exceptions though.

Mime
View raw message