eycloud-recipe-redis 0.1.5
Sign up to get free protection for your applications and to get access to all the features.
- data/.gitignore +4 -0
- data/ChangeLog.md +0 -0
- data/Gemfile +3 -0
- data/README.md +19 -0
- data/Rakefile +2 -0
- data/attributes/recipe.rb +16 -0
- data/eycloud-recipe-redis.gemspec +22 -0
- data/libraries/find_redis_instance.rb +20 -0
- data/metadata.json +13 -0
- data/metadata.rb +7 -0
- data/recipes/configure.rb +66 -0
- data/recipes/default.rb +8 -0
- data/recipes/install.rb +15 -0
- data/recipes/restart.rb +9 -0
- data/redis/recipes/default.rb +5 -0
- data/templates/default/redis.conf.erb +470 -0
- data/templates/default/redis.erb +13 -0
- data/templates/default/redis.monitrc.erb +5 -0
- metadata +91 -0
data/.gitignore
ADDED
data/ChangeLog.md
ADDED
File without changes
|
data/Gemfile
ADDED
data/README.md
ADDED
@@ -0,0 +1,19 @@
|
|
1
|
+
# Redis recipe for EY Cloud
|
2
|
+
|
3
|
+
DESCRIPTION HERE
|
4
|
+
|
5
|
+
## Installation
|
6
|
+
|
7
|
+
INSTALLATION HERE
|
8
|
+
|
9
|
+
## Contributing
|
10
|
+
|
11
|
+
1. Fork it
|
12
|
+
2. Create your feature branch (`git checkout -b my-new-feature`)
|
13
|
+
3. Commit your changes (`git commit -am 'Added some feature'`)
|
14
|
+
4. Push to the branch (`git push origin my-new-feature`)
|
15
|
+
5. Create new Pull Request
|
16
|
+
|
17
|
+
## License
|
18
|
+
|
19
|
+
MIT LICENSE
|
data/Rakefile
ADDED
@@ -0,0 +1,16 @@
|
|
1
|
+
redis \
|
2
|
+
:version => "2.4.6",
|
3
|
+
:bindport => "6379",
|
4
|
+
:unixsocket => "/tmp/redis.sock",
|
5
|
+
:basename => "redis_state.rdb",
|
6
|
+
:basedir => "/db/redis",
|
7
|
+
:pidfile => "/var/run/redis.pid",
|
8
|
+
:loglevel => "notice",
|
9
|
+
:logfile => "/db/redis/redis.log",
|
10
|
+
:conigfile => "/etc/redis/redis.conf",
|
11
|
+
:timeout => 300000,
|
12
|
+
:saveperiod => ["90 1","300 10","60 10000"],
|
13
|
+
:databases => 16,
|
14
|
+
:rdbcompression => "yes",
|
15
|
+
:user => "root",
|
16
|
+
:group => "root"
|
@@ -0,0 +1,22 @@
|
|
1
|
+
# -*- encoding: utf-8 -*-
|
2
|
+
$:.push File.expand_path("../lib", __FILE__)
|
3
|
+
|
4
|
+
version = "0.1.5" # TODO get from metadata.json or .rb
|
5
|
+
|
6
|
+
Gem::Specification.new do |s|
|
7
|
+
s.name = "eycloud-recipe-redis"
|
8
|
+
s.version = version
|
9
|
+
s.authors = ["Dr Nic Williams"]
|
10
|
+
s.email = ["drnicwilliams@gmail.com"]
|
11
|
+
s.homepage = ""
|
12
|
+
s.summary = %q{Redis recipe for EY Cloud} # TODO from metadata
|
13
|
+
s.description = %q{Redis recipe for EY Cloud} # TODO from metadata long_description
|
14
|
+
|
15
|
+
s.files = `git ls-files`.split("\n")
|
16
|
+
s.test_files = `git ls-files -- {test,spec,features}/*`.split("\n")
|
17
|
+
s.executables = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
|
18
|
+
s.require_paths = ["lib"]
|
19
|
+
|
20
|
+
s.add_dependency("eycloud-helper-emerge")
|
21
|
+
s.add_development_dependency("rake")
|
22
|
+
end
|
@@ -0,0 +1,20 @@
|
|
1
|
+
class Chef
|
2
|
+
class Recipe
|
3
|
+
# Return which instance is to have redis installed on it
|
4
|
+
# This is determind as follows:
|
5
|
+
# 1. A utility named 'redis'
|
6
|
+
# 2. The db_master
|
7
|
+
# 3. The solo
|
8
|
+
# Returns hash of instance data, including { "id" => "i-123456", }
|
9
|
+
def redis_instance
|
10
|
+
@redis_instance ||= node[:engineyard][:environment][:instances].find {|x| x[:name] == "redis"} ||
|
11
|
+
node[:engineyard][:environment][:db_master] ||
|
12
|
+
node[:engineyard][:environment][:instances].find { |x| x[:role] == "solo" }
|
13
|
+
end
|
14
|
+
|
15
|
+
# Is the instance (or this current instance if no argument passed) the redis instance?
|
16
|
+
def redis_instance?(instance_id = node["engineyard"]["this"])
|
17
|
+
redis_instance["id"] == instance_id
|
18
|
+
end
|
19
|
+
end
|
20
|
+
end
|
data/metadata.json
ADDED
@@ -0,0 +1,13 @@
|
|
1
|
+
{
|
2
|
+
"name": "redis",
|
3
|
+
"description": "Redis recipe for EY Cloud",
|
4
|
+
"long_description": "",
|
5
|
+
"license": "MIT",
|
6
|
+
"maintainer": "Dr Nic Williams",
|
7
|
+
"maintainer_email": "drnicwilliams@gmail.com",
|
8
|
+
"version": "0.1.5",
|
9
|
+
"attributes": {
|
10
|
+
},
|
11
|
+
"dependencies": {
|
12
|
+
}
|
13
|
+
}
|
data/metadata.rb
ADDED
@@ -0,0 +1,66 @@
|
|
1
|
+
#
|
2
|
+
# Cookbook Name:: redis
|
3
|
+
# Recipe:: configure
|
4
|
+
#
|
5
|
+
|
6
|
+
if redis_instance?
|
7
|
+
|
8
|
+
directory "#{node[:redis][:basedir]}" do
|
9
|
+
owner 'redis'
|
10
|
+
group 'redis'
|
11
|
+
mode 0755
|
12
|
+
recursive true
|
13
|
+
end
|
14
|
+
|
15
|
+
directory "/etc/redis" do
|
16
|
+
action :create
|
17
|
+
end
|
18
|
+
|
19
|
+
managed_template "/etc/conf.d/redis" do
|
20
|
+
owner 'root'
|
21
|
+
group 'root'
|
22
|
+
mode 0644
|
23
|
+
source 'redis.erb'
|
24
|
+
variables({
|
25
|
+
:configuration_file => node[:redis][:configfile],
|
26
|
+
:user => node[:redis][:user],
|
27
|
+
:grup => node[:redis][:group],
|
28
|
+
})
|
29
|
+
end
|
30
|
+
|
31
|
+
managed_template "/etc/redis/redis.conf" do
|
32
|
+
owner 'root'
|
33
|
+
group 'root'
|
34
|
+
mode 0644
|
35
|
+
source "redis.conf.erb"
|
36
|
+
variables({
|
37
|
+
:pidfile => node[:redis][:pidfile],
|
38
|
+
:basedir => node[:redis][:basedir],
|
39
|
+
:basename => node[:redis][:basename],
|
40
|
+
:logfile => node[:redis][:logfile],
|
41
|
+
:loglevel => node[:redis][:loglevel],
|
42
|
+
:port => node[:redis][:bindport],
|
43
|
+
:unixsocket => node[:redis][:unixsocket],
|
44
|
+
:saveperiod => node[:redis][:saveperiod],
|
45
|
+
:timeout => node[:redis][:timeout],
|
46
|
+
:databases => node[:redis][:databases],
|
47
|
+
:rdbcompression => node[:redis][:rdbcompression],
|
48
|
+
})
|
49
|
+
end
|
50
|
+
|
51
|
+
template "/data/monit.d/redis.monitrc" do
|
52
|
+
source 'redis.monitrc.erb'
|
53
|
+
owner 'root'
|
54
|
+
group 'root'
|
55
|
+
mode 0644
|
56
|
+
backup 0
|
57
|
+
|
58
|
+
variables(
|
59
|
+
:port => node[:redis][:port],
|
60
|
+
:pidfile => node[:redis][:pidfile],
|
61
|
+
:configfile => "/etc/redis/redis.conf"
|
62
|
+
)
|
63
|
+
|
64
|
+
# notifies :run, resources(:execute => "restart-monit")
|
65
|
+
end
|
66
|
+
end
|
data/recipes/default.rb
ADDED
data/recipes/install.rb
ADDED
data/recipes/restart.rb
ADDED
@@ -0,0 +1,470 @@
|
|
1
|
+
# Redis configuration file example
|
2
|
+
|
3
|
+
# Note on units: when memory size is needed, it is possible to specifiy
|
4
|
+
# it in the usual form of 1k 5GB 4M and so forth:
|
5
|
+
#
|
6
|
+
# 1k => 1000 bytes
|
7
|
+
# 1kb => 1024 bytes
|
8
|
+
# 1m => 1000000 bytes
|
9
|
+
# 1mb => 1024*1024 bytes
|
10
|
+
# 1g => 1000000000 bytes
|
11
|
+
# 1gb => 1024*1024*1024 bytes
|
12
|
+
#
|
13
|
+
# units are case insensitive so 1GB 1Gb 1gB are all the same.
|
14
|
+
|
15
|
+
# By default Redis does not run as a daemon. Use 'yes' if you need it.
|
16
|
+
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
|
17
|
+
daemonize yes
|
18
|
+
|
19
|
+
# When running daemonized, Redis writes a pid file in /var/run/redis.pid by
|
20
|
+
# default. You can specify a custom pid file location here.
|
21
|
+
pidfile <%= @pidfile %>
|
22
|
+
|
23
|
+
# Accept connections on the specified port, default is 6379.
|
24
|
+
# If port 0 is specified Redis will not listen on a TCP socket.
|
25
|
+
port <%= @port %>
|
26
|
+
|
27
|
+
# If you want you can bind a single interface, if the bind option is not
|
28
|
+
# specified all the interfaces will listen for incoming connections.
|
29
|
+
#
|
30
|
+
bind 0.0.0.0
|
31
|
+
|
32
|
+
# Specify the path for the unix socket that will be used to listen for
|
33
|
+
# incoming connections. There is no default, so Redis will not listen
|
34
|
+
# on a unix socket when not specified.
|
35
|
+
#
|
36
|
+
unixsocket <%= @unixsocket %>
|
37
|
+
unixsocketperm 755
|
38
|
+
|
39
|
+
# Close the connection after a client is idle for N seconds (0 to disable)
|
40
|
+
timeout <%= @timeout %>
|
41
|
+
|
42
|
+
# Set server verbosity to 'debug'
|
43
|
+
# it can be one of:
|
44
|
+
# debug (a lot of information, useful for development/testing)
|
45
|
+
# verbose (many rarely useful info, but not a mess like the debug level)
|
46
|
+
# notice (moderately verbose, what you want in production probably)
|
47
|
+
# warning (only very important / critical messages are logged)
|
48
|
+
loglevel <%= @loglevel %>
|
49
|
+
|
50
|
+
# Specify the log file name. Also 'stdout' can be used to force
|
51
|
+
# Redis to log on the standard output. Note that if you use standard
|
52
|
+
# output for logging but daemonize, logs will be sent to /dev/null
|
53
|
+
logfile <%= @logfile %>
|
54
|
+
|
55
|
+
# To enable logging to the system logger, just set 'syslog-enabled' to yes,
|
56
|
+
# and optionally update the other syslog parameters to suit your needs.
|
57
|
+
# syslog-enabled no
|
58
|
+
|
59
|
+
# Specify the syslog identity.
|
60
|
+
# syslog-ident redis
|
61
|
+
|
62
|
+
# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
|
63
|
+
# syslog-facility local0
|
64
|
+
|
65
|
+
# Set the number of databases. The default database is DB 0, you can select
|
66
|
+
# a different one on a per-connection basis using SELECT <dbid> where
|
67
|
+
# dbid is a number between 0 and 'databases'-1
|
68
|
+
databases <%= @databases %>
|
69
|
+
|
70
|
+
################################ SNAPSHOTTING #################################
|
71
|
+
#
|
72
|
+
# Save the DB on disk:
|
73
|
+
#
|
74
|
+
# save <seconds> <changes>
|
75
|
+
#
|
76
|
+
# Will save the DB if both the given number of seconds and the given
|
77
|
+
# number of write operations against the DB occurred.
|
78
|
+
#
|
79
|
+
# In the example below the behaviour will be to save:
|
80
|
+
# after 900 sec (15 min) if at least 1 key changed
|
81
|
+
# after 300 sec (5 min) if at least 10 keys changed
|
82
|
+
# after 60 sec if at least 10000 keys changed
|
83
|
+
#
|
84
|
+
# Note: you can disable saving at all commenting all the "save" lines.
|
85
|
+
<% @saveperiod.each do |s| %>
|
86
|
+
save <%= s %>
|
87
|
+
<% end %>
|
88
|
+
|
89
|
+
# Compress string objects using LZF when dump .rdb databases?
|
90
|
+
# For default that's set to 'yes' as it's almost always a win.
|
91
|
+
# If you want to save some CPU in the saving child set it to 'no' but
|
92
|
+
# the dataset will likely be bigger if you have compressible values or keys.
|
93
|
+
rdbcompression <%= @rdbcompression %>
|
94
|
+
|
95
|
+
# The filename where to dump the DB
|
96
|
+
dbfilename <%= @basename %>
|
97
|
+
|
98
|
+
# The working directory.
|
99
|
+
#
|
100
|
+
# The DB will be written inside this directory, with the filename specified
|
101
|
+
# above using the 'dbfilename' configuration directive.
|
102
|
+
#
|
103
|
+
# Also the Append Only File will be created inside this directory.
|
104
|
+
#
|
105
|
+
# Note that you must specify a directory here, not a file name.
|
106
|
+
dir <%= @basedir %>
|
107
|
+
|
108
|
+
################################# REPLICATION #################################
|
109
|
+
|
110
|
+
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
|
111
|
+
# another Redis server. Note that the configuration is local to the slave
|
112
|
+
# so for example it is possible to configure the slave to save the DB with a
|
113
|
+
# different interval, or to listen to another port, and so on.
|
114
|
+
#
|
115
|
+
# slaveof <masterip> <masterport>
|
116
|
+
|
117
|
+
# If the master is password protected (using the "requirepass" configuration
|
118
|
+
# directive below) it is possible to tell the slave to authenticate before
|
119
|
+
# starting the replication synchronization process, otherwise the master will
|
120
|
+
# refuse the slave request.
|
121
|
+
#
|
122
|
+
# masterauth <master-password>
|
123
|
+
|
124
|
+
# When a slave lost the connection with the master, or when the replication
|
125
|
+
# is still in progress, the slave can act in two different ways:
|
126
|
+
#
|
127
|
+
# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
|
128
|
+
# still reply to client requests, possibly with out of data data, or the
|
129
|
+
# data set may just be empty if this is the first synchronization.
|
130
|
+
#
|
131
|
+
# 2) if slave-serve-stale data is set to 'no' the slave will reply with
|
132
|
+
# an error "SYNC with master in progress" to all the kind of commands
|
133
|
+
# but to INFO and SLAVEOF.
|
134
|
+
#
|
135
|
+
slave-serve-stale-data yes
|
136
|
+
|
137
|
+
################################## SECURITY ###################################
|
138
|
+
|
139
|
+
# Require clients to issue AUTH <PASSWORD> before processing any other
|
140
|
+
# commands. This might be useful in environments in which you do not trust
|
141
|
+
# others with access to the host running redis-server.
|
142
|
+
#
|
143
|
+
# This should stay commented out for backward compatibility and because most
|
144
|
+
# people do not need auth (e.g. they run their own servers).
|
145
|
+
#
|
146
|
+
# Warning: since Redis is pretty fast an outside user can try up to
|
147
|
+
# 150k passwords per second against a good box. This means that you should
|
148
|
+
# use a very strong password otherwise it will be very easy to break.
|
149
|
+
#
|
150
|
+
# requirepass foobared
|
151
|
+
|
152
|
+
# Command renaming.
|
153
|
+
#
|
154
|
+
# It is possilbe to change the name of dangerous commands in a shared
|
155
|
+
# environment. For instance the CONFIG command may be renamed into something
|
156
|
+
# of hard to guess so that it will be still available for internal-use
|
157
|
+
# tools but not available for general clients.
|
158
|
+
#
|
159
|
+
# Example:
|
160
|
+
#
|
161
|
+
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
|
162
|
+
#
|
163
|
+
# It is also possilbe to completely kill a command renaming it into
|
164
|
+
# an empty string:
|
165
|
+
#
|
166
|
+
# rename-command CONFIG ""
|
167
|
+
|
168
|
+
################################### LIMITS ####################################
|
169
|
+
|
170
|
+
# Set the max number of connected clients at the same time. By default there
|
171
|
+
# is no limit, and it's up to the number of file descriptors the Redis process
|
172
|
+
# is able to open. The special value '0' means no limits.
|
173
|
+
# Once the limit is reached Redis will close all the new connections sending
|
174
|
+
# an error 'max number of clients reached'.
|
175
|
+
#
|
176
|
+
# maxclients 128
|
177
|
+
|
178
|
+
# Don't use more memory than the specified amount of bytes.
|
179
|
+
# When the memory limit is reached Redis will try to remove keys with an
|
180
|
+
# EXPIRE set. It will try to start freeing keys that are going to expire
|
181
|
+
# in little time and preserve keys with a longer time to live.
|
182
|
+
# Redis will also try to remove objects from free lists if possible.
|
183
|
+
#
|
184
|
+
# If all this fails, Redis will start to reply with errors to commands
|
185
|
+
# that will use more memory, like SET, LPUSH, and so on, and will continue
|
186
|
+
# to reply to most read-only commands like GET.
|
187
|
+
#
|
188
|
+
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
|
189
|
+
# 'state' server or cache, not as a real DB. When Redis is used as a real
|
190
|
+
# database the memory usage will grow over the weeks, it will be obvious if
|
191
|
+
# it is going to use too much memory in the long run, and you'll have the time
|
192
|
+
# to upgrade. With maxmemory after the limit is reached you'll start to get
|
193
|
+
# errors for write operations, and this may even lead to DB inconsistency.
|
194
|
+
#
|
195
|
+
# maxmemory <bytes>
|
196
|
+
|
197
|
+
# MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
|
198
|
+
# is reached? You can select among five behavior:
|
199
|
+
#
|
200
|
+
# volatile-lru -> remove the key with an expire set using an LRU algorithm
|
201
|
+
# allkeys-lru -> remove any key accordingly to the LRU algorithm
|
202
|
+
# volatile-random -> remove a random key with an expire set
|
203
|
+
# allkeys->random -> remove a random key, any key
|
204
|
+
# volatile-ttl -> remove the key with the nearest expire time (minor TTL)
|
205
|
+
# noeviction -> don't expire at all, just return an error on write operations
|
206
|
+
#
|
207
|
+
# Note: with all the kind of policies, Redis will return an error on write
|
208
|
+
# operations, when there are not suitable keys for eviction.
|
209
|
+
#
|
210
|
+
# At the date of writing this commands are: set setnx setex append
|
211
|
+
# incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
|
212
|
+
# sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
|
213
|
+
# zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
|
214
|
+
# getset mset msetnx exec sort
|
215
|
+
#
|
216
|
+
# The default is:
|
217
|
+
#
|
218
|
+
# maxmemory-policy volatile-lru
|
219
|
+
|
220
|
+
# LRU and minimal TTL algorithms are not precise algorithms but approximated
|
221
|
+
# algorithms (in order to save memory), so you can select as well the sample
|
222
|
+
# size to check. For instance for default Redis will check three keys and
|
223
|
+
# pick the one that was used less recently, you can change the sample size
|
224
|
+
# using the following configuration directive.
|
225
|
+
#
|
226
|
+
# maxmemory-samples 3
|
227
|
+
|
228
|
+
############################## APPEND ONLY MODE ###############################
|
229
|
+
|
230
|
+
# By default Redis asynchronously dumps the dataset on disk. If you can live
|
231
|
+
# with the idea that the latest records will be lost if something like a crash
|
232
|
+
# happens this is the preferred way to run Redis. If instead you care a lot
|
233
|
+
# about your data and don't want to that a single record can get lost you should
|
234
|
+
# enable the append only mode: when this mode is enabled Redis will append
|
235
|
+
# every write operation received in the file appendonly.aof. This file will
|
236
|
+
# be read on startup in order to rebuild the full dataset in memory.
|
237
|
+
#
|
238
|
+
# Note that you can have both the async dumps and the append only file if you
|
239
|
+
# like (you have to comment the "save" statements above to disable the dumps).
|
240
|
+
# Still if append only mode is enabled Redis will load the data from the
|
241
|
+
# log file at startup ignoring the dump.rdb file.
|
242
|
+
#
|
243
|
+
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
|
244
|
+
# log file in background when it gets too big.
|
245
|
+
|
246
|
+
appendonly no
|
247
|
+
|
248
|
+
# The name of the append only file (default: "appendonly.aof")
|
249
|
+
# appendfilename appendonly.aof
|
250
|
+
|
251
|
+
# The fsync() call tells the Operating System to actually write data on disk
|
252
|
+
# instead to wait for more data in the output buffer. Some OS will really flush
|
253
|
+
# data on disk, some other OS will just try to do it ASAP.
|
254
|
+
#
|
255
|
+
# Redis supports three different modes:
|
256
|
+
#
|
257
|
+
# no: don't fsync, just let the OS flush the data when it wants. Faster.
|
258
|
+
# always: fsync after every write to the append only log . Slow, Safest.
|
259
|
+
# everysec: fsync only if one second passed since the last fsync. Compromise.
|
260
|
+
#
|
261
|
+
# The default is "everysec" that's usually the right compromise between
|
262
|
+
# speed and data safety. It's up to you to understand if you can relax this to
|
263
|
+
# "no" that will will let the operating system flush the output buffer when
|
264
|
+
# it wants, for better performances (but if you can live with the idea of
|
265
|
+
# some data loss consider the default persistence mode that's snapshotting),
|
266
|
+
# or on the contrary, use "always" that's very slow but a bit safer than
|
267
|
+
# everysec.
|
268
|
+
#
|
269
|
+
# If unsure, use "everysec".
|
270
|
+
|
271
|
+
# appendfsync always
|
272
|
+
appendfsync everysec
|
273
|
+
# appendfsync no
|
274
|
+
|
275
|
+
# When the AOF fsync policy is set to always or everysec, and a background
|
276
|
+
# saving process (a background save or AOF log background rewriting) is
|
277
|
+
# performing a lot of I/O against the disk, in some Linux configurations
|
278
|
+
# Redis may block too long on the fsync() call. Note that there is no fix for
|
279
|
+
# this currently, as even performing fsync in a different thread will block
|
280
|
+
# our synchronous write(2) call.
|
281
|
+
#
|
282
|
+
# In order to mitigate this problem it's possible to use the following option
|
283
|
+
# that will prevent fsync() from being called in the main process while a
|
284
|
+
# BGSAVE or BGREWRITEAOF is in progress.
|
285
|
+
#
|
286
|
+
# This means that while another child is saving the durability of Redis is
|
287
|
+
# the same as "appendfsync none", that in pratical terms means that it is
|
288
|
+
# possible to lost up to 30 seconds of log in the worst scenario (with the
|
289
|
+
# default Linux settings).
|
290
|
+
#
|
291
|
+
# If you have latency problems turn this to "yes". Otherwise leave it as
|
292
|
+
# "no" that is the safest pick from the point of view of durability.
|
293
|
+
no-appendfsync-on-rewrite no
|
294
|
+
|
295
|
+
# Automatic rewrite of the append only file.
|
296
|
+
# Redis is able to automatically rewrite the log file implicitly calling
|
297
|
+
# BGREWRITEAOF when the AOF log size will growth by the specified percentage.
|
298
|
+
#
|
299
|
+
# This is how it works: Redis remembers the size of the AOF file after the
|
300
|
+
# latest rewrite (or if no rewrite happened since the restart, the size of
|
301
|
+
# the AOF at startup is used).
|
302
|
+
#
|
303
|
+
# This base size is compared to the current size. If the current size is
|
304
|
+
# bigger than the specified percentage, the rewrite is triggered. Also
|
305
|
+
# you need to specify a minimal size for the AOF file to be rewritten, this
|
306
|
+
# is useful to avoid rewriting the AOF file even if the percentage increase
|
307
|
+
# is reached but it is still pretty small.
|
308
|
+
#
|
309
|
+
# Specify a precentage of zero in order to disable the automatic AOF
|
310
|
+
# rewrite feature.
|
311
|
+
|
312
|
+
auto-aof-rewrite-percentage 100
|
313
|
+
auto-aof-rewrite-min-size 64mb
|
314
|
+
|
315
|
+
################################## SLOW LOG ###################################
|
316
|
+
|
317
|
+
# The Redis Slow Log is a system to log queries that exceeded a specified
|
318
|
+
# execution time. The execution time does not include the I/O operations
|
319
|
+
# like talking with the client, sending the reply and so forth,
|
320
|
+
# but just the time needed to actually execute the command (this is the only
|
321
|
+
# stage of command execution where the thread is blocked and can not serve
|
322
|
+
# other requests in the meantime).
|
323
|
+
#
|
324
|
+
# You can configure the slow log with two parameters: one tells Redis
|
325
|
+
# what is the execution time, in microseconds, to exceed in order for the
|
326
|
+
# command to get logged, and the other parameter is the length of the
|
327
|
+
# slow log. When a new command is logged the oldest one is removed from the
|
328
|
+
# queue of logged commands.
|
329
|
+
|
330
|
+
# The following time is expressed in microseconds, so 1000000 is equivalent
|
331
|
+
# to one second. Note that a negative number disables the slow log, while
|
332
|
+
# a value of zero forces the logging of every command.
|
333
|
+
slowlog-log-slower-than 10000
|
334
|
+
|
335
|
+
# There is no limit to this length. Just be aware that it will consume memory.
|
336
|
+
# You can reclaim memory used by the slow log with SLOWLOG RESET.
|
337
|
+
slowlog-max-len 1024
|
338
|
+
|
339
|
+
################################ VIRTUAL MEMORY ###############################
|
340
|
+
|
341
|
+
### WARNING! Virtual Memory is deprecated in Redis 2.4
|
342
|
+
### The use of Virtual Memory is strongly discouraged.
|
343
|
+
|
344
|
+
# Virtual Memory allows Redis to work with datasets bigger than the actual
|
345
|
+
# amount of RAM needed to hold the whole dataset in memory.
|
346
|
+
# In order to do so very used keys are taken in memory while the other keys
|
347
|
+
# are swapped into a swap file, similarly to what operating systems do
|
348
|
+
# with memory pages.
|
349
|
+
#
|
350
|
+
# To enable VM just set 'vm-enabled' to yes, and set the following three
|
351
|
+
# VM parameters accordingly to your needs.
|
352
|
+
|
353
|
+
vm-enabled no
|
354
|
+
# vm-enabled yes
|
355
|
+
|
356
|
+
# This is the path of the Redis swap file. As you can guess, swap files
|
357
|
+
# can't be shared by different Redis instances, so make sure to use a swap
|
358
|
+
# file for every redis process you are running. Redis will complain if the
|
359
|
+
# swap file is already in use.
|
360
|
+
#
|
361
|
+
# The best kind of storage for the Redis swap file (that's accessed at random)
|
362
|
+
# is a Solid State Disk (SSD).
|
363
|
+
#
|
364
|
+
# *** WARNING *** if you are using a shared hosting the default of putting
|
365
|
+
# the swap file under /tmp is not secure. Create a dir with access granted
|
366
|
+
# only to Redis user and configure Redis to create the swap file there.
|
367
|
+
vm-swap-file /tmp/redis.swap
|
368
|
+
|
369
|
+
# vm-max-memory configures the VM to use at max the specified amount of
|
370
|
+
# RAM. Everything that deos not fit will be swapped on disk *if* possible, that
|
371
|
+
# is, if there is still enough contiguous space in the swap file.
|
372
|
+
#
|
373
|
+
# With vm-max-memory 0 the system will swap everything it can. Not a good
|
374
|
+
# default, just specify the max amount of RAM you can in bytes, but it's
|
375
|
+
# better to leave some margin. For instance specify an amount of RAM
|
376
|
+
# that's more or less between 60 and 80% of your free RAM.
|
377
|
+
vm-max-memory 0
|
378
|
+
|
379
|
+
# Redis swap files is split into pages. An object can be saved using multiple
|
380
|
+
# contiguous pages, but pages can't be shared between different objects.
|
381
|
+
# So if your page is too big, small objects swapped out on disk will waste
|
382
|
+
# a lot of space. If you page is too small, there is less space in the swap
|
383
|
+
# file (assuming you configured the same number of total swap file pages).
|
384
|
+
#
|
385
|
+
# If you use a lot of small objects, use a page size of 64 or 32 bytes.
|
386
|
+
# If you use a lot of big objects, use a bigger page size.
|
387
|
+
# If unsure, use the default :)
|
388
|
+
vm-page-size 32
|
389
|
+
|
390
|
+
# Number of total memory pages in the swap file.
|
391
|
+
# Given that the page table (a bitmap of free/used pages) is taken in memory,
|
392
|
+
# every 8 pages on disk will consume 1 byte of RAM.
|
393
|
+
#
|
394
|
+
# The total swap size is vm-page-size * vm-pages
|
395
|
+
#
|
396
|
+
# With the default of 32-bytes memory pages and 134217728 pages Redis will
|
397
|
+
# use a 4 GB swap file, that will use 16 MB of RAM for the page table.
|
398
|
+
#
|
399
|
+
# It's better to use the smallest acceptable value for your application,
|
400
|
+
# but the default is large in order to work in most conditions.
|
401
|
+
vm-pages 134217728
|
402
|
+
|
403
|
+
# Max number of VM I/O threads running at the same time.
|
404
|
+
# This threads are used to read/write data from/to swap file, since they
|
405
|
+
# also encode and decode objects from disk to memory or the reverse, a bigger
|
406
|
+
# number of threads can help with big objects even if they can't help with
|
407
|
+
# I/O itself as the physical device may not be able to couple with many
|
408
|
+
# reads/writes operations at the same time.
|
409
|
+
#
|
410
|
+
# The special value of 0 turn off threaded I/O and enables the blocking
|
411
|
+
# Virtual Memory implementation.
|
412
|
+
vm-max-threads 4
|
413
|
+
|
414
|
+
############################### ADVANCED CONFIG ###############################
|
415
|
+
|
416
|
+
# Hashes are encoded in a special way (much more memory efficient) when they
|
417
|
+
# have at max a given numer of elements, and the biggest element does not
|
418
|
+
# exceed a given threshold. You can configure this limits with the following
|
419
|
+
# configuration directives.
|
420
|
+
hash-max-zipmap-entries 512
|
421
|
+
hash-max-zipmap-value 64
|
422
|
+
|
423
|
+
# Similarly to hashes, small lists are also encoded in a special way in order
|
424
|
+
# to save a lot of space. The special representation is only used when
|
425
|
+
# you are under the following limits:
|
426
|
+
list-max-ziplist-entries 512
|
427
|
+
list-max-ziplist-value 64
|
428
|
+
|
429
|
+
# Sets have a special encoding in just one case: when a set is composed
|
430
|
+
# of just strings that happens to be integers in radix 10 in the range
|
431
|
+
# of 64 bit signed integers.
|
432
|
+
# The following configuration setting sets the limit in the size of the
|
433
|
+
# set in order to use this special memory saving encoding.
|
434
|
+
set-max-intset-entries 512
|
435
|
+
|
436
|
+
# Similarly to hashes and lists, sorted sets are also specially encoded in
|
437
|
+
# order to save a lot of space. This encoding is only used when the length and
|
438
|
+
# elements of a sorted set are below the following limits:
|
439
|
+
zset-max-ziplist-entries 128
|
440
|
+
zset-max-ziplist-value 64
|
441
|
+
|
442
|
+
# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
|
443
|
+
# order to help rehashing the main Redis hash table (the one mapping top-level
|
444
|
+
# keys to values). The hash table implementation redis uses (see dict.c)
|
445
|
+
# performs a lazy rehashing: the more operation you run into an hash table
|
446
|
+
# that is rhashing, the more rehashing "steps" are performed, so if the
|
447
|
+
# server is idle the rehashing is never complete and some more memory is used
|
448
|
+
# by the hash table.
|
449
|
+
#
|
450
|
+
# The default is to use this millisecond 10 times every second in order to
|
451
|
+
# active rehashing the main dictionaries, freeing memory when possible.
|
452
|
+
#
|
453
|
+
# If unsure:
|
454
|
+
# use "activerehashing no" if you have hard latency requirements and it is
|
455
|
+
# not a good thing in your environment that Redis can reply form time to time
|
456
|
+
# to queries with 2 milliseconds delay.
|
457
|
+
#
|
458
|
+
# use "activerehashing yes" if you don't have such hard requirements but
|
459
|
+
# want to free memory asap when possible.
|
460
|
+
activerehashing yes
|
461
|
+
|
462
|
+
################################## INCLUDES ###################################
|
463
|
+
|
464
|
+
# Include one or more other config files here. This is useful if you
|
465
|
+
# have a standard template that goes to all redis server but also need
|
466
|
+
# to customize a few per-server settings. Include files can include
|
467
|
+
# other files, so use this wisely.
|
468
|
+
#
|
469
|
+
# include /path/to/local.conf
|
470
|
+
# include /path/to/other.conf
|
@@ -0,0 +1,13 @@
|
|
1
|
+
# /etc/conf.d/redis: config file for /etc/init.d/redis
|
2
|
+
|
3
|
+
# Location of the Redis server configuration file
|
4
|
+
REDIS_CONF="<%= @configuration_file %>"
|
5
|
+
|
6
|
+
# User Redis server will run as
|
7
|
+
REDIS_USER="<%= @user %>"
|
8
|
+
|
9
|
+
# Group Redis server will run as
|
10
|
+
REDIS_GROUP="<%= @user %>"
|
11
|
+
|
12
|
+
# Pass extra options to Redis server
|
13
|
+
REDIS_EXTRA_OPTS=""
|
metadata
ADDED
@@ -0,0 +1,91 @@
|
|
1
|
+
--- !ruby/object:Gem::Specification
|
2
|
+
name: eycloud-recipe-redis
|
3
|
+
version: !ruby/object:Gem::Version
|
4
|
+
version: 0.1.5
|
5
|
+
prerelease:
|
6
|
+
platform: ruby
|
7
|
+
authors:
|
8
|
+
- Dr Nic Williams
|
9
|
+
autorequire:
|
10
|
+
bindir: bin
|
11
|
+
cert_chain: []
|
12
|
+
date: 2012-03-18 00:00:00.000000000 Z
|
13
|
+
dependencies:
|
14
|
+
- !ruby/object:Gem::Dependency
|
15
|
+
name: eycloud-helper-emerge
|
16
|
+
requirement: &70125509507800 !ruby/object:Gem::Requirement
|
17
|
+
none: false
|
18
|
+
requirements:
|
19
|
+
- - ! '>='
|
20
|
+
- !ruby/object:Gem::Version
|
21
|
+
version: '0'
|
22
|
+
type: :runtime
|
23
|
+
prerelease: false
|
24
|
+
version_requirements: *70125509507800
|
25
|
+
- !ruby/object:Gem::Dependency
|
26
|
+
name: rake
|
27
|
+
requirement: &70125509507020 !ruby/object:Gem::Requirement
|
28
|
+
none: false
|
29
|
+
requirements:
|
30
|
+
- - ! '>='
|
31
|
+
- !ruby/object:Gem::Version
|
32
|
+
version: '0'
|
33
|
+
type: :development
|
34
|
+
prerelease: false
|
35
|
+
version_requirements: *70125509507020
|
36
|
+
description: Redis recipe for EY Cloud
|
37
|
+
email:
|
38
|
+
- drnicwilliams@gmail.com
|
39
|
+
executables: []
|
40
|
+
extensions: []
|
41
|
+
extra_rdoc_files: []
|
42
|
+
files:
|
43
|
+
- .gitignore
|
44
|
+
- ChangeLog.md
|
45
|
+
- Gemfile
|
46
|
+
- README.md
|
47
|
+
- Rakefile
|
48
|
+
- attributes/recipe.rb
|
49
|
+
- eycloud-recipe-redis.gemspec
|
50
|
+
- libraries/find_redis_instance.rb
|
51
|
+
- metadata.json
|
52
|
+
- metadata.rb
|
53
|
+
- recipes/configure.rb
|
54
|
+
- recipes/default.rb
|
55
|
+
- recipes/install.rb
|
56
|
+
- recipes/restart.rb
|
57
|
+
- redis/recipes/default.rb
|
58
|
+
- templates/default/redis.conf.erb
|
59
|
+
- templates/default/redis.erb
|
60
|
+
- templates/default/redis.monitrc.erb
|
61
|
+
homepage: ''
|
62
|
+
licenses: []
|
63
|
+
post_install_message:
|
64
|
+
rdoc_options: []
|
65
|
+
require_paths:
|
66
|
+
- lib
|
67
|
+
required_ruby_version: !ruby/object:Gem::Requirement
|
68
|
+
none: false
|
69
|
+
requirements:
|
70
|
+
- - ! '>='
|
71
|
+
- !ruby/object:Gem::Version
|
72
|
+
version: '0'
|
73
|
+
segments:
|
74
|
+
- 0
|
75
|
+
hash: 4203206076896397544
|
76
|
+
required_rubygems_version: !ruby/object:Gem::Requirement
|
77
|
+
none: false
|
78
|
+
requirements:
|
79
|
+
- - ! '>='
|
80
|
+
- !ruby/object:Gem::Version
|
81
|
+
version: '0'
|
82
|
+
segments:
|
83
|
+
- 0
|
84
|
+
hash: 4203206076896397544
|
85
|
+
requirements: []
|
86
|
+
rubyforge_project:
|
87
|
+
rubygems_version: 1.8.17
|
88
|
+
signing_key:
|
89
|
+
specification_version: 3
|
90
|
+
summary: Redis recipe for EY Cloud
|
91
|
+
test_files: []
|