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:57:12 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=5&rev2=6

  
    Instructions for checking out the source code can always be found on the [[http://incubator.apache.org/cassandra/#download|website]].
  
+ <<Anchor(running_a_single_node)>>
  == 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.
  
@@ -39, +40 @@

  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 ==
+ 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.
+ 
+ Cassandra nodes exchange information about one another using a mechanism called Gossip,
but to get the ball rolling a newly started node needs to know of at least one other, this
is called a `Seed`. It's customary to pick a small number of relatively stable nodes to serve
as your seeds, but there is no hard-and-fast rule here. Do make sure that each seed also knows
of at least one other, remember, the goal to avoid a chicken-and-egg scenario and provide
an avenue for all nodes in the cluster to discover one another.
+ 
+ In addition to seeds, you'll need to configure the IP interface to listen on for Gossip
and Thrift, (`ListenAddress` and `ThriftAddress` respectively). Use a `ListenAddress` that
will be reachable from the `ListenAddress` used on all other nodes, and a `ThriftAddress`
that will be accessible to clients.
+ 
  
  == Step 4: Write your application ==
  

Mime
View raw message