cookbook 'riak', '= 2.4.21'
riak
(51) Versions
2.4.21
-
-
3.1.4
-
3.1.3
-
3.1.2
-
3.1.1
-
3.1.0
-
3.0.2
-
3.0.1
-
3.0.0
-
2.4.21
-
2.4.20
-
2.4.19
-
2.4.18
-
2.4.17
-
2.4.16
-
2.4.15
-
2.4.14
-
2.4.13
-
2.4.12
-
2.4.11
-
2.4.10
-
2.4.9
-
2.4.8
-
2.4.7
-
2.4.6
-
2.4.5
-
2.4.4
-
2.4.3
-
2.4.2
-
2.4.1
-
2.4.0
-
2.3.4
-
2.3.3
-
2.3.2
-
2.2.0
-
2.0.1
-
2.0.0
-
1.3.0
-
1.2.1
-
1.1.0
-
1.0.3
-
1.0.2
-
0.14.5
-
0.14.4
-
0.14.3
-
0.14.2
-
0.14.1
-
0.14.0
-
0.12.1
-
0.12.0
-
0.11.0
-
0.1.0
Follow39
- 3.1.4
- 3.1.3
- 3.1.2
- 3.1.1
- 3.1.0
- 3.0.2
- 3.0.1
- 3.0.0
- 2.4.21
- 2.4.20
- 2.4.19
- 2.4.18
- 2.4.17
- 2.4.16
- 2.4.15
- 2.4.14
- 2.4.13
- 2.4.12
- 2.4.11
- 2.4.10
- 2.4.9
- 2.4.8
- 2.4.7
- 2.4.6
- 2.4.5
- 2.4.4
- 2.4.3
- 2.4.2
- 2.4.1
- 2.4.0
- 2.3.4
- 2.3.3
- 2.3.2
- 2.2.0
- 2.0.1
- 2.0.0
- 1.3.0
- 1.2.1
- 1.1.0
- 1.0.3
- 1.0.2
- 0.14.5
- 0.14.4
- 0.14.3
- 0.14.2
- 0.14.1
- 0.14.0
- 0.12.1
- 0.12.0
- 0.11.0
- 0.1.0
Installs and configures Riak distributed data store
cookbook 'riak', '= 2.4.21', :supermarket
knife supermarket install riak
knife supermarket download riak
Riak Cookbook
Overview
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'] = "12"
If you are installing Riak Enterprise with the custom_repository
method,
also populate the following attribute with a package name:
node['riak']['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:
node['riak']['package']['enterprise_key']
If you are installing Riak Enterprise with the custom_repository
method,
also populate the following attribute with a package name:
node['riak']['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
Networking
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 0.0.0.0:8087
, 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
Erlang
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] end
Bitcask
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
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
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
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
Notes
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.
Dependent cookbooks
apt ~> 2.3.8 |
build-essential ~> 2.0.2 |
erlang ~> 1.5.0 |
git ~> 3.0 |
sysctl < 0.5.0 |
ulimit ~> 0.3.2 |
yum ~> 3.4 |
yum-epel ~> 0.3 |
Contingent cookbooks
v2.4.21
- Update Riak CS default version to 1.5.4
v2.4.20
- Update Riak CS default version to 1.5.3
- Update Gemfile deps
v2.4.19
- Riak
1.4.12
is now the default
v2.4.18
- Update Riak CS default version to 1.5.2
v2.4.17
- Fix and update tests
- Add digitalocean to .kitchen.cloud.yml
- Add source build suit to .kitchen.cloud.yml
v2.4.16
- If fqdn isn't valid, use ipaddress for vm.args -name
- Drop 13.10 support (EOL)
- Drop minitest for serverspec
- Update yum dependency which fixes https://github.com/opscode-cookbooks/yum/issues/99
v2.4.15:
- Update Riak CS default version to 1.5.1
v2.4.14:
- Riak
1.4.10
is now the default. - Remove Ubuntu 13.04 support (EOL).
- Add Ubuntu 13.10 support
- Add Ubuntu 14.04 support
v2.4.13:
- Increase pessimistic version constraint on
build-essential
. - Restrict version constraint on
sysctl
due to breaking changes.
v2.4.12:
- Increase default
ulimit
from4096
to65536
.
v2.4.11:
- Ensure SNMP directory is created when customer
data_dir
is provided.
v2.4.10:
- Fix invalid default Multi backend definitions.
v2.4.9:
- Revert errant change of Riak node name from FQDN to IP address.
v2.4.8:
- Make default for
cs_version
be1.4.5
- Add support for Ubuntu 13.04 (Raring).
- Add support for Amazon Linux (2014.03).
v2.4.7:
- 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.
v2.4.6:
- Updated yum dependency constraint.
v2.4.5:
- Riak
1.4.8
is now the default.
v2.4.4:
- Riak
1.4.7
is now the default.
v2.4.3:
- Add a constraint to
yum
cookbook dependency so that breaking changes in v3.0 are mitigated. - Updated Gemfile to include integration test dependencies.
v2.4.2:
- Riak
1.4.6
is now the default. - Make use of
vagrantfile_erb
setting of kitchen-vagrant. - Added kernel and network tuning via sysctl.
v2.4.1:
- Removed Recipe Tester.
- Bumped Chef to version
11.8.0
for Test Kitchen. - Make default for
cs_version
be1.4.3
v2.4.0:
- Added a recipe for installing Riak through a custom package repository.
v2.3.4:
- Made Test Kitchen run faster by enabling the
vagrant-cachier
plugin through thekitchen-vagrant
driver. - Make default for
cs_version
be1.4.1
v2.3.3:
- Riak
1.4.2
is now the default. - Fixed the
remote_file
resource for Enterprise packages so that it utilizes a checksum.
v2.3.2:
- Add a default
cluster_mgr
attribute. - Add
allow_mult
override when theriak_cs_kv_multi_backend
is chosen.
v2.3.1:
- Riak
1.4.1
is now the default. - Fixed Debian support.
- Added Debian Wheezy to Test Kitchen.
v2.3.0:
- 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.
v2.2.0:
- Riak
1.4.0
is the default. - Debian init scripts now use
start-stop-daemon
forstart
. 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 appropriateulimit
call. - Added new options and defaults to
vm.args
andapp.config
attributes. - Test Kitchen requires version
2.2.4
or greater of theyum
cookbook because earlier versions contained a bad test stub.
Foodcritic Metric
2.4.21 failed this metric
FC024: Consider adding platform equivalents: /tmp/cook/cc0f04ac311ba705f83142d4/riak/recipes/enterprise_package.rb:37
FC024: Consider adding platform equivalents: /tmp/cook/cc0f04ac311ba705f83142d4/riak/recipes/package.rb:27
FC024: Consider adding platform equivalents: /tmp/cook/cc0f04ac311ba705f83142d4/riak/recipes/package.rb:70
FC031: Cookbook without metadata file: /tmp/cook/cc0f04ac311ba705f83142d4/riak/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/cc0f04ac311ba705f83142d4/riak/metadata.rb:1
2.4.21 failed this metric
FC024: Consider adding platform equivalents: /tmp/cook/cc0f04ac311ba705f83142d4/riak/recipes/package.rb:27
FC024: Consider adding platform equivalents: /tmp/cook/cc0f04ac311ba705f83142d4/riak/recipes/package.rb:70
FC031: Cookbook without metadata file: /tmp/cook/cc0f04ac311ba705f83142d4/riak/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/cc0f04ac311ba705f83142d4/riak/metadata.rb:1