Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


riak (51) Versions 2.4.17

Installs and configures Riak distributed data store

cookbook 'riak', '= 2.4.17', :supermarket
cookbook 'riak', '= 2.4.17'
knife supermarket install riak
knife supermarket download riak
Quality 0%

Riak Cookbook

Build Status


Riak is a Dynamo-inspired key/value store that scales predictably and easily. Riak combines a decentralized key/value store, a flexible map/reduce engine, and a friendly HTTP/JSON query interface to provide a database ideally suited for Web applications. And, without any object-relational mappers and other heavy middleware, applications built on Riak can be both simpler and more powerful. For complete documentation and source code, see the Riak home page at Basho.

Getting Started

The Riak cookbook can be used just by adding "riak" to the runlist for a node. The default settings will cause Riak to be installed and configured. All the config options exist in the node['riak']['config'] namespace and can be set to the appropriate Erlang data type with the methods : to_erl_string and to_erl_tuple . For more information see the erlang_template_helper repository

Package Installation

There are two options for package installation: package and custom_repository. If you are using a Red Hat, CentOS, Fedora, Debian or Ubuntu distributions, package installation is recommended and is the default.

The package parameters available are version, type and, optionally for source installation, an install prefix:

# default.rb
node['riak']['install_method'] = "package"

# package.rb
node['riak']['package']['version']['major'] = "1"
node['riak']['package']['version']['minor'] = "4"
node['riak']['package']['version']['incremental'] = "10"

If you are installing Riak Enterprise with the custom_repository method,
also populate the following attribute with a package name:


Source Installation

The riak::source recipe can be used to install Riak from source. The source installation requires Erlang/OTP R15B01 or later and the build-essential and erlang cookbooks.

Enterprise Installation

To install Riak Enterprise populate the following attribute with a Basho provided key:


If you are installing Riak Enterprise with the custom_repository method,
also populate the following attribute with a package name:


Basic Configuration

Most Riak configuration is for networking, Erlang, and storage backends. The only interesting configuration options outside of those is the filesystem path where ring state files should be stored.

node['riak']['config']['riak_core']['ring_state_dir'] = "/var/lib/riak/ring".to_erl_string


Riak clients communicate with the nodes in the cluster through either the HTTP or Protobufs interfaces, both of which may be used simultaneously. Configuration for each interface includes the IP address and TCP port on which to listen for client connections. The default for the HTTP interface is localhost:8098 and for Protobufs, meaning client connections to any address on the server, TCP port 8087, are accepted. As the default HTTP configuration is inaccessible to other nodes, it must be changed if you want clients to use the HTTP interface.

node['riak']['config']['riak_core']['http'] = [[node['ipaddress'].to_erl_string, 8098].to_erl_tuple]
node['riak']['config']['riak_api']['pb'] = [[node['ipaddress'].to_erl_string, 8087].to_erl_tuple]

Intra-cluster handoff occurs over a dedicated port, which defaults to 8099.

node['riak']['config']['riak_core']['handoff_port'] = 8099

Finally, by default, options are included in the configuration to define the set of ports used for Erlang inter-node communication.

node['riak']['config']['kernel']['inet_dist_listen_min'] = 6000
node['riak']['config']['kernel']['inet_dist_listen_max'] = 7999


A number of Erlang parameters may be configured through the cookbook. The node name and cookie are most important for creating multi-node clusters. The rest of the parameters are primarily for performance tuning, with kernel polling and smp enabled by default. Any available Erlang environment variable may be set with the env vars hash.

node['riak']['args']['-name'] = "riak@#{node['ipaddress']}"
node['riak']['args']['-setcookie'] = "riak"
node['riak']['args']['+K'] = (true | false)
node['riak']['args']['+A'] = 64
node['riak']['args']['+W'] = "w"
node['riak']['args']['-env']['ERL_MAX_PORTS'] = 4096
node['riak']['args']['-env']['ERL_FULLSWEEP_AFTER'] = 0
node['riak']['args']['-env']['ERL_CRASH_DUMP'] = "/var/log/riak/erl_crash.dump"

