├── AUTHORS ├── CONTRIBUTING.md ├── LICENSE ├── Makefile ├── README.md ├── go-httpd ├── Dockerfile.legacy ├── Dockerfile.nabla ├── Makefile └── src │ ├── helper │ └── process_args.go │ └── httpd.go ├── node-express ├── Dockerfile.legacy ├── Dockerfile.nabla ├── Makefile └── app │ ├── app.js │ └── package.json ├── node-webrepl ├── Dockerfile.legacy ├── Dockerfile.nabla ├── Makefile └── app │ ├── app.js │ └── package.json ├── python-tornado ├── Dockerfile.legacy ├── Dockerfile.nabla ├── Makefile └── tornado_main.py └── redis-test ├── Dockerfile.legacy ├── Dockerfile.nabla ├── Makefile └── redis.conf /AUTHORS: -------------------------------------------------------------------------------- 1 | Corporate Contributors 2 | ====================== 3 | 4 | Copyright (c) 2018 IBM 5 | 6 | Individual Contributors 7 | ======================= 8 | 9 | Brandon Lum (IBM) 10 | Dan Williams (IBM) 11 | Ricardo Koller (IBM) 12 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | We require all contributions to be signed off on, indicating that the 2 | contributor agrees to the Developer's Certificate of Origin 1.1 3 | [used by Linux][1] and reproduced below: 4 | 5 | > Developer's Certificate of Origin 1.1 6 | > 7 | > By making a contribution to this project, I certify that: 8 | > 9 | > 1. The contribution was created in whole or in part by me and I have 10 | > the right to submit it under the open source license indicated in 11 | > the file; or 12 | > 13 | > 2. The contribution is based upon previous work that, to the best of 14 | > my knowledge, is covered under an appropriate open source license 15 | > and I have the right under that license to submit that work with 16 | > modifications, whether created in whole or in part by me, under 17 | > the same open source license (unless I am permitted to submit 18 | > under a different license), as indicated in the file; or 19 | > 20 | > 3. The contribution was provided directly to me by some other person 21 | > who certified (a), (b) or (c) and I have not modified it. 22 | > 23 | > 4. I understand and agree that this project and the contribution are 24 | > public and that a record of the contribution (including all 25 | > personal information I submit with it, including my sign-off) is 26 | > maintained indefinitely and may be redistributed consistent with 27 | > this project or the open source license(s) involved. 28 | 29 | 30 | [1]: https://github.com/torvalds/linux/blob/master/Documentation/process/submitting-patches.rst 31 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | ISC License 2 | 3 | Copyright (c) 2018 Contributors as noted in the AUTHORS file 4 | 5 | Permission to use, copy, modify, and/or distribute this software 6 | for any purpose with or without fee is hereby granted, provided 7 | that the above copyright notice and this permission notice appear 8 | in all copies. 9 | 10 | THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL 11 | WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED 12 | WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE 13 | AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR 14 | CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS 15 | OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 16 | NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 17 | CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 18 | -------------------------------------------------------------------------------- /Makefile: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2018 Contributors as noted in the AUTHORS file 2 | # 3 | # Permission to use, copy, modify, and/or distribute this software 4 | # for any purpose with or without fee is hereby granted, provided 5 | # that the above copyright notice and this permission notice appear 6 | # in all copies. 7 | # 8 | # THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL 9 | # WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED 10 | # WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE 11 | # AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR 12 | # CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS 13 | # OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 14 | # NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 15 | # CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 16 | 17 | all: 18 | @echo "To build a demo image, run 'make'" 19 | @echo "in the demo's directory." 20 | @echo 21 | @echo "To build all demo images, run 'make world'." 22 | 23 | world: 24 | make -C node-express 25 | make -C node-webrepl 26 | make -C python-tornado 27 | make -C redis-test 28 | 29 | publish: world 30 | sudo docker tag node-express-nabla nablact/node-express-nabla:v0.3 31 | sudo docker tag node-express-legacy nablact/node-express-legacy:v0.3 32 | sudo docker tag node-webrepl-nabla nablact/node-webrepl-nabla:v0.3 33 | sudo docker tag node-webrepl-legacy nablact/node-webrepl-legacy:v0.3 34 | sudo docker tag python-tornado-nabla nablact/python-tornado-nabla:v0.3 35 | sudo docker tag python-tornado-legacy nablact/python-tornado-legacy:v0.3 36 | sudo docker tag redis-test-nabla nablact/redis-test-nabla:v0.3 37 | sudo docker tag redis-test-legacy nablact/redis-test-legacy:v0.3 38 | sudo docker push nablact/node-express-nabla:v0.3 39 | sudo docker push nablact/node-express-legacy:v0.3 40 | sudo docker push nablact/node-webrepl-nabla:v0.3 41 | sudo docker push nablact/node-webrepl-legacy:v0.3 42 | sudo docker push nablact/python-tornado-nabla:v0.3 43 | sudo docker push nablact/python-tornado-legacy:v0.3 44 | sudo docker push nablact/redis-test-nabla:v0.3 45 | sudo docker push nablact/redis-test-legacy:v0.3 46 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | This repository holds some containerized applications that we use for 2 | testing and also serves the purpose of showing how to run your own 3 | applications using the nabla container bases from the 4 | [nabla-base-build](https://github.com/nabla-containers/nabla-base-build) 5 | repository. 6 | 7 | Each subdirectory contains two Dockerfiles (`Dockerfile` for a 8 | standard container and `Dockerfile.nabla` for a nabla container) and a 9 | Makefile that builds both standard and nabla containers of the 10 | application (for comparison purposes). For example, to build the 11 | `node-express` application, just: 12 | 13 | cd node-express 14 | make 15 | 16 | ### Running the Containers 17 | 18 | The `Makefile` will produce two container images, named after the 19 | directory (the test application name) with "-nabla" or "-legacy" 20 | appended to the end. To run the applications, use Docker (you must 21 | have installed [`runnc`](https://github.com/nabla-containers/runnc) 22 | for the nabla case). For example: 23 | 24 | docker run --rm -it node-express-legacy 25 | docker run --rm -it --runtime=runnc node-express-nabla 26 | 27 | ### Modifying Dockerfiles 28 | 29 | In the general case, each `Dockerfile.nabla` represents a stage build. 30 | For example, the first stage may install all of the node.js or Python 31 | packages necessary in a standard container, then the second stage 32 | copies them into a fresh nabla base container for the language 33 | runtime. 34 | 35 | The example `Dockerfile.nabla` files in this repository assume that 36 | the bases are available locally, as if built from the 37 | [nabla-base-build](https://github.com/nabla-containers/nabla-base-build) 38 | repository. Alternatively, the `FROM` line could reference our base 39 | images on [Docker hub](https://hub.docker.com/u/nablact/), for 40 | example: 41 | 42 | FROM nablact/nabla-node-base 43 | 44 | ### Information about the demo applications 45 | 46 | * `node-express-nabla` and `node-express-legacy`: runs a node express web server. Access it on port 47 | 8080; you should receive a text string "Nabla!". 48 | 49 | * `node-webrepl-naba` and `node-webrepl-legacy`: runs a webrepl in node. Access it on port 8081. 50 | 51 | * `python-tornado-nabla` and `python-tornado-legacy`: runs a Python tornado web server. Access it on 52 | port 5000, you should see some `x`s. 53 | 54 | * `redis-test-nabla` and `redis-test-legacy`: runs a Redis key/value store. Access it on port 6379 55 | using e.g. the Redis CLI (you should see OK): 56 | 57 | redis-cli -h 172.17.0.2 -p 6379 set foo bar 58 | 59 | 60 | ### See Also 61 | 62 | * [nabla-containers/runnc](https://github.com/nabla-containers/runnc) 63 | * [nabla-containers/nabla-base-build](https://github.com/nabla-containers/nabla-base-build) 64 | 65 | -------------------------------------------------------------------------------- /go-httpd/Dockerfile.legacy: -------------------------------------------------------------------------------- 1 | FROM golang 2 | 3 | COPY src/ /goapp/ 4 | WORKDIR "/goapp" 5 | 6 | RUN go get -d ./... 7 | RUN go build 8 | 9 | ENTRYPOINT ["/goapp/goapp"] 10 | 11 | -------------------------------------------------------------------------------- /go-httpd/Dockerfile.nabla: -------------------------------------------------------------------------------- 1 | FROM nablact/nabla-go-base:v0.3 2 | 3 | COPY src/ /goapp/ 4 | WORKDIR /goapp 5 | 6 | RUN go get -d ./... 7 | RUN make -f Makefile.goapp 8 | 9 | FROM scratch 10 | COPY --from=0 /goapp/goapp.spt /goapp.nabla 11 | ENTRYPOINT ["/goapp.nabla"] 12 | -------------------------------------------------------------------------------- /go-httpd/Makefile: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2018 Contributors as noted in the AUTHORS file 2 | # 3 | # Permission to use, copy, modify, and/or distribute this software 4 | # for any purpose with or without fee is hereby granted, provided 5 | # that the above copyright notice and this permission notice appear 6 | # in all copies. 7 | # 8 | # THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL 9 | # WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED 10 | # WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE 11 | # AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR 12 | # CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS 13 | # OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 14 | # NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 15 | # CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 16 | 17 | all: Dockerfile.nabla Makefile src/* Dockerfile.legacy 18 | sudo docker build -t go-httpd-nabla -f Dockerfile.nabla . 19 | sudo docker build -t go-httpd-legacy -f Dockerfile.legacy . 20 | -------------------------------------------------------------------------------- /go-httpd/src/helper/process_args.go: -------------------------------------------------------------------------------- 1 | package helper 2 | 3 | import "fmt" 4 | import "C" 5 | import "os" 6 | import "github.com/golang/example/stringutil" 7 | 8 | func Process_args() { 9 | args := os.Args[1:] 10 | fmt.Println(stringutil.Reverse(":sgra enildnammoc toG")) 11 | fmt.Println(args) 12 | } 13 | -------------------------------------------------------------------------------- /go-httpd/src/httpd.go: -------------------------------------------------------------------------------- 1 | package main 2 | 3 | import ( 4 | "./helper" 5 | "C" 6 | "fmt" 7 | "net/http" 8 | ) 9 | 10 | func reqHandler(w http.ResponseWriter, r *http.Request) { 11 | fmt.Fprintf(w, "Response 200 from go-http\n") 12 | } 13 | 14 | func main() { 15 | fmt.Println("Hi") 16 | helper.Process_args() 17 | httpd() 18 | } 19 | 20 | func httpd() { 21 | fmt.Println("You can now call `curl :3000' now") 22 | http.HandleFunc("/", reqHandler) 23 | http.ListenAndServe(":3000", nil) 24 | } 25 | -------------------------------------------------------------------------------- /node-express/Dockerfile.legacy: -------------------------------------------------------------------------------- 1 | FROM node:4.3.0 2 | 3 | WORKDIR /home/node 4 | COPY app/app.js app/app.js 5 | COPY app/package.json app/package.json 6 | RUN (cd app; npm install) 7 | 8 | CMD ["node","/home/node/app/app.js"] 9 | -------------------------------------------------------------------------------- /node-express/Dockerfile.nabla: -------------------------------------------------------------------------------- 1 | FROM node:4.3.0 2 | 3 | WORKDIR /home/node 4 | COPY app/app.js app/app.js 5 | COPY app/package.json app/package.json 6 | RUN (cd app; npm install) 7 | 8 | # The first step gets all the modules 9 | 10 | FROM nablact/nabla-node-base:v0.3 11 | COPY --from=0 /home/node/app/ /home/node/app/ 12 | CMD ["/home/node/app/app.js"] 13 | -------------------------------------------------------------------------------- /node-express/Makefile: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2018 Contributors as noted in the AUTHORS file 2 | # 3 | # Permission to use, copy, modify, and/or distribute this software 4 | # for any purpose with or without fee is hereby granted, provided 5 | # that the above copyright notice and this permission notice appear 6 | # in all copies. 7 | # 8 | # THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL 9 | # WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED 10 | # WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE 11 | # AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR 12 | # CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS 13 | # OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 14 | # NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 15 | # CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 16 | 17 | all: app/package.json app/app.js Dockerfile.legacy Makefile Dockerfile.nabla 18 | sudo docker build -t node-express-nabla -f Dockerfile.nabla . 19 | sudo docker build -t node-express-legacy -f Dockerfile.legacy . 20 | -------------------------------------------------------------------------------- /node-express/app/app.js: -------------------------------------------------------------------------------- 1 | const express = require('express') 2 | const app = express() 3 | 4 | app.get('/', (req, res) => res.send('Nabla!')) 5 | 6 | app.listen(8080, () => console.log('Listening on port 8080')) 7 | -------------------------------------------------------------------------------- /node-express/app/package.json: -------------------------------------------------------------------------------- 1 | 2 | { 3 | "name": "nabla_test", 4 | "version": "0.0.1", 5 | "scripts": { 6 | "start": "node app.js" 7 | }, 8 | "dependencies": { 9 | "express": "^4.15.x" 10 | } 11 | } 12 | -------------------------------------------------------------------------------- /node-webrepl/Dockerfile.legacy: -------------------------------------------------------------------------------- 1 | FROM node:4.3.0 2 | 3 | WORKDIR /home/node 4 | COPY app/app.js app/app.js 5 | COPY app/package.json app/package.json 6 | RUN (cd app; npm install) 7 | 8 | CMD ["node","/home/node/app/app.js"] 9 | -------------------------------------------------------------------------------- /node-webrepl/Dockerfile.nabla: -------------------------------------------------------------------------------- 1 | FROM node:4.3.0 2 | 3 | WORKDIR /home/node 4 | COPY app/app.js app/app.js 5 | COPY app/package.json app/package.json 6 | RUN (cd app; npm install) 7 | 8 | # The first step gets all the modules 9 | 10 | FROM nablact/nabla-node-base:v0.3 11 | COPY --from=0 /home/node/app/ /home/node/app/ 12 | CMD ["/home/node/app/app.js"] 13 | -------------------------------------------------------------------------------- /node-webrepl/Makefile: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2018 Contributors as noted in the AUTHORS file 2 | # 3 | # Permission to use, copy, modify, and/or distribute this software 4 | # for any purpose with or without fee is hereby granted, provided 5 | # that the above copyright notice and this permission notice appear 6 | # in all copies. 7 | # 8 | # THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL 9 | # WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED 10 | # WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE 11 | # AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR 12 | # CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS 13 | # OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 14 | # NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 15 | # CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 16 | 17 | all: Dockerfile.nabla Dockerfile.legacy Makefile app/app.js app/package.json 18 | sudo docker build -t node-webrepl-nabla -f Dockerfile.nabla . 19 | sudo docker build -t node-webrepl-legacy -f Dockerfile.legacy . 20 | 21 | -------------------------------------------------------------------------------- /node-webrepl/app/app.js: -------------------------------------------------------------------------------- 1 | var ip = require("ip"); 2 | 3 | var webrepl = require('webrepl'); 4 | console.log('listening on http://' + ip.address() + ':8081/') 5 | webrepl.start(8081); 6 | -------------------------------------------------------------------------------- /node-webrepl/app/package.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "hello", 3 | "version": "1.0.0", 4 | "description": "", 5 | "main": "app.js", 6 | "scripts": { 7 | "test": "node app.js" 8 | }, 9 | "author": "", 10 | "license": "ISC", 11 | "dependencies": { 12 | "ip": "^1.1.5", 13 | "request": "^2.87.0", 14 | "webrepl": "https://github.com/ricarkol/webrepl.git" 15 | } 16 | } 17 | -------------------------------------------------------------------------------- /python-tornado/Dockerfile.legacy: -------------------------------------------------------------------------------- 1 | FROM python:3.5.2-alpine 2 | RUN apk update && apk add iproute2 git 3 | 4 | ENV PYTHONHOME=/usr/local 5 | RUN pip install tornado==4.5.3 six perf 6 | 7 | COPY tornado_main.py /usr/local/tornado_main.py 8 | 9 | ENTRYPOINT ["python", "/usr/local/tornado_main.py"] 10 | -------------------------------------------------------------------------------- /python-tornado/Dockerfile.nabla: -------------------------------------------------------------------------------- 1 | FROM python:3.5.2-alpine 2 | 3 | ENV PYTHONHOME=/usr/local 4 | RUN pip install tornado==4.5.3 six perf 5 | 6 | # First stage installs dependencies 7 | 8 | FROM nablact/nabla-python3-base:v0.3 9 | 10 | # nabla-python3-base has a PYTHONHOME of /usr/local 11 | 12 | COPY --from=0 /usr/local/lib /usr/local/lib 13 | COPY tornado_main.py /usr/local/tornado_main.py 14 | CMD ["/usr/local/tornado_main.py"] 15 | -------------------------------------------------------------------------------- /python-tornado/Makefile: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2018 Contributors as noted in the AUTHORS file 2 | # 3 | # Permission to use, copy, modify, and/or distribute this software 4 | # for any purpose with or without fee is hereby granted, provided 5 | # that the above copyright notice and this permission notice appear 6 | # in all copies. 7 | # 8 | # THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL 9 | # WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED 10 | # WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE 11 | # AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR 12 | # CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS 13 | # OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 14 | # NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 15 | # CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 16 | 17 | all: Dockerfile.legacy Dockerfile.nabla Makefile tornado_main.py 18 | sudo docker build -t python-tornado-nabla -f Dockerfile.nabla . 19 | sudo docker build -t python-tornado-legacy -f Dockerfile.legacy . 20 | -------------------------------------------------------------------------------- /python-tornado/tornado_main.py: -------------------------------------------------------------------------------- 1 | import tornado.ioloop 2 | import tornado.web 3 | 4 | class MainHandler(tornado.web.RequestHandler): 5 | def get(self): 6 | size = int(self.get_argument('size', 1000)) 7 | self.write('x'*size) 8 | 9 | def post(self): 10 | size = int(self.get_argument('size', 1000)) 11 | self.write('x'*size) 12 | 13 | def make_app(): 14 | return tornado.web.Application([ 15 | (r"/", MainHandler), 16 | ]) 17 | 18 | if __name__ == "__main__": 19 | app = make_app() 20 | app.listen(5000) 21 | tornado.ioloop.IOLoop.current().start() 22 | -------------------------------------------------------------------------------- /redis-test/Dockerfile.legacy: -------------------------------------------------------------------------------- 1 | FROM redis:3 2 | 3 | COPY redis.conf /usr/local/etc/redis/redis.conf 4 | EXPOSE 6379 5 | 6 | CMD ["redis-server", "/usr/local/etc/redis/redis.conf"] 7 | -------------------------------------------------------------------------------- /redis-test/Dockerfile.nabla: -------------------------------------------------------------------------------- 1 | FROM nablact/nabla-redis-base:v0.3 2 | 3 | COPY redis.conf /data/conf/redis.conf 4 | CMD ["/data/conf/redis.conf"] 5 | -------------------------------------------------------------------------------- /redis-test/Makefile: -------------------------------------------------------------------------------- 1 | # Copyright (c) 2018 Contributors as noted in the AUTHORS file 2 | # 3 | # Permission to use, copy, modify, and/or distribute this software 4 | # for any purpose with or without fee is hereby granted, provided 5 | # that the above copyright notice and this permission notice appear 6 | # in all copies. 7 | # 8 | # THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL 9 | # WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED 10 | # WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE 11 | # AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR 12 | # CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS 13 | # OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, 14 | # NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN 15 | # CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 16 | 17 | all: Dockerfile.legacy Dockerfile.nabla Makefile redis.conf 18 | sudo docker build -t redis-test-nabla -f Dockerfile.nabla . 19 | sudo docker build -t redis-test-legacy -f Dockerfile.legacy . 20 | 21 | -------------------------------------------------------------------------------- /redis-test/redis.conf: -------------------------------------------------------------------------------- 1 | # Redis configuration file example 2 | 3 | # Note on units: when memory size is needed, it is possible to specify 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 | ################################## INCLUDES ################################### 16 | 17 | # Include one or more other config files here. This is useful if you 18 | # have a standard template that goes to all Redis servers but also need 19 | # to customize a few per-server settings. Include files can include 20 | # other files, so use this wisely. 21 | # 22 | # Notice option "include" won't be rewritten by command "CONFIG REWRITE" 23 | # from admin or Redis Sentinel. Since Redis always uses the last processed 24 | # line as value of a configuration directive, you'd better put includes 25 | # at the beginning of this file to avoid overwriting config change at runtime. 26 | # 27 | # If instead you are interested in using includes to override configuration 28 | # options, it is better to use include as the last line. 29 | # 30 | # include /path/to/local.conf 31 | # include /path/to/other.conf 32 | 33 | ################################ GENERAL ##################################### 34 | 35 | # By default Redis does not run as a daemon. Use 'yes' if you need it. 36 | # Note that Redis will write a pid file in /var/run/redis.pid when daemonized. 37 | daemonize no 38 | 39 | # When running daemonized, Redis writes a pid file in /var/run/redis.pid by 40 | # default. You can specify a custom pid file location here. 41 | pidfile /var/run/redis.pid 42 | 43 | # Accept connections on the specified port, default is 6379. 44 | # If port 0 is specified Redis will not listen on a TCP socket. 45 | port 6379 46 | 47 | # TCP listen() backlog. 48 | # 49 | # In high requests-per-second environments you need an high backlog in order 50 | # to avoid slow clients connections issues. Note that the Linux kernel 51 | # will silently truncate it to the value of /proc/sys/net/core/somaxconn so 52 | # make sure to raise both the value of somaxconn and tcp_max_syn_backlog 53 | # in order to get the desired effect. 54 | tcp-backlog 511 55 | 56 | # By default Redis listens for connections from all the network interfaces 57 | # available on the server. It is possible to listen to just one or multiple 58 | # interfaces using the "bind" configuration directive, followed by one or 59 | # more IP addresses. 60 | # 61 | # Examples: 62 | # 63 | # bind 192.168.1.100 10.0.0.1 64 | # bind 127.0.0.1 65 | 66 | # Specify the path for the Unix socket that will be used to listen for 67 | # incoming connections. There is no default, so Redis will not listen 68 | # on a unix socket when not specified. 69 | # 70 | # unixsocket /tmp/redis.sock 71 | # unixsocketperm 700 72 | 73 | # Close the connection after a client is idle for N seconds (0 to disable) 74 | timeout 0 75 | 76 | # TCP keepalive. 77 | # 78 | # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence 79 | # of communication. This is useful for two reasons: 80 | # 81 | # 1) Detect dead peers. 82 | # 2) Take the connection alive from the point of view of network 83 | # equipment in the middle. 84 | # 85 | # On Linux, the specified value (in seconds) is the period used to send ACKs. 86 | # Note that to close the connection the double of the time is needed. 87 | # On other kernels the period depends on the kernel configuration. 88 | # 89 | # A reasonable value for this option is 60 seconds. 90 | tcp-keepalive 60 91 | 92 | # Specify the server verbosity level. 93 | # This can be one of: 94 | # debug (a lot of information, useful for development/testing) 95 | # verbose (many rarely useful info, but not a mess like the debug level) 96 | # notice (moderately verbose, what you want in production probably) 97 | # warning (only very important / critical messages are logged) 98 | loglevel notice 99 | 100 | # Specify the log file name. Also the empty string can be used to force 101 | # Redis to log on the standard output. Note that if you use standard 102 | # output for logging but daemonize, logs will be sent to /dev/null 103 | logfile "" 104 | 105 | # To enable logging to the system logger, just set 'syslog-enabled' to yes, 106 | # and optionally update the other syslog parameters to suit your needs. 107 | # syslog-enabled no 108 | 109 | # Specify the syslog identity. 110 | # syslog-ident redis 111 | 112 | # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7. 113 | # syslog-facility local0 114 | 115 | # Set the number of databases. The default database is DB 0, you can select 116 | # a different one on a per-connection basis using SELECT where 117 | # dbid is a number between 0 and 'databases'-1 118 | databases 16 119 | 120 | ################################ SNAPSHOTTING ################################ 121 | # 122 | # Save the DB on disk: 123 | # 124 | # save 125 | # 126 | # Will save the DB if both the given number of seconds and the given 127 | # number of write operations against the DB occurred. 128 | # 129 | # In the example below the behaviour will be to save: 130 | # after 900 sec (15 min) if at least 1 key changed 131 | # after 300 sec (5 min) if at least 10 keys changed 132 | # after 60 sec if at least 10000 keys changed 133 | # 134 | # Note: you can disable saving completely by commenting out all "save" lines. 135 | # 136 | # It is also possible to remove all the previously configured save 137 | # points by adding a save directive with a single empty string argument 138 | # like in the following example: 139 | # 140 | # save "" 141 | 142 | #save 900 1 143 | #save 300 10 144 | #save 60 10000 145 | 146 | # By default Redis will stop accepting writes if RDB snapshots are enabled 147 | # (at least one save point) and the latest background save failed. 148 | # This will make the user aware (in a hard way) that data is not persisting 149 | # on disk properly, otherwise chances are that no one will notice and some 150 | # disaster will happen. 151 | # 152 | # If the background saving process will start working again Redis will 153 | # automatically allow writes again. 154 | # 155 | # However if you have setup your proper monitoring of the Redis server 156 | # and persistence, you may want to disable this feature so that Redis will 157 | # continue to work as usual even if there are problems with disk, 158 | # permissions, and so forth. 159 | stop-writes-on-bgsave-error yes 160 | 161 | # Compress string objects using LZF when dump .rdb databases? 162 | # For default that's set to 'yes' as it's almost always a win. 163 | # If you want to save some CPU in the saving child set it to 'no' but 164 | # the dataset will likely be bigger if you have compressible values or keys. 165 | rdbcompression yes 166 | 167 | # Since version 5 of RDB a CRC64 checksum is placed at the end of the file. 168 | # This makes the format more resistant to corruption but there is a performance 169 | # hit to pay (around 10%) when saving and loading RDB files, so you can disable it 170 | # for maximum performances. 171 | # 172 | # RDB files created with checksum disabled have a checksum of zero that will 173 | # tell the loading code to skip the check. 174 | rdbchecksum yes 175 | 176 | # The filename where to dump the DB 177 | dbfilename dump.rdb 178 | 179 | # The working directory. 180 | # 181 | # The DB will be written inside this directory, with the filename specified 182 | # above using the 'dbfilename' configuration directive. 183 | # 184 | # The Append Only File will also be created inside this directory. 185 | # 186 | # Note that you must specify a directory here, not a file name. 187 | dir /tmp/ 188 | 189 | ################################# REPLICATION ################################# 190 | 191 | # Master-Slave replication. Use slaveof to make a Redis instance a copy of 192 | # another Redis server. A few things to understand ASAP about Redis replication. 193 | # 194 | # 1) Redis replication is asynchronous, but you can configure a master to 195 | # stop accepting writes if it appears to be not connected with at least 196 | # a given number of slaves. 197 | # 2) Redis slaves are able to perform a partial resynchronization with the 198 | # master if the replication link is lost for a relatively small amount of 199 | # time. You may want to configure the replication backlog size (see the next 200 | # sections of this file) with a sensible value depending on your needs. 201 | # 3) Replication is automatic and does not need user intervention. After a 202 | # network partition slaves automatically try to reconnect to masters 203 | # and resynchronize with them. 204 | # 205 | # slaveof 206 | 207 | # If the master is password protected (using the "requirepass" configuration 208 | # directive below) it is possible to tell the slave to authenticate before 209 | # starting the replication synchronization process, otherwise the master will 210 | # refuse the slave request. 211 | # 212 | # masterauth 213 | 214 | # When a slave loses its connection with the master, or when the replication 215 | # is still in progress, the slave can act in two different ways: 216 | # 217 | # 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will 218 | # still reply to client requests, possibly with out of date data, or the 219 | # data set may just be empty if this is the first synchronization. 220 | # 221 | # 2) if slave-serve-stale-data is set to 'no' the slave will reply with 222 | # an error "SYNC with master in progress" to all the kind of commands 223 | # but to INFO and SLAVEOF. 224 | # 225 | slave-serve-stale-data yes 226 | 227 | # You can configure a slave instance to accept writes or not. Writing against 228 | # a slave instance may be useful to store some ephemeral data (because data 229 | # written on a slave will be easily deleted after resync with the master) but 230 | # may also cause problems if clients are writing to it because of a 231 | # misconfiguration. 232 | # 233 | # Since Redis 2.6 by default slaves are read-only. 234 | # 235 | # Note: read only slaves are not designed to be exposed to untrusted clients 236 | # on the internet. It's just a protection layer against misuse of the instance. 237 | # Still a read only slave exports by default all the administrative commands 238 | # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve 239 | # security of read only slaves using 'rename-command' to shadow all the 240 | # administrative / dangerous commands. 241 | slave-read-only yes 242 | 243 | # Replication SYNC strategy: disk or socket. 244 | # 245 | # ------------------------------------------------------- 246 | # WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY 247 | # ------------------------------------------------------- 248 | # 249 | # New slaves and reconnecting slaves that are not able to continue the replication 250 | # process just receiving differences, need to do what is called a "full 251 | # synchronization". An RDB file is transmitted from the master to the slaves. 252 | # The transmission can happen in two different ways: 253 | # 254 | # 1) Disk-backed: The Redis master creates a new process that writes the RDB 255 | # file on disk. Later the file is transferred by the parent 256 | # process to the slaves incrementally. 257 | # 2) Diskless: The Redis master creates a new process that directly writes the 258 | # RDB file to slave sockets, without touching the disk at all. 259 | # 260 | # With disk-backed replication, while the RDB file is generated, more slaves 261 | # can be queued and served with the RDB file as soon as the current child producing 262 | # the RDB file finishes its work. With diskless replication instead once 263 | # the transfer starts, new slaves arriving will be queued and a new transfer 264 | # will start when the current one terminates. 265 | # 266 | # When diskless replication is used, the master waits a configurable amount of 267 | # time (in seconds) before starting the transfer in the hope that multiple slaves 268 | # will arrive and the transfer can be parallelized. 269 | # 270 | # With slow disks and fast (large bandwidth) networks, diskless replication 271 | # works better. 272 | repl-diskless-sync no 273 | 274 | # When diskless replication is enabled, it is possible to configure the delay 275 | # the server waits in order to spawn the child that transfers the RDB via socket 276 | # to the slaves. 277 | # 278 | # This is important since once the transfer starts, it is not possible to serve 279 | # new slaves arriving, that will be queued for the next RDB transfer, so the server 280 | # waits a delay in order to let more slaves arrive. 281 | # 282 | # The delay is specified in seconds, and by default is 5 seconds. To disable 283 | # it entirely just set it to 0 seconds and the transfer will start ASAP. 284 | repl-diskless-sync-delay 5 285 | 286 | # Slaves send PINGs to server in a predefined interval. It's possible to change 287 | # this interval with the repl_ping_slave_period option. The default value is 10 288 | # seconds. 289 | # 290 | # repl-ping-slave-period 10 291 | 292 | # The following option sets the replication timeout for: 293 | # 294 | # 1) Bulk transfer I/O during SYNC, from the point of view of slave. 295 | # 2) Master timeout from the point of view of slaves (data, pings). 296 | # 3) Slave timeout from the point of view of masters (REPLCONF ACK pings). 297 | # 298 | # It is important to make sure that this value is greater than the value 299 | # specified for repl-ping-slave-period otherwise a timeout will be detected 300 | # every time there is low traffic between the master and the slave. 301 | # 302 | # repl-timeout 60 303 | 304 | # Disable TCP_NODELAY on the slave socket after SYNC? 305 | # 306 | # If you select "yes" Redis will use a smaller number of TCP packets and 307 | # less bandwidth to send data to slaves. But this can add a delay for 308 | # the data to appear on the slave side, up to 40 milliseconds with 309 | # Linux kernels using a default configuration. 310 | # 311 | # If you select "no" the delay for data to appear on the slave side will 312 | # be reduced but more bandwidth will be used for replication. 313 | # 314 | # By default we optimize for low latency, but in very high traffic conditions 315 | # or when the master and slaves are many hops away, turning this to "yes" may 316 | # be a good idea. 317 | repl-disable-tcp-nodelay no 318 | 319 | # Set the replication backlog size. The backlog is a buffer that accumulates 320 | # slave data when slaves are disconnected for some time, so that when a slave 321 | # wants to reconnect again, often a full resync is not needed, but a partial 322 | # resync is enough, just passing the portion of data the slave missed while 323 | # disconnected. 324 | # 325 | # The bigger the replication backlog, the longer the time the slave can be 326 | # disconnected and later be able to perform a partial resynchronization. 327 | # 328 | # The backlog is only allocated once there is at least a slave connected. 329 | # 330 | # repl-backlog-size 1mb 331 | 332 | # After a master has no longer connected slaves for some time, the backlog 333 | # will be freed. The following option configures the amount of seconds that 334 | # need to elapse, starting from the time the last slave disconnected, for 335 | # the backlog buffer to be freed. 336 | # 337 | # A value of 0 means to never release the backlog. 338 | # 339 | # repl-backlog-ttl 3600 340 | 341 | # The slave priority is an integer number published by Redis in the INFO output. 342 | # It is used by Redis Sentinel in order to select a slave to promote into a 343 | # master if the master is no longer working correctly. 344 | # 345 | # A slave with a low priority number is considered better for promotion, so 346 | # for instance if there are three slaves with priority 10, 100, 25 Sentinel will 347 | # pick the one with priority 10, that is the lowest. 348 | # 349 | # However a special priority of 0 marks the slave as not able to perform the 350 | # role of master, so a slave with priority of 0 will never be selected by 351 | # Redis Sentinel for promotion. 352 | # 353 | # By default the priority is 100. 354 | slave-priority 100 355 | 356 | # It is possible for a master to stop accepting writes if there are less than 357 | # N slaves connected, having a lag less or equal than M seconds. 358 | # 359 | # The N slaves need to be in "online" state. 360 | # 361 | # The lag in seconds, that must be <= the specified value, is calculated from 362 | # the last ping received from the slave, that is usually sent every second. 363 | # 364 | # This option does not GUARANTEE that N replicas will accept the write, but 365 | # will limit the window of exposure for lost writes in case not enough slaves 366 | # are available, to the specified number of seconds. 367 | # 368 | # For example to require at least 3 slaves with a lag <= 10 seconds use: 369 | # 370 | # min-slaves-to-write 3 371 | # min-slaves-max-lag 10 372 | # 373 | # Setting one or the other to 0 disables the feature. 374 | # 375 | # By default min-slaves-to-write is set to 0 (feature disabled) and 376 | # min-slaves-max-lag is set to 10. 377 | 378 | ################################## SECURITY ################################### 379 | 380 | # Require clients to issue AUTH before processing any other 381 | # commands. This might be useful in environments in which you do not trust 382 | # others with access to the host running redis-server. 383 | # 384 | # This should stay commented out for backward compatibility and because most 385 | # people do not need auth (e.g. they run their own servers). 386 | # 387 | # Warning: since Redis is pretty fast an outside user can try up to 388 | # 150k passwords per second against a good box. This means that you should 389 | # use a very strong password otherwise it will be very easy to break. 390 | # 391 | # requirepass foobared 392 | 393 | # Command renaming. 394 | # 395 | # It is possible to change the name of dangerous commands in a shared 396 | # environment. For instance the CONFIG command may be renamed into something 397 | # hard to guess so that it will still be available for internal-use tools 398 | # but not available for general clients. 399 | # 400 | # Example: 401 | # 402 | # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52 403 | # 404 | # It is also possible to completely kill a command by renaming it into 405 | # an empty string: 406 | # 407 | # rename-command CONFIG "" 408 | # 409 | # Please note that changing the name of commands that are logged into the 410 | # AOF file or transmitted to slaves may cause problems. 411 | 412 | ################################### LIMITS #################################### 413 | 414 | # Set the max number of connected clients at the same time. By default 415 | # this limit is set to 10000 clients, however if the Redis server is not 416 | # able to configure the process file limit to allow for the specified limit 417 | # the max number of allowed clients is set to the current file limit 418 | # minus 32 (as Redis reserves a few file descriptors for internal uses). 419 | # 420 | # Once the limit is reached Redis will close all the new connections sending 421 | # an error 'max number of clients reached'. 422 | # 423 | # maxclients 10000 424 | 425 | # Don't use more memory than the specified amount of bytes. 426 | # When the memory limit is reached Redis will try to remove keys 427 | # according to the eviction policy selected (see maxmemory-policy). 428 | # 429 | # If Redis can't remove keys according to the policy, or if the policy is 430 | # set to 'noeviction', Redis will start to reply with errors to commands 431 | # that would use more memory, like SET, LPUSH, and so on, and will continue 432 | # to reply to read-only commands like GET. 433 | # 434 | # This option is usually useful when using Redis as an LRU cache, or to set 435 | # a hard memory limit for an instance (using the 'noeviction' policy). 436 | # 437 | # WARNING: If you have slaves attached to an instance with maxmemory on, 438 | # the size of the output buffers needed to feed the slaves are subtracted 439 | # from the used memory count, so that network problems / resyncs will 440 | # not trigger a loop where keys are evicted, and in turn the output 441 | # buffer of slaves is full with DELs of keys evicted triggering the deletion 442 | # of more keys, and so forth until the database is completely emptied. 443 | # 444 | # In short... if you have slaves attached it is suggested that you set a lower 445 | # limit for maxmemory so that there is some free RAM on the system for slave 446 | # output buffers (but this is not needed if the policy is 'noeviction'). 447 | # 448 | # maxmemory 449 | 450 | # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory 451 | # is reached. You can select among five behaviors: 452 | # 453 | # volatile-lru -> remove the key with an expire set using an LRU algorithm 454 | # allkeys-lru -> remove any key according to the LRU algorithm 455 | # volatile-random -> remove a random key with an expire set 456 | # allkeys-random -> remove a random key, any key 457 | # volatile-ttl -> remove the key with the nearest expire time (minor TTL) 458 | # noeviction -> don't expire at all, just return an error on write operations 459 | # 460 | # Note: with any of the above policies, Redis will return an error on write 461 | # operations, when there are no suitable keys for eviction. 462 | # 463 | # At the date of writing these commands are: set setnx setex append 464 | # incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd 465 | # sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby 466 | # zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby 467 | # getset mset msetnx exec sort 468 | # 469 | # The default is: 470 | # 471 | # maxmemory-policy noeviction 472 | 473 | # LRU and minimal TTL algorithms are not precise algorithms but approximated 474 | # algorithms (in order to save memory), so you can tune it for speed or 475 | # accuracy. For default Redis will check five keys and pick the one that was 476 | # used less recently, you can change the sample size using the following 477 | # configuration directive. 478 | # 479 | # The default of 5 produces good enough results. 10 Approximates very closely 480 | # true LRU but costs a bit more CPU. 3 is very fast but not very accurate. 481 | # 482 | # maxmemory-samples 5 483 | 484 | ############################## APPEND ONLY MODE ############################### 485 | 486 | # By default Redis asynchronously dumps the dataset on disk. This mode is 487 | # good enough in many applications, but an issue with the Redis process or 488 | # a power outage may result into a few minutes of writes lost (depending on 489 | # the configured save points). 490 | # 491 | # The Append Only File is an alternative persistence mode that provides 492 | # much better durability. For instance using the default data fsync policy 493 | # (see later in the config file) Redis can lose just one second of writes in a 494 | # dramatic event like a server power outage, or a single write if something 495 | # wrong with the Redis process itself happens, but the operating system is 496 | # still running correctly. 497 | # 498 | # AOF and RDB persistence can be enabled at the same time without problems. 499 | # If the AOF is enabled on startup Redis will load the AOF, that is the file 500 | # with the better durability guarantees. 501 | # 502 | # Please check http://redis.io/topics/persistence for more information. 503 | 504 | appendonly no 505 | 506 | # The name of the append only file (default: "appendonly.aof") 507 | 508 | appendfilename "appendonly.aof" 509 | 510 | # The fsync() call tells the Operating System to actually write data on disk 511 | # instead of waiting for more data in the output buffer. Some OS will really flush 512 | # data on disk, some other OS will just try to do it ASAP. 513 | # 514 | # Redis supports three different modes: 515 | # 516 | # no: don't fsync, just let the OS flush the data when it wants. Faster. 517 | # always: fsync after every write to the append only log. Slow, Safest. 518 | # everysec: fsync only one time every second. Compromise. 519 | # 520 | # The default is "everysec", as that's usually the right compromise between 521 | # speed and data safety. It's up to you to understand if you can relax this to 522 | # "no" that will let the operating system flush the output buffer when 523 | # it wants, for better performances (but if you can live with the idea of 524 | # some data loss consider the default persistence mode that's snapshotting), 525 | # or on the contrary, use "always" that's very slow but a bit safer than 526 | # everysec. 527 | # 528 | # More details please check the following article: 529 | # http://antirez.com/post/redis-persistence-demystified.html 530 | # 531 | # If unsure, use "everysec". 532 | 533 | # appendfsync always 534 | appendfsync everysec 535 | # appendfsync no 536 | 537 | # When the AOF fsync policy is set to always or everysec, and a background 538 | # saving process (a background save or AOF log background rewriting) is 539 | # performing a lot of I/O against the disk, in some Linux configurations 540 | # Redis may block too long on the fsync() call. Note that there is no fix for 541 | # this currently, as even performing fsync in a different thread will block 542 | # our synchronous write(2) call. 543 | # 544 | # In order to mitigate this problem it's possible to use the following option 545 | # that will prevent fsync() from being called in the main process while a 546 | # BGSAVE or BGREWRITEAOF is in progress. 547 | # 548 | # This means that while another child is saving, the durability of Redis is 549 | # the same as "appendfsync none". In practical terms, this means that it is 550 | # possible to lose up to 30 seconds of log in the worst scenario (with the 551 | # default Linux settings). 552 | # 553 | # If you have latency problems turn this to "yes". Otherwise leave it as 554 | # "no" that is the safest pick from the point of view of durability. 555 | 556 | no-appendfsync-on-rewrite no 557 | 558 | # Automatic rewrite of the append only file. 559 | # Redis is able to automatically rewrite the log file implicitly calling 560 | # BGREWRITEAOF when the AOF log size grows by the specified percentage. 561 | # 562 | # This is how it works: Redis remembers the size of the AOF file after the 563 | # latest rewrite (if no rewrite has happened since the restart, the size of 564 | # the AOF at startup is used). 565 | # 566 | # This base size is compared to the current size. If the current size is 567 | # bigger than the specified percentage, the rewrite is triggered. Also 568 | # you need to specify a minimal size for the AOF file to be rewritten, this 569 | # is useful to avoid rewriting the AOF file even if the percentage increase 570 | # is reached but it is still pretty small. 571 | # 572 | # Specify a percentage of zero in order to disable the automatic AOF 573 | # rewrite feature. 574 | 575 | auto-aof-rewrite-percentage 100 576 | auto-aof-rewrite-min-size 64mb 577 | 578 | # An AOF file may be found to be truncated at the end during the Redis 579 | # startup process, when the AOF data gets loaded back into memory. 580 | # This may happen when the system where Redis is running 581 | # crashes, especially when an ext4 filesystem is mounted without the 582 | # data=ordered option (however this can't happen when Redis itself 583 | # crashes or aborts but the operating system still works correctly). 584 | # 585 | # Redis can either exit with an error when this happens, or load as much 586 | # data as possible (the default now) and start if the AOF file is found 587 | # to be truncated at the end. The following option controls this behavior. 588 | # 589 | # If aof-load-truncated is set to yes, a truncated AOF file is loaded and 590 | # the Redis server starts emitting a log to inform the user of the event. 591 | # Otherwise if the option is set to no, the server aborts with an error 592 | # and refuses to start. When the option is set to no, the user requires 593 | # to fix the AOF file using the "redis-check-aof" utility before to restart 594 | # the server. 595 | # 596 | # Note that if the AOF file will be found to be corrupted in the middle 597 | # the server will still exit with an error. This option only applies when 598 | # Redis will try to read more data from the AOF file but not enough bytes 599 | # will be found. 600 | aof-load-truncated yes 601 | 602 | ################################ LUA SCRIPTING ############################### 603 | 604 | # Max execution time of a Lua script in milliseconds. 605 | # 606 | # If the maximum execution time is reached Redis will log that a script is 607 | # still in execution after the maximum allowed time and will start to 608 | # reply to queries with an error. 609 | # 610 | # When a long running script exceeds the maximum execution time only the 611 | # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be 612 | # used to stop a script that did not yet called write commands. The second 613 | # is the only way to shut down the server in the case a write command was 614 | # already issued by the script but the user doesn't want to wait for the natural 615 | # termination of the script. 616 | # 617 | # Set it to 0 or a negative value for unlimited execution without warnings. 618 | lua-time-limit 5000 619 | 620 | ################################ REDIS CLUSTER ############################### 621 | # 622 | # ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 623 | # WARNING EXPERIMENTAL: Redis Cluster is considered to be stable code, however 624 | # in order to mark it as "mature" we need to wait for a non trivial percentage 625 | # of users to deploy it in production. 626 | # ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 627 | # 628 | # Normal Redis instances can't be part of a Redis Cluster; only nodes that are 629 | # started as cluster nodes can. In order to start a Redis instance as a 630 | # cluster node enable the cluster support uncommenting the following: 631 | # 632 | # cluster-enabled yes 633 | 634 | # Every cluster node has a cluster configuration file. This file is not 635 | # intended to be edited by hand. It is created and updated by Redis nodes. 636 | # Every Redis Cluster node requires a different cluster configuration file. 637 | # Make sure that instances running in the same system do not have 638 | # overlapping cluster configuration file names. 639 | # 640 | # cluster-config-file nodes-6379.conf 641 | 642 | # Cluster node timeout is the amount of milliseconds a node must be unreachable 643 | # for it to be considered in failure state. 644 | # Most other internal time limits are multiple of the node timeout. 645 | # 646 | # cluster-node-timeout 15000 647 | 648 | # A slave of a failing master will avoid to start a failover if its data 649 | # looks too old. 650 | # 651 | # There is no simple way for a slave to actually have a exact measure of 652 | # its "data age", so the following two checks are performed: 653 | # 654 | # 1) If there are multiple slaves able to failover, they exchange messages 655 | # in order to try to give an advantage to the slave with the best 656 | # replication offset (more data from the master processed). 657 | # Slaves will try to get their rank by offset, and apply to the start 658 | # of the failover a delay proportional to their rank. 659 | # 660 | # 2) Every single slave computes the time of the last interaction with 661 | # its master. This can be the last ping or command received (if the master 662 | # is still in the "connected" state), or the time that elapsed since the 663 | # disconnection with the master (if the replication link is currently down). 664 | # If the last interaction is too old, the slave will not try to failover 665 | # at all. 666 | # 667 | # The point "2" can be tuned by user. Specifically a slave will not perform 668 | # the failover if, since the last interaction with the master, the time 669 | # elapsed is greater than: 670 | # 671 | # (node-timeout * slave-validity-factor) + repl-ping-slave-period 672 | # 673 | # So for example if node-timeout is 30 seconds, and the slave-validity-factor 674 | # is 10, and assuming a default repl-ping-slave-period of 10 seconds, the 675 | # slave will not try to failover if it was not able to talk with the master 676 | # for longer than 310 seconds. 677 | # 678 | # A large slave-validity-factor may allow slaves with too old data to failover 679 | # a master, while a too small value may prevent the cluster from being able to 680 | # elect a slave at all. 681 | # 682 | # For maximum availability, it is possible to set the slave-validity-factor 683 | # to a value of 0, which means, that slaves will always try to failover the 684 | # master regardless of the last time they interacted with the master. 685 | # (However they'll always try to apply a delay proportional to their 686 | # offset rank). 687 | # 688 | # Zero is the only value able to guarantee that when all the partitions heal 689 | # the cluster will always be able to continue. 690 | # 691 | # cluster-slave-validity-factor 10 692 | 693 | # Cluster slaves are able to migrate to orphaned masters, that are masters 694 | # that are left without working slaves. This improves the cluster ability 695 | # to resist to failures as otherwise an orphaned master can't be failed over 696 | # in case of failure if it has no working slaves. 697 | # 698 | # Slaves migrate to orphaned masters only if there are still at least a 699 | # given number of other working slaves for their old master. This number 700 | # is the "migration barrier". A migration barrier of 1 means that a slave 701 | # will migrate only if there is at least 1 other working slave for its master 702 | # and so forth. It usually reflects the number of slaves you want for every 703 | # master in your cluster. 704 | # 705 | # Default is 1 (slaves migrate only if their masters remain with at least 706 | # one slave). To disable migration just set it to a very large value. 707 | # A value of 0 can be set but is useful only for debugging and dangerous 708 | # in production. 709 | # 710 | # cluster-migration-barrier 1 711 | 712 | # By default Redis Cluster nodes stop accepting queries if they detect there 713 | # is at least an hash slot uncovered (no available node is serving it). 714 | # This way if the cluster is partially down (for example a range of hash slots 715 | # are no longer covered) all the cluster becomes, eventually, unavailable. 716 | # It automatically returns available as soon as all the slots are covered again. 717 | # 718 | # However sometimes you want the subset of the cluster which is working, 719 | # to continue to accept queries for the part of the key space that is still 720 | # covered. In order to do so, just set the cluster-require-full-coverage 721 | # option to no. 722 | # 723 | # cluster-require-full-coverage yes 724 | 725 | # In order to setup your cluster make sure to read the documentation 726 | # available at http://redis.io web site. 727 | 728 | ################################## SLOW LOG ################################### 729 | 730 | # The Redis Slow Log is a system to log queries that exceeded a specified 731 | # execution time. The execution time does not include the I/O operations 732 | # like talking with the client, sending the reply and so forth, 733 | # but just the time needed to actually execute the command (this is the only 734 | # stage of command execution where the thread is blocked and can not serve 735 | # other requests in the meantime). 736 | # 737 | # You can configure the slow log with two parameters: one tells Redis 738 | # what is the execution time, in microseconds, to exceed in order for the 739 | # command to get logged, and the other parameter is the length of the 740 | # slow log. When a new command is logged the oldest one is removed from the 741 | # queue of logged commands. 742 | 743 | # The following time is expressed in microseconds, so 1000000 is equivalent 744 | # to one second. Note that a negative number disables the slow log, while 745 | # a value of zero forces the logging of every command. 746 | slowlog-log-slower-than 10000 747 | 748 | # There is no limit to this length. Just be aware that it will consume memory. 749 | # You can reclaim memory used by the slow log with SLOWLOG RESET. 750 | slowlog-max-len 128 751 | 752 | ################################ LATENCY MONITOR ############################## 753 | 754 | # The Redis latency monitoring subsystem samples different operations 755 | # at runtime in order to collect data related to possible sources of 756 | # latency of a Redis instance. 757 | # 758 | # Via the LATENCY command this information is available to the user that can 759 | # print graphs and obtain reports. 760 | # 761 | # The system only logs operations that were performed in a time equal or 762 | # greater than the amount of milliseconds specified via the 763 | # latency-monitor-threshold configuration directive. When its value is set 764 | # to zero, the latency monitor is turned off. 765 | # 766 | # By default latency monitoring is disabled since it is mostly not needed 767 | # if you don't have latency issues, and collecting data has a performance 768 | # impact, that while very small, can be measured under big load. Latency 769 | # monitoring can easily be enabled at runtime using the command 770 | # "CONFIG SET latency-monitor-threshold " if needed. 771 | latency-monitor-threshold 0 772 | 773 | ############################# EVENT NOTIFICATION ############################## 774 | 775 | # Redis can notify Pub/Sub clients about events happening in the key space. 776 | # This feature is documented at http://redis.io/topics/notifications 777 | # 778 | # For instance if keyspace events notification is enabled, and a client 779 | # performs a DEL operation on key "foo" stored in the Database 0, two 780 | # messages will be published via Pub/Sub: 781 | # 782 | # PUBLISH __keyspace@0__:foo del 783 | # PUBLISH __keyevent@0__:del foo 784 | # 785 | # It is possible to select the events that Redis will notify among a set 786 | # of classes. Every class is identified by a single character: 787 | # 788 | # K Keyspace events, published with __keyspace@__ prefix. 789 | # E Keyevent events, published with __keyevent@__ prefix. 790 | # g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ... 791 | # $ String commands 792 | # l List commands 793 | # s Set commands 794 | # h Hash commands 795 | # z Sorted set commands 796 | # x Expired events (events generated every time a key expires) 797 | # e Evicted events (events generated when a key is evicted for maxmemory) 798 | # A Alias for g$lshzxe, so that the "AKE" string means all the events. 799 | # 800 | # The "notify-keyspace-events" takes as argument a string that is composed 801 | # of zero or multiple characters. The empty string means that notifications 802 | # are disabled. 803 | # 804 | # Example: to enable list and generic events, from the point of view of the 805 | # event name, use: 806 | # 807 | # notify-keyspace-events Elg 808 | # 809 | # Example 2: to get the stream of the expired keys subscribing to channel 810 | # name __keyevent@0__:expired use: 811 | # 812 | # notify-keyspace-events Ex 813 | # 814 | # By default all notifications are disabled because most users don't need 815 | # this feature and the feature has some overhead. Note that if you don't 816 | # specify at least one of K or E, no events will be delivered. 817 | notify-keyspace-events "" 818 | 819 | ############################### ADVANCED CONFIG ############################### 820 | 821 | # Hashes are encoded using a memory efficient data structure when they have a 822 | # small number of entries, and the biggest entry does not exceed a given 823 | # threshold. These thresholds can be configured using the following directives. 824 | hash-max-ziplist-entries 512 825 | hash-max-ziplist-value 64 826 | 827 | # Similarly to hashes, small lists are also encoded in a special way in order 828 | # to save a lot of space. The special representation is only used when 829 | # you are under the following limits: 830 | list-max-ziplist-entries 512 831 | list-max-ziplist-value 64 832 | 833 | # Sets have a special encoding in just one case: when a set is composed 834 | # of just strings that happen to be integers in radix 10 in the range 835 | # of 64 bit signed integers. 836 | # The following configuration setting sets the limit in the size of the 837 | # set in order to use this special memory saving encoding. 838 | set-max-intset-entries 512 839 | 840 | # Similarly to hashes and lists, sorted sets are also specially encoded in 841 | # order to save a lot of space. This encoding is only used when the length and 842 | # elements of a sorted set are below the following limits: 843 | zset-max-ziplist-entries 128 844 | zset-max-ziplist-value 64 845 | 846 | # HyperLogLog sparse representation bytes limit. The limit includes the 847 | # 16 bytes header. When an HyperLogLog using the sparse representation crosses 848 | # this limit, it is converted into the dense representation. 849 | # 850 | # A value greater than 16000 is totally useless, since at that point the 851 | # dense representation is more memory efficient. 852 | # 853 | # The suggested value is ~ 3000 in order to have the benefits of 854 | # the space efficient encoding without slowing down too much PFADD, 855 | # which is O(N) with the sparse encoding. The value can be raised to 856 | # ~ 10000 when CPU is not a concern, but space is, and the data set is 857 | # composed of many HyperLogLogs with cardinality in the 0 - 15000 range. 858 | hll-sparse-max-bytes 3000 859 | 860 | # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in 861 | # order to help rehashing the main Redis hash table (the one mapping top-level 862 | # keys to values). The hash table implementation Redis uses (see dict.c) 863 | # performs a lazy rehashing: the more operation you run into a hash table 864 | # that is rehashing, the more rehashing "steps" are performed, so if the 865 | # server is idle the rehashing is never complete and some more memory is used 866 | # by the hash table. 867 | # 868 | # The default is to use this millisecond 10 times every second in order to 869 | # actively rehash the main dictionaries, freeing memory when possible. 870 | # 871 | # If unsure: 872 | # use "activerehashing no" if you have hard latency requirements and it is 873 | # not a good thing in your environment that Redis can reply from time to time 874 | # to queries with 2 milliseconds delay. 875 | # 876 | # use "activerehashing yes" if you don't have such hard requirements but 877 | # want to free memory asap when possible. 878 | activerehashing yes 879 | 880 | # The client output buffer limits can be used to force disconnection of clients 881 | # that are not reading data from the server fast enough for some reason (a 882 | # common reason is that a Pub/Sub client can't consume messages as fast as the 883 | # publisher can produce them). 884 | # 885 | # The limit can be set differently for the three different classes of clients: 886 | # 887 | # normal -> normal clients including MONITOR clients 888 | # slave -> slave clients 889 | # pubsub -> clients subscribed to at least one pubsub channel or pattern 890 | # 891 | # The syntax of every client-output-buffer-limit directive is the following: 892 | # 893 | # client-output-buffer-limit 894 | # 895 | # A client is immediately disconnected once the hard limit is reached, or if 896 | # the soft limit is reached and remains reached for the specified number of 897 | # seconds (continuously). 898 | # So for instance if the hard limit is 32 megabytes and the soft limit is 899 | # 16 megabytes / 10 seconds, the client will get disconnected immediately 900 | # if the size of the output buffers reach 32 megabytes, but will also get 901 | # disconnected if the client reaches 16 megabytes and continuously overcomes 902 | # the limit for 10 seconds. 903 | # 904 | # By default normal clients are not limited because they don't receive data 905 | # without asking (in a push way), but just after a request, so only 906 | # asynchronous clients may create a scenario where data is requested faster 907 | # than it can read. 908 | # 909 | # Instead there is a default limit for pubsub and slave clients, since 910 | # subscribers and slaves receive data in a push fashion. 911 | # 912 | # Both the hard or the soft limit can be disabled by setting them to zero. 913 | client-output-buffer-limit normal 0 0 0 914 | client-output-buffer-limit slave 256mb 64mb 60 915 | client-output-buffer-limit pubsub 32mb 8mb 60 916 | 917 | # Redis calls an internal function to perform many background tasks, like 918 | # closing connections of clients in timeout, purging expired keys that are 919 | # never requested, and so forth. 920 | # 921 | # Not all tasks are performed with the same frequency, but Redis checks for 922 | # tasks to perform according to the specified "hz" value. 923 | # 924 | # By default "hz" is set to 10. Raising the value will use more CPU when 925 | # Redis is idle, but at the same time will make Redis more responsive when 926 | # there are many keys expiring at the same time, and timeouts may be 927 | # handled with more precision. 928 | # 929 | # The range is between 1 and 500, however a value over 100 is usually not 930 | # a good idea. Most users should use the default of 10 and raise this up to 931 | # 100 only in environments where very low latency is required. 932 | hz 10 933 | 934 | # When a child rewrites the AOF file, if the following option is enabled 935 | # the file will be fsync-ed every 32 MB of data generated. This is useful 936 | # in order to commit the file to the disk more incrementally and avoid 937 | # big latency spikes. 938 | aof-rewrite-incremental-fsync yes 939 | --------------------------------------------------------------------------------