Welcome to Riak.

Date: 2010-06-09 10:06:44 CDT

Table of Contents
1 Overview 
2 Quick Start 
    2.1 Building Riak 
    2.2 Starting Riak 
    2.3 Connecting a client to Riak 
    2.4 Clients for Other Languages 
3 Server Management 
    3.1 Configuration 
    3.2 Server Control 
        3.2.1 bin/riak 
        3.2.2 bin/riak-admin 

1 Overview 
  Riak is a distributed, decentralized data storage system. 
  Below, you will find the "quick start" directions for setting up and
  using Riak.  For more information, browse the following files:
  * README:  this file
  * TODO:    a list of improvements planned for Riak
  * LICENSE: the license under which Riak is released
  * apps/    the source tree for Riak and all its dependencies
  * doc/
    - Riak Administration Guide
    - architecture.txt: details about the underlying design of Riak
    - basic-client.txt: slightly more detail on using Riak
    - basic-setup.txt:  slightly more detail on setting up Riak
    - basic-mapreduce.txt: introduction to map/reduce on Riak
    - using Javascript with Riak map/reduce
    - man/riak.1.gz: manual page for the riak(1) command
    - man/riak-admin.1.gz manual page for the riak-admin(1) command
    - raw-http-howto.txt: using the Riak HTTP interface

2 Quick Start 

  This section assumes that you have copy of the Riak source tree. To get
  started, you need to:
  1. Build Riak
  2. Start the Riak server
  3. Connect a client and store/fetch data

2.1 Building Riak 

   Assuming you have a working Erlang (R13B04 or later) installation,
   building Riak should be as simple as:

  $ cd $RIAK
  $ make rel

2.2 Starting Riak 

   Once you have successfully built Riak, you can start the server with the
   following commands:

  $ cd $RIAK/rel/riak
  $ bin/riak start

   Now, verify that the server started up cleanly and is working:

   $ bin/riak-admin test

   Note that the $RIAK/rel/riak directory is a complete, self-contained instance
   of Riak and Erlang. It is strongly suggested that you move this directory
   outside the source tree if you plan to run a production instance.

2.3 Connecting a client to Riak 

   Now that you have a functional server, let's try storing some data in
   it. First, start up a erlang node using our embedded version of erlang:

  $ erts-<vsn>/bin/erl -name riaktest@ -setcookie riak
  Eshell V5.7.4  (abort with ^G)

   Now construct the node name of Riak server and make sure we can talk to it:

  (riaktest@> RiakNode = 'riak@'.
  (riaktest@> net_adm:ping(RiakNode).
   We are now ready to start the Riak client:

  (riaktest@> {ok, C} = riak:client_connect(RiakNode).

   Let's create a shopping list for bread at /groceries/mine:

  (riaktest@> O0 = riak_object:new(<<"groceries">>, <<"mine">>, ["bread"]).
  O0 = riak_object:new(<<"groceries">>, <<"mine">>, ["bread"]).
   (riaktest@> C:put(O0, 1).
    Now, read the list back from the Riak server and extract the value

  (riaktest@> {ok, O1} = C:get(<<"groceries">>, <<"mine">>, 1).
   (riaktest@> %% extract the value
   (riaktest@> V = riak_object:get_value(O1).

     Add milk to our list of groceries and write the new value to Riak:

  (riaktest@> %% add milk to the list
  (riaktest@> O2 = riak_object:update_value(O1, ["milk" | V]).
  (riaktest@> %% store the new list
  (riaktest@> C:put(O2, 1).

     Finally, see what other keys are available in groceries bucket:

  (riaktest@> C:list_keys(<<"groceries">>).

2.4 Clients for Other Languages 

   Client libraries are available for many languages.  Rather than
   bundle them with the Riak server source code, we have given them
   each their own source repository.  Currently, official Riak
   client language libraries include:

   + Javascript

   + Python

   + Ruby

   + Java

   + PHP

   + Erlang
     (using protocol buffers instead of distributed Erlang)

3 Server Management 

3.1 Configuration 
   Configuration for the Riak server is stored in $RIAK/rel/riak/etc
   directory. There are two files:
   - vm.args 
     This file contains the arguments that are passed to the Erlang VM
     in which Riak runs. The default settings in this file shouldn't need to be
     changed for most environments.

   - app.config 
     This file contains the configuration for the Erlang applications
     that run on the Riak server.

   More information about this files is available in doc/basic-setup.txt.

3.2 Server Control 

3.2.1 bin/riak 
    This script is the primary interface for starting and stopping the Riak

    To start a daemonized (background) instance of Riak:

    $ bin/riak start 

    Once a server is running in the background you can attach to the Erlang
    console via:

    $ bin/riak attach

    Alternatively, if you want to run a foreground instance of Riak, start it

    $ bin/riak console

    Stopping a foreground or background instance of Riak can be done from a
    shell prompt via:

    $ bin/riak stop 

    Or if you are attached/on the Erlang console:

    (riak@> q().

    You can determine if the server is running by:

    $ bin/riak ping

3.2.2 bin/riak-admin 
    This script provides access to general administration of the Riak server. 
    The below commands assume you are running a default configuration for 
    parameters such as cookie.

    To join a new Riak node to an existing cluster:

  $ bin/riak start # If a local server is not already running
  $ bin/riak-admin join <node in cluster>

    (Note that you must have a local node already running for this to work)
    To verify that the local Riak node is able to read/write data:
    $ bin/riak-admin test

    To backup a node or cluster run the following:
    $ bin/riak-admin backup riak@X.X.X.X riak <directory/backup_file> node
    $ bin/riak-admin backup riak@X.X.X.X riak <directory/backup_file> all
    Restores can function in two ways, if the backup file was of a node the 
    node will be restored and if the backup file contains the data for a 
    cluster all nodes in the cluster will be restored.
    To restore from a backup file:
    $ riak-admin restore riak@X.X.X.X riak <directory/backup_file>
    To view the status of a node:
    $ bin/riak-admin status
    If you change the IP or node name you will need to use the reip command:
    $ bin/riak-admin reip <old_nodename> <new_nodename>