Storage Backends

Riak requires specification of a storage backend along with various backend storage options, specific to each backend. While Riak supports specification of different backends for different buckets, the Chef cookbook does not yet allow such configurations. The backend options are Bitcask (the default) or LevelDB. The typical configuration options and their defaults are given below.

Changing Storage Backend

Changing Riak's storage backend is accomplished by changing the node['riak']['config']['riak_kv']['storage_backend'] parameter to one of:

  • riak_kv_bitcask_backend for Bitcask
  • riak_kv_eleveldb_backend for eLevelDB
  • riak_kv_multi_backend for Multi Backend

By default, Riak will use Bitcask, with riak_kv_bitcask_backend. To change this to eLevelDB for example:

node['riak']['config']['riak_kv']['storage_backend'] = 'riak_kv_eleveldb_backend'

NOTE: you can override any of the existing storage_backend configurations by including the following in the attributes of a Riak wrapper cookbook of your own creation:

# custom Multi-backend
case node['riak']['config']['riak_kv']['storage_backend']
  when "riak_kv_multi_backend"
    default['riak']['config']['riak_kv']['multi_backend_default'] = "bitcask". to_erl_binary
    bitcask = ["bitcask".to_erl_binary, "riak_kv_bitcask_backend", {"data_root" => "#{node['riak']['data_dir']}/bitcask".to_erl_string, "expiry_secs" => -1}]
    expiring_data = ["expiring_data".to_erl_binary, "riak_kv_bitcask_backend", {"data_root" => "#{node['riak']['data_dir']}/expiring_data".to_erl_string, "expiry_secs" => 5184000}]
    default['riak']['config']['riak_kv']['multi_backend'] = [bitcask.to_erl_tuple, expiring_data.to_erl_tuple]


Bitcask is an Erlang application that provides an API for storing and retrieving key/value data into a log-structured hash table that provides very fast access.

node['riak']['config']['bitcask']['data_root'] = "/var/lib/riak/bitcask".to_erl_string
node['riak']['config']['bitcask']['max_file_size'] = 2147483648
node['riak']['config']['bitcask']['open_timeout'] = 4
node['riak']['config']['bitcask']['sync_strategy'] = "none"
node['riak']['config']['bitcask']['frag_merge_trigger'] = 60
node['riak']['config']['bitcask']['dead_bytes_merge_trigger'] = 536870912
node['riak']['config']['bitcask']['frag_threshold'] = 40
node['riak']['config']['bitcask']['dead_bytes_threshold'] = 134217728
node['riak']['config']['bitcask']['small_file_threshold'] = 10485760
node['riak']['config']['bitcask']['expiry_secs'] = -1


eLevelDB is an Erlang application that encapsulates LevelDB, an open source on-disk key-value store written by Google Fellows Jeffrey Dean and Sanjay Ghemawat. LevelDB's storage architecture is more like BigTable's memtable/sstable model than it is like Bitcask.

node['riak']['config']['eleveldb']['data_root'] = "/var/lib/riak/leveldb".to_erl_string


Lager is the logging framework used within Riak. It can also be used with erlang/OTP.

node['riak']['config']['lager']['crash_log'] = "/var/log/riak/crash.log".to_erl_string
node['riak']['config']['lager']['crash_log_date'] = "$D0".to_erl_string
node['riak']['config']['lager']['crash_log_msg_size']  = 65536
node['riak']['config']['lager']['crash_log_size'] = 10485760
node['riak']['config']['lager']['error_logger_redirect'] = true
node['riak']['config']['lager']['handlers']['lager_file_backend']['lager_error_log'] =  ["/var/log/riak/error.log".to_erl_string, "error", 10485760, "$D0".to_erl_string, 5].to_erl_tuple
node['riak']['config']['lager']['handlers']['lager_file_backend']['lager_console_log'] = ["/var/log/riak/console.log".to_erl_string, "info", 10485760, "$D0".to_erl_string, 5].to_erl_tuple


