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 Tue, 22 Sep 2009 20:13:16 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=4&rev2=5

  == Introduction ==
  Cassandra is an advanced topic, and while work is always underway to make things easier,
it can still be daunting to get up and running for the first time. This document aims to provide
a few easy to follow steps to take the first-time user from installation, to an operational
Cassandra cluster.
  
+ <<Anchor(picking_a_version)>>
  == Step 1: Picking a version ==
  At any given time, there are a number of different versions available for install:
  
@@ -29, +30 @@

    Instructions for checking out the source code can always be found on the [[http://incubator.apache.org/cassandra/#download|website]].
  
  == Step 2: Running a single node ==
- Cassandra is meant to be run on a cluster of nodes, but it will run equally as well on a
single machine. This is a handy way of getting familiar with the software while avoiding the
complexities of a larger system.
+ 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.
+ 
+ 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]].
  
  == Step 3: Running a cluster ==
  
  == Step 4: Write your application ==
  
+ <<Anchor(if_something_goes_wrong)>>
  == If Something Goes Wrong ==
  

Mime
View raw message