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 22:23:13 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=8&rev2=9

   1. Betas and release candidates
    Betas are prototype releases considered ready for user testing, and release candidates
have the potential to become the next stable release. These releases represent the state-of-the-art
so are often the best place to start, and since APIs and on-disk storage formats can change
between major versions this can also save you from an upgrade. The testing and feedback is
also highly appreciated. 
  
-   When available, beta and release candidates can be downloaded from [[http://localhost|FIXME]].
+   0.4.0 rc2 is the latest release candidate and can be downloaded [[http://www.apache.org/dyn/closer.cgi/incubator/cassandra/0.4.0/apache-cassandra-incubating-0.4.0-rc2-bin.tar.gz|here]]
(not a direct download link; open in browser).
  
   1. Nightly builds
    Nightly builds represent the current state of development as of the time of the build.
They contain all of the previous days new features, fixes, and newly introduced bugs. The
only guarantee they come with is that they successfully build and the unit tests pass. Nightly
builds are a handy way of testing recent changes, or accessing the latest features and fixes
not found in beta or release candidates, but there is some risk of them being buggy. 
@@ -42, +42 @@

  == 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.
+ 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 is 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.
+ In addition to seeds, you'll also 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.
  
  Once everything is configured and the nodes are running, use the `bin/nodeprobe` utility
to verify a properly connected cluster. For example:
  
@@ -60, +60 @@

  
  <<Anchor(if_something_goes_wrong)>>
  == If Something Goes Wrong ==
+ If you followed the steps in this guide and failed to get up and running, we'd love to help.
Here's what we need.
  
+  1. If you are running anything other than a stable release, please upgrade first and see
if you can still reproduce the problem.
+  1. Make sure debug logging is enabled (hint: `conf/log4j.properties`) and save a copy of
the output.
+  1. Search the [[http://www.mail-archive.com/cassandra-user@incubator.apache.org/|mailing
list archive]] and see if anyone has reported a similar problem and what, if any resolution
they received.
+  1. Ditto for the [[https://issues.apache.org/jira/browse/CASSANDRA|bug tracking system]].
+  1. See if you can put together a unit test, script, or application that reproduces the
problem.
+ 
+ Finally, post a message with all relevant details to the list ([[mailto:cassandra-user-subscribe@incubator.apache.org|subscription
required]]), or hop onto [[http://www.mibbit.com/?server=irc.freenode.net&channel=%23cassandra&nick=ohnoes|IRC]]
(network irc.freenode.net, channel #cassandra) and let us know.
+ 

Mime
View raw message