Sysmon monitors riaks gc process and logs relevant information to the status of garbage collection.

node['riak']['config']['sysmon']['process_limit'] = 30
node['riak']['config']['sysmon']['port_limit'] = 30
node['riak']['config']['sysmon']['gc_ms_limit'] = 50 #if gc takes longer than 50ms. Spam the log.
node['riak']['config']['sysmon']['heap_word_limit'] = 10485760

Index Merge

node['riak']['config']['merge_index']['data_root'] = "/var/lib/riak/merge_index".to_erl_string
node['riak']['config']['merge_index']['buffer_rollover_size'] = 1048576
node['riak']['config']['merge_index']['max_compact_segments'] = 20


The Chef 10.10 release has a bug where changes to a file resource does not properly notify restart. This is fixed in Chef 10.12.


  • Fix and update tests
  • Add digitalocean to
  • Add source build suit to



  • Update Riak CS default version to 1.5.1


  • Riak 1.4.10 is now the default.
  • Remove Ubuntu 13.04 support (EOL).
  • Add Ubuntu 13.10 support
  • Add Ubuntu 14.04 support


  • Increase pessimistic version constraint on build-essential.
  • Restrict version constraint on sysctl due to breaking changes.


  • Increase default ulimit from 4096 to 65536.


  • Ensure SNMP directory is created when customer data_dir is provided.


  • Fix invalid default Multi backend definitions.


  • Revert errant change of Riak node name from FQDN to IP address.


  • Make default for cs_version be 1.4.5
  • Add support for Ubuntu 13.04 (Raring).
  • Add support for Amazon Linux (2014.03).


  • Ensure /etc/default/riak is regenerated when open file limits change.
  • Ensure Riak data directory exists and is owned by the Riak user.
  • Make all cookbook dependency versions explicit.


  • Updated yum dependency constraint.


  • Riak 1.4.8 is now the default.


  • Riak 1.4.7 is now the default.


  • Add a constraint to yum cookbook dependency so that breaking changes in v3.0 are mitigated.
  • Updated Gemfile to include integration test dependencies.


  • Riak 1.4.6 is now the default.
  • Make use of vagrantfile_erb setting of kitchen-vagrant.
  • Added kernel and network tuning via sysctl.


  • Removed Recipe Tester.
  • Bumped Chef to version 11.8.0 for Test Kitchen.
  • Make default for cs_version be 1.4.3


  • Added a recipe for installing Riak through a custom package repository.


  • Made Test Kitchen run faster by enabling the vagrant-cachier plugin through the kitchen-vagrant driver.
  • Make default for cs_version be 1.4.1


  • Riak 1.4.2 is now the default.
  • Fixed the remote_file resource for Enterprise packages so that it utilizes a checksum.


  • Add a default cluster_mgr attribute.
  • Add allow_mult override when the riak_cs_kv_multi_backend is chosen.


  • Riak 1.4.1 is now the default.
  • Fixed Debian support.
  • Added Debian Wheezy to Test Kitchen.


  • Fixed package installation so that it respects version numbers.
  • Added Test Kitchen support for CentOS 5.9.
  • Fixed Protocol Buffers interface configuration changes between Riak 1.3 and 1.4.


  • Riak 1.4.0 is the default.
  • Debian init scripts now use start-stop-daemon for start. This caused an issue with the way we were handling file descriptor limits for Debian. Now the init script sources /etc/default/riak, which contains the appropriate ulimit call.
  • Added new options and defaults to vm.args and app.config attributes.
  • Test Kitchen requires version 2.2.4 or greater of the yum cookbook because earlier versions contained a bad test stub.

Foodcritic Metric

2.4.17 failed this metric

FC007: Ensure recipe dependencies are reflected in cookbook metadata: /tmp/cook/ce736255bb27244fec73a299/riak/recipes/monit.rb:3
FC024: Consider adding platform equivalents: /tmp/cook/ce736255bb27244fec73a299/riak/recipes/package.rb:27