Permalink
Browse files

Update release notes for 1.1.2

  • Loading branch information...
1 parent a49de3f commit d9f10f962790293fb7bddac2650fab1eb8289186 Jared Morrow committed Apr 13, 2012
Showing with 7 additions and 6 deletions.
  1. +7 −6 RELEASE-NOTES.org
View
@@ -2,7 +2,7 @@
** Features and Improvements for Riak
This is mainly a stabalization release, adding a few stability improvements
-for heavily loaded networks and improving support for running mixed clusters
+for heavily loaded networks and improving support for running mixed clusters
while migrating to the 1.1.x series.
The frequency that Riak checks whether primary partitions need to be transferred
@@ -20,7 +20,7 @@ variable in app.config.
The /usr/sbin/riak script expects /var/run/riak to exist. On Fedora and possibly
other Linux distributions /var/run is built on tmpfs, so the directory created
-at package install time goes away on reboot and the /usr/sbin/riak script does not
+at package install time goes away on reboot and the /usr/sbin/riak script does not
have permissions to recreate it.
As a work around, add this to /etc/rc.local
@@ -31,6 +31,7 @@ mkdir /var/run/riak && chown -R riak /var/run/riak
** Bugs Fixed
+-[[https://github.com/basho/erlang_js/issues/18][erlang_js inlines don't work on XCode 4.3]]
-[[https://github.com/basho/riak_sysmon/issues/5][Work-around for net_kernel:get_status() race condition]]
-[[https://github.com/basho/riak_core/issues/152][Handoff reported as started even if rejected for exceeding handoff concurrency]]
-[[https://github.com/basho/riak_core/issues/153][Intermittent hang with handoff sender]]
@@ -45,12 +46,12 @@ This release includes fixes for systems with heavy MapReduce load.
Pipe maintains a limit on the number of active worker processes in the system.
Workers are created on demand when the pipe executes - they are not reserved
-at pipe creation time.
+at pipe creation time.
Prior to 1.1.1 not all fittings (e.g. get object from riak, map value, reduce)
were checking to make sure their output was being delivered to the next stage
of the pipeline. This has been changed so that the pipe will error if
-processing errors or system limits are hit.
+processing errors or system limits are hit.
As a result of the change if the pipe is overloaded clients will see errors of this form:
={error,<<"Error sending inputs: {error,worker_limit_reached}">>}=
@@ -65,7 +66,7 @@ Different numbers of workers are used based on the type of MapReduce query so
tuning will be very workload dependent.
If you are using Javascript MapReduce you will also need to increase the number of
-Javascript virtual machines in the =riak_kv= section of =app.config=.
+Javascript virtual machines in the =riak_kv= section of =app.config=.
#+BEGIN_SRC erlangB
{map_js_vm_count, #MapVMs},
@@ -102,7 +103,7 @@ a margin for overload.
- Tracing support (see the [[https://github.com/basho/lager/blob/master/README.org][README]])
- Term printing is ~4x faster and much more correct (compared to io:format)
- Bitstring printing support was added
-*** MapReduce Improvements
+*** MapReduce Improvements
- The MapReduce interface now supports requests with empty queries. This allows the 2i, list-keys, and search inputs to return matching keys to clients without needing to include a reduce_identity query phase.
- MapReduce error messages have been improved. Most error cases should now return helpful information all the way to the client, while also producing less spam in Riak's logs.
*** Riak KV Improvements

0 comments on commit d9f10f9

Please sign in to comment.