Log message:
Update wip/riak to 2.1.1

Riak 2.1.1

Fixes:
- Make default handoff_ip value 0.0.0.0 in vars.config.

Riak 2.1.0

New features:
- Performance Improvements
- Write-Once Bucket Type

Changes:
- Applies fix to most causes of data loss from repeated causal history.
- Update API to retrieve active preflist based on particular bucket/key.
- Add a JSON writer for several riak-admin commands
- Integrate performance patches into Erlang R16 VM used by Riak
- Add riak_core_ring_manager:is_stable_ring/0 to public API.
- Add search_query_latency_mean and search_index_latency_mean metrics.

Bugs fixed:
- Timeouts during bulk data load, possible tie in to yz_events crash and
  a bad state on core create
- Don't delete siblings in YZ when using SC or CRDTs.
- Creating a new search index via HTTP responds before the index
  is available
- AAE Failing hourly, with exit value {badarg,46},
  [{base64,decode_binary[{base64.erl…
- yz_events:handle_info called with bad arguments.
- Fix YZ stats name typo from throughput to throughput.
- SSL connections from peers with matching wildcard name are
  always rejected.

Log message:
Fix distfile checksum

Log message:
Update riak to 2.0.5.

2.0.5
- Adding --format=csv to allow some administrative commands to be output
  as csv files
- Sequential tuning Improving leveldb for when a single database (vnode)
  receives a large write volume. This situation commonly occurs during
  a Riak handoff operation.
- Add optional timeout for handle_handoff_data callback and improve logging
- L0 Realtime connection balancing. N v3 repl realtime connections are chosen
  randomly which can lead to large imbalances. Previous implementations did
  a better job of ensuring there was good balance. The goal of this work is
  to bring that back to v3 realtime replication.
- If Solr complains that the index exists, update Riak's metadata to reflect it
- node_get_fsm_time and node_put_fsm_time stats are incorrect.
  node_get_fsm_time and node_put_fsm_time values are an order of magnitude
  smaller than 2.0.2
- Other bugfixes

2.0.4
- Improve AAE fullsync by estimating total number of keys. This allows for
  better sizing of the bloom filter when performing a bloom-fold-based exchange
  and enhances the adaptive exchange logic that was added previously in Riak
  2.0.1. In that version, the new riak_repl.fullsync_direct_percentage_limit
  setting was added, which allowed the limit to be specified as a percentage of
  total keys rather than as a fixed number.
- Added last_fullsync_complete stat tracking
- Expose AAE tree status in the logs
- Improve AAE fullsync by using breadth-first exchange
- Riak now uses Exometer for collecting metrics and has an improved CLI for
  finding and displaying them
- Internal components can process partial configurations as if they were in the
  global config file. This supports the handoff visibility changes.
- Riak now uses Clique for managing CLI commands. The initial commands covered
  exist to increase visibility into the handoff process and provide Cuttlefish
  config support from the CLI.
- Fix stats process crash if no leader
- Address some minor bugs around establishing SSL connections
- 2.0 port of AAE transient filesystem failures
- Fix error/retry exit counts on location down messages
- Fix deadlock when performing AAE fullsync over SSL (Erlang VM patch)
- Prevent servers from accepting SSLv3 connections (Erlang VM patch)
- The map Data Type is now more efficient when merging
- Fix a case in which sibling explosion could occur during handoff
- Special handling for the net_ticktime setting in admin scripts
- Add a missing function clause in riak_kv_node that could result in crashes
- Avoid timeouts when handoff sender is folding over a large number of keys
- No more extra work for handoff sender after TCP error makes that work useless
- Report error when failing to open file instead of crashing when calling
  riak_core_util:replace_file/2
- Ensure creation of ensembles when strongly consistent bucket types
  with different n_vals from default bucket type do not yet have buckets
- Avoid SSL deadlocks that occur when sending data bidirectionally using Erlang
  SSL sockets. The fix is a patch to the Erlang VM shipped with the build.

2.0.3:
- Introduce exometer metrics into 2.0
- Remove afunix from EXOMETER_PACKAGES.
- remove afunix from reltool.config

Full changelog:

https://github.com/basho/riak/blob/2.0/RELEASE-NOTES.md

Log message:
Fix PLIST handling. Ignore more unused script shebangs.

Log message:
Try to fix NetBSD builds. Account for a different PLIST on non-SunOS
platforms and with hipe enabled.

Log message:
Fix incorrect PLIST vars, improve patch file.

Log message:
Update riak to 2.0.2.

- Clean up and simplify Makefile.
- Add an SMF manifest.
- Remove innostore option, doesn't seem to be maintained for recent OTP
- Remove some unneeded patching.

Upstream changes since 1.4.6 too numerous, please see the release notes:

  http://docs.basho.com/riak/2.0.2/intro-v20/

The upgrade guide:

  http://docs.basho.com/riak/2.0.2/upgrade-v20/

Log message:
Update riak to 1.4.6

Changes since 1.4.2:
* Secondary index improvements
* bitcask/122:   [Bound merge queue to number of partitions]
* node_package/101: [Add extra options to debuild template]
* node_package/93: [Incorrect package format in SmartOS causes segfault
  on pkg_info]
* riak_core/429: [Handoff fix is to enable handoff to complete in mixed
  pre-1.4 clusters]
* riak_core/467: [Bound the time that stats calculation can take]
* riak_core/470: [Provide a synchronous registration and unregistration
  of services.]
* riak_core/476: [Remove connection manager and service manager.]
* riak_kv/715: [2i term regex filter 1.4]
* riak_kv/743: [Fix vnode sending > max_results items for 2i query]
* riak_kv/766: [Fix error when hashing index data in tree builds]
* riak_kv/767: [Fixed 2i queries in mixed clusters]
* riak_kv/772: [Fix broken return terms handling]
* riak_kv/774: [Enable bloom filters for AAE LevelDB instances]
* leveldb/110 [Add option for changing fadvise
* leveldb/112: [Create asynchronous close path to resolve race between
  write threads]