Merge branch 'master' into az-459-leveldb-docs

pages/Riak/Community/Critical-Issues.textile

@@ -0,0 +1,7 @@
+The Basho Dev Team does all that it can to ensure our users are kept up-to-date on critical bugs and issues that may occur. In addition to making Riak bugs public and searchable at "issues.basho.com":https://issues.basho.com, there are two additional avenues to monitor critical issues:
+
+* "Riak Critical Issues Mailing List":http://lists.basho.com/mailman/listinfo/riak-critical-issues_lists.basho.com - A very *low* traffic list used to disseminate information about bugs or issues that might negatively impact a production Riak cluster or deal with data integrity. 
+
+* "Critical Issues Atom Feed":https://issues.basho.com/buglist.cgi?bug_severity=critical&bug_status=NEW&product=Basho%20IT&product=basho_bench&product=bitcask&product=ebloom&product=erlang_js&product=innostore&product=luwak&product=rebar&product=riak&product=riak_webui&product=search&product=webmachine&query_format=advanced&title=Bug%20List&ctype=atom - This is generated by the "Basho Bug Tracker":https://issues.basho.com and will deliver a link to any issue tagged at "critical" to your preferred Atom feed reader. (Keep in mind that the status "critical" is in the eye of the filer, and that community-logged bugs with a "critical" tag may be less severe than what Basho deems "critical".)
+
+_We strive to be as transparent as possible with our community. If you have any ideas or comments on how Basho can do this better, don't hesitate to email *mark@basho.com*_.

pages/Riak/Community/_Sidebar.md

@@ -5,4 +5,5 @@
 * [[Contributing to the Riak Wiki]]
 * [[Contributors]]
 * [[How to Report a Bug]]
+* [[Critical Issues]]
 * [[Logos]]

pages/Riak/Concepts/MapReduce.textile

@@ -601,7 +601,7 @@ Similarly, in Erlang:
 {reduce, FunSpec, [reduce_phase_only_1], Keep}
 ```
 
-<div class="note">Warning: A known bug in Riak 1.0 means that it is possible a reduce function may run more often than specified if handoff happens while the phase is accumulating inputs.</div>
+<div class="note">Warning: A known bug in Riak 1.0.0 means that it is possible a reduce function may run more often than specified if handoff happens while the phase is accumulating inputs.  This bug was fixed in 1.0.1.</div>
 
 h3. Pre-Reduce
 
@@ -620,4 +620,4 @@ Pre-reduce may also be enabled or disabled on a per-phase basis via the Erlang A
 {map, FunSpec, [do_prereduce], Keep}
 ```
 
-<div class="note">Warning: A known bug in Riak 1.0 prevents per-phase pre-reduce from being enabled over HTTP.  This bug also prevents per-phase pre-reduce from being enabled for Javascript phases.  Use the global app.config flag for these cases.</div>
+<div class="note">Warning: A known bug in Riak 1.0.0 prevents per-phase pre-reduce from being enabled over HTTP.  This bug also prevents per-phase pre-reduce from being enabled for Javascript phases.  Use the global app.config flag for these cases. This bug was fixed in 1.0.1.</div>

pages/Riak/Developers/Client-Libraries/Community-Developed-Libraries-and-Projects.textile

