cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Cassandra Wiki] Update of "GettingStarted" by JonathanEllis
Date Mon, 14 Dec 2009 21:45:58 GMT
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 JonathanEllis.
The comment on this change is: how to fix java_home on OS X.


  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
  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/`
and make sure that directories exist for the configured log file(s) as well.
+ Some people running OS X have trouble getting Java 6 to work. If you've kept up with Apple's
updates, Java 6 should already be installed (it comes in Mac OS X 10.5 Update 1). Unfortunately,
Apple does not default to using it. What you have to do is change your `JAVA_HOME` environment
setting to `/System/Library/Frameworks/JavaVM.framework/Versions/1.6` and add `/System/Library/Frameworks/JavaVM.framework/Versions/1.6/bin`
to the beginning of your `PATH`.
  And now for the moment of truth, start up Cassandra by invoking `bin/cassandra -f` from
the command line<<FootNote(To learn more about controlling the behavior of startup scripts,
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]].

View raw message