Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Wed, 23 Sep 2009 19:24:04 -0000
Message-ID: <20090923192404.24692.22112@eos.apache.org>
Subject: 
 =?utf-8?q?=5BCassandra_Wiki=5D_Update_of_=22GettingStarted2=22_by_EricEva?=
 =?utf-8?q?ns?=

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=3Ddiff&rev1=3D9&rev=
2=3D10

  =3D=3D Step 2: Running a single node =3D=3D
  Cassandra is meant to run on a cluster of nodes, but will run equally wel=
l on a single machine. This is a handy way of getting familiar with the sof=
tware while avoiding the complexities of a larger system.
  =

- Since there isn't currently an installation method per se, the easiest so=
lution is to simply run Cassandra from an extracted archive or SVN checkout=
 (see: [[#picking_a_version|Picking a version]]). Also, unless you've downl=
oaded a binary distribution, you'll need to compile the software by invokin=
g `ant` from the top-level directory.
+ Since there isn't currently an installation method per se, the easiest so=
lution is to simply run Cassandra from an extracted archive<<FootNote(Users=
 of Debian or Debian-based derivatives can install the latest stable releas=
e 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 su=
re that the paths exist for `CommitLogDirectory`, `DataFileDirectories`, `C=
alloutLocation`, `BootstrapFileDirectory`, and `StagingFileDirectory`. Addi=
tionally, 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/cass=
andra -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 s=
tack trace, then chances are you've succeeded. To be certain though, take s=
ome 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/cass=
andra -f` from the command line<<FootNote(For more information on how to co=
ntrol startup behavior, see RunningCassandra)>>. The service should start i=
n the foreground and log gratuitously to standard-out. Assuming you don't s=
ee messages with scary words like "error", or "fatal", or anything that loo=
ks like a Java stack trace, then chances are you've succeeded. To be certai=
n though, take some time to try out the examples in CassandraCli and Thrift=
Interface before moving on. Also, if you run into problems, Don't Panic, ca=
lmly proceed to [[#if_something_goes_wrong|If Something Goes Wrong]].
  =

  =3D=3D Step 3: Running a cluster =3D=3D
  Setting up a Cassandra cluster is ''almost'' as simple as repeating [[#ru=
nning_a_single_node|Step 2]] for each node in your cluster. There are a few=
 minor exceptions though.