@@ -12,10 +12,12 @@ h2. Client Libraries and Frameworks
 * [[Riak C Driver|https://github.com/fenek/riak-c-driver]]
 
 *Clojure*
+* [[knockbox|https://github.com/reiddraper/knockbox]] - An eventual-consistency toolbox for Clojure 
+* [[Welle|https://github.com/michaelklishin/welle]] - Experimental idiomatic Clojure wrapper around the Riak Java Driver 
 * [[clj-riak|http://github.com/mmcgrana/clj-riak]] - Clojure bindings to the Riak Protocol Buffers API
 
 *Common Lisp*
-* [[cl-riak (1)|https://github.com/whee/cl-riak]]
+* [[cl-riak (1)|https://github.com/whee/cl-riak]] 
 * [[cl-riak (2)|https://github.com/eriknomitch/cl-riak]]
 
 *Django*
@@ -57,6 +59,7 @@ h2. Client Libraries and Frameworks
 * [[Data.RiakClient|http://github.com/garethstokes/Data.RiakClient]]
 
 *Node.js*
+* [[resourceful-riak|https://github.com/admazely/resourceful-riak]] - A Riak engine to the [[resourceful|https://github.com/flatiron/resourceful/]] model framework from [[flatiron|https://github.com/flatiron/]].
 * [[Connect-Riak|https://github.com/frank06/connect-riak]] - Riak Session Store for Connect backed by [[Riak-js|http://riakjs.org/]]
 * [[Riak-js|http://riakjs.org/]] - Node.js client for Riak with support for HTTP and Protocol Buffers
 * [[Riakjs-model|https://github.com/dandean/riakjs-model]] - a model abstraction around riak-js
@@ -77,13 +80,15 @@ h2. Client Libraries and Frameworks
 * [[Riak Module for The Play Framework|http://www.playframework.org/modules/riak-head/home]]
 
 *Python*
+* [[riak_crdt|https://github.com/ericmoritz/riak_crdt]] - A CRDT (Conflict-Free Replicated Data Type) loader for Riak using the [[crdt API|https://github.com/ericmoritz/crdt]]
 * [[txriak|https://launchpad.net/txriak]]- a Twisted module for communicating with Riak via the HTTP interface
 * [[txriakidx|https://github.com/williamsjj/txriakidx]] - Riak client for Twisted Python that implements transparent indexes
 
 *Racket*
 * [[Racket-Riak|https://github.com/shofetim/Racket-Riak]] - Racket API to Riak
 
 *Ruby*
+* [[Shogun|https://github.com/krainboltgreene/shogun]] - A light weight, powerful Ruby web application framework with first class support for Riak.
 * [[Risky|https://github.com/aphyr/risky]] - A lightweight Ruby ORM for Riak 
 * [[Riak Model|http://github.com/botanicus/riak-model]]
 * [[Riak DataObjects adapter|http://github.com/botanicus/do_riak]]
@@ -123,12 +128,14 @@ h2. Backup Tools
 
 h2. riak_core
 
+* [[Misultin Riak Core VNode Dispatcher|https://github.com/jbrisbin/misultin-riak-core-vnode-dispatcher]]
 * [[ecnty|https://github.com/benmmurphy/ecnty]] - Partitioned Counter Based on Riak Core 
 * [[rebar_riak_core|https://github.com/websterclay/rebar_riak_core]] - Rebar templates for generating riak_core applications
 * [[Try Try Try|https://github.com/rzezeski/try-try-try/]] - Ryan Zezeski's working blog that explores many aspects of riak_core (this is an amazing resource)
 * [[riak_zab|https://github.com/jtuple/riak_zab]] - an extension for riak_core that provides totally ordered atomic broadcast capabilities 
 * [[riak_zab_example|https://github.com/jtuple/riak_zab_example]] - an example application that allows you to build a multi-node cluster using riak_zab
 
+
 h2. Riak and RabbitMQ 
 
 * [[Riak/RabbitMQ Commit Hook|https://github.com/jbrisbin/riak-rabbitmq-commit-hooks]] - A Post-Commit hook that sends entries into a RabbitMQ broker using the Erlang AMQP client
@@ -137,6 +144,12 @@ h2. Riak and RabbitMQ
 * [[msg_store_bitcask_index|https://github.com/videlalvaro/msg_store_bitcask_index]] - RabbitMQ message store index with Bitcask Backend
 * [[RabbitMQ-Riak Core Vnode Dispatcher|https://github.com/jbrisbin/rabbitmq-riak-code-vnode-dispatcher]]
 
+h2. Lager 
+
+* [[Lager AMQP Backend|https://github.com/jbrisbin/lager_amqp_backend]]
+
+
+
 h2. Recipes, Cookbooks, and Configurations
 
 * [[Scalarium-Riak|https://github.com/mattmatt/scalarium-riak]] - Riak Cookbooks for Scalarium Platform

pages/Riak/Installation/Installing-Erlang.textile → pages/Riak/Installation/Installing-Erlang.md

@@ -72,7 +72,23 @@ $ tar zxvf otp_src_R14B03.tar.gz
 $ cd otp_src_R14B03
 ```
 
-Next, configure Erlang.  If you're on Snow Leopard (OS/X 10.6) or Leopard (OS/X 10.5) with an Intel processor:
+Next, configure Erlang.  
+
+If you're on Lion (OS/X 10.7) you can use LLVM, the default, or GCC to compile Erlang.
+
+Using LLVM:
+```bash
+$ CFLAGS=-O0 ./configure --enable-hipe --enable-smp-support --enable-threads \
+--enable-kernel-poll --enable-darwin-64bit
+```
+If you prefer GCC:
+```bash
+$ CC=gcc-4.2 CPPFLAGS='-DNDEBUG' MAKEFLAGS='-j 3' \
+./configure --enable-hipe --enable-smp-support --enable-threads \
+--enable-kernel-poll --enable-darwin-64bit
+```
+
+If you're on Snow Leopard (OS/X 10.6) or Leopard (OS/X 10.5) with an Intel processor:
 
 ```bash
 $ ./configure --enable-hipe --enable-smp-support --enable-threads \

pages/Riak/Installation/Installing-Riak-from-Source.textile

@@ -18,9 +18,9 @@ Download the Riak source package from the [[Download Center|http://downloads.bas
 
 
 ```bash
-$ curl -O http://downloads.basho.com/riak/riak-1.0.1/riak-1.0.1.tar.gz
-$ tar zxvf riak-1.0.1.tar.gz
-$ cd riak-1.0.1
+$ curl -O http://downloads.basho.com/riak/riak-1.0.2/riak-1.0.2.tar.gz
+$ tar zxvf riak-1.0.2.tar.gz
+$ cd riak-1.0.2
 $ make rel
 ```
 

pages/Riak/Installation/Installing-on-Debian-and-Ubuntu.textile

@@ -8,17 +8,17 @@ h3. 64-bit
 
 
 ```bash
-$ wget http://downloads.basho.com/riak/riak-1.0.1/riak_1.0.1-1_amd64.deb
-$ sudo dpkg -i riak_1.0.1-1_amd64.deb
+$ wget http://downloads.basho.com/riak/riak-1.0.2/riak_1.0.2-1_amd64.deb
+$ sudo dpkg -i riak_1.0.2-1_amd64.deb
 ```
 
 
 h3. 32-bit
 
 
 ```bash
-$ wget http://downloads.basho.com/riak/riak-1.0.1/riak_1.0.1-1_i386.deb
-$ sudo dpkg -i riak_1.0.1-1_i386.deb
+$ wget http://downloads.basho.com/riak/riak-1.0.2/riak_1.0.2-1_i386.deb
+$ sudo dpkg -i riak_1.0.2-1_i386.deb
 ```
 
 h2. From source
@@ -37,9 +37,9 @@ If you have not installed Erlang, please [[do so|Installing Erlang]].
 Now we can download and install Riak:
 
 ```bash
-$ wget http://downloads.basho.com/riak/riak-1.0.1/riak-1.0.1.tar.gz
-$ tar zxvf riak-1.0.1.tar.gz
-$ cd riak-1.0.1
+$ wget http://downloads.basho.com/riak/riak-1.0.2/riak-1.0.2.tar.gz
+$ tar zxvf riak-1.0.2.tar.gz
+$ cd riak-1.0.2
 $ make rel
 ```
 

pages/Riak/Installation/Installing-on-Mac-OS-X.textile

@@ -15,8 +15,8 @@ To run Riak from our precompiled tarball, run these commands for the appropriate
 h3. 64-bit
 
 ```bash
-$ curl -O http://downloads.basho.com/riak/riak-1.0.1/riak-1.0.1-osx-x86_64.tar.gz
-$ tar xzvf riak-1.0.1-osx-x86_64.tar.gz
+$ curl -O http://downloads.basho.com/riak/riak-1.0.2/riak-1.0.2-osx-x86_64.tar.gz
+$ tar xzvf riak-1.0.2-osx-x86_64.tar.gz
 ```
 
 After the release is untared you will be able to cd into the riak directory and execute bin/riak start to start the Riak node.
@@ -54,9 +54,9 @@ Next, download and unpack the source distribution.
 
 
 ```bash
-$ curl -O http://downloads.basho.com/riak/riak-1.0.1/riak-1.0.1.tar.gz
-$ tar zxvf riak-1.0.1.tar.gz
-$ cd riak-1.0.1
+$ curl -O http://downloads.basho.com/riak/riak-1.0.2/riak-1.0.2.tar.gz
+$ tar zxvf riak-1.0.2.tar.gz
+$ cd riak-1.0.2
 $ make rel
 ```
 

pages/Riak/Installation/Installing-on-RHEL-and-CentOS.textile

@@ -4,8 +4,8 @@ h2. From our custom .rpm package
 
 
 ```bash
-$ wget http://downloads.basho.com/riak/riak-1.0.1/riak-1.0.1-1.el5.x86_64.rpm
-$ sudo rpm -Uvh riak-1.0.1-1.el5.x86_64.rpm
+$ wget http://downloads.basho.com/riak/riak-1.0.2/riak-1.0.2-1.el5.x86_64.rpm
+$ sudo rpm -Uvh riak-1.0.2-1.el5.x86_64.rpm
 ```
 
 
@@ -31,9 +31,9 @@ Now we can download and install Riak:
 
 
 ```bash
-$ wget http://downloads.basho.com/riak/riak-1.0.1/riak-1.0.1.tar.gz
-$ tar zxvf riak-1.0.1.tar.gz
-$ cd riak-1.0.1
+$ wget http://downloads.basho.com/riak/riak-1.0.2/riak-1.0.2.tar.gz
+$ tar zxvf riak-1.0.2.tar.gz
+$ cd riak-1.0.2
 $ make rel
 ```
 

pages/Riak/Operations/Storage-Backends/Bitcask.md

@@ -440,11 +440,11 @@ speeding up disk I/O.  Note that this can be spoiled when you still have
 `atime` enabled on your filesystem because the disk head will have to move to
 update both the data blocks and the file and directory meta data blocks.  The
 primary speed-up from a log-based database is its ability to minimize disk head
-seeks.  Deleating a value from Bitcask is a two step process.  First we append
+seeks.  Deleting a value from Bitcask is a two step process.  First we append
 a "tombstone" record to the file open for writes which indicates that a value
 was marked for deletion at that time.  At the same time we remove references to
 that key in the in-memory `keydir` information.  Later, during a merge,
-non-active non-active data files are scanned and only those values without
+non-active data files are scanned and only those values without
 tombstones are merged into the active data file.  This effectively removes the
 obsolete data and reclaims disk space associated with it.  This data management
 strategy may use up a lot of space over time, since we just write out new