Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "introduction of two installation and deployment methods of Redis". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

1. Install redis on Linux system

Installation

There is an installation tutorial on the redis official website. Link: https://redis.io/download. I have copied the installation steps as follows:

$wget http://download.redis.io/releases/redis-5.0.6.tar.gz $tar xzf redis-5.0.6.tar.gz $cd redis-5.0.6$ make

I operate these commands under the / usr/local directory, that is to say, the installation directory of Redis is / usr/local. After the execution of these commands, Redis is installed on your machine. During the installation process, if gcc is not installed on your machine, make may report the following error after you install gcc

Jemalloc/jemalloc.h: No such file or directory

At that time, we did not intercept the detailed error information, but only intercepted the main section. The reason for this error is that there is a compiled file after our last make error, so we need to clear the last residual file and recompile and replace make with make distclean & & make.

Redis.conf file

Redis.conf is the configuration file of Redis. All the configurations of redis are in this file. This file is very large and has nearly 1400 lines. The operation and instructions for using redis are all in it. You can read this configuration file in detail. In most cases, we just use the default configuration and only need to set a small amount of configuration. The location of redis.conf is under the installation directory of Redis, and I am under the / usr/local/redis-5.0.5 directory. Let's take a look at some configurations that we may modify:

Bind 127.0.0.1: allows access to the IP of the machine. By default, only the machine can access it. You can modify the ip to run it so that other machines can also access it, but if you want all machines to be accessible, just set it to bind 0.0.0.0.

Port started by port 6379:redis instance. Default is 6379.

Daemonize no: whether to run as a daemon. The default is no, which means that if you close the startup window, the redis instance will be closed. Generally speaking, we set this option to yes and run as a daemon. To put it more colloquially, it runs in the background.

Pidfile / var/run/redis_6379.pid: if we run it as a daemon, we will produce a file with the suffix .pid, which can be used by default

Dir. /: persist the file storage location. We'd better set this configuration. I set it to dir / usr/local/redis_data here.

Appendonly no: whether to enable AOF persistence mode. Redis only enables RDB mode by default. Here we set it to yes, and both methods are enabled. Double insurance. We will learn about the difference between these two methods later.

It seems that you can probably set these. For more information about redis.conf configuration, you can read the redis.conf configuration file in detail or consult the relevant manual.

Startup of redis

The startup of Redis is very simple. After the Redis installation is completed, the shell interactive command of Redis will be stored in / usr/local/redis-5.0.5/src, where there is a redis-server, which is the startup command of Redis. Execute:

. / redis-server / usr/local/redis-5.0.5/redis.conf

This is followed by the file path of redis.conf. If nothing happens, we will launch successfully. You will see the following interface:

Redis start

Here we are using a daemon to start, so there will not be a startup interface with redis logo. We can log in to Redis using the shell command, or execute the following command under the src directory:

. / redis-cli

This command takes you to the shell interface. The. / redis-cli command can take some parameters, such as-h IP, to enter the Redis instance of the specified machine, and then you can perform some operations, as shown in the following figure:

Redis operation

Redis shuts down

There are two ways to shut down Redis, one is to shut down the shell interface, and the other is to shut down the Redis instance by kill + process number.

Shell interactive interface closed

Shutdown [nosave | save]

Enter the shutdown command in the shell interface to close the Redis instance, followed by an optional parameter, nosave does not persist the data in memory, and save persists the data in memory. Shutdown shutdown is an elegant way to close. It is recommended to use it.

Kill + process number shuts down the Redis instance

Use ps-ef | grep redis to view the Redis process number, as shown in the following figure:

View redis process number

Find the process number where we need to shut down the redis instance. For example, here our process number is 27133, then we will directly use kill 27133 to shut down the Redis instance service. In this way, we need to pay attention to one thing, that is, we need to delete the pid file, and the location where the pid file is stored is the pidfile / var/run/redis_6379.pid that we configured in redis.conf. We need to delete the redis_6379.pid in the / var/run directory so that the Redis service can be restarted next time.

You can shut down the Redis service in either of the above two ways, but remember not to use Kill 9 to shut down the Redis process, so that Redis will not carry out persistence operations. in addition, it will also cause resources such as buffers not to be gracefully closed, which in extreme cases will result in data loss in AOF and replication.

Redis boot self-startup

We may need to set Redis to boot on the server, but this is also very simple, we only need to do the following four steps.

1. Write the configuration script vim / etc/init.d/redis

#! / bin/sh # # Simple Redis init.d script conceived to work on Linux systems # as it does use of the / proc filesystem. # chkconfig: 2345 80 90 # description:auto_run # Port number REDISPORT=6379 # Startup Command EXEC=/usr/local/redis-5.0.5/src/redis-server # shell delivery Command CLIEXEC=/usr/local/redis-5.0.5/src/redis-cli # pid location PIDFILE=/var/run/redis_$ {REDISPORT} .pid # redis configuration file CONF= "/ usr/local/redis-5.0.5/redis.conf" case "$1" in Start) if [- f $PIDFILE] then echo "$PIDFILE exists Process is already running or crashed "else echo" Starting Redis server... "$EXEC $CONF fi Stop) if [!-f $PIDFILE] then echo "$PIDFILE does not exist Process is not running "else PID=$ (cat $PIDFILE) echo" Stopping... "$CLIEXEC-p $REDISPORT shutdown while [- x / proc/$ {PID}] do echo" Waiting for Redis to shutdown... " Sleep 1 done echo "Redis stopped" fi;; *) echo "Please use start or stop as first argument";; esac

2. Modify redis.conf and set redis to run in daemon mode

# # GENERAL # By default Redis does not run as a daemon. Use 'yes' if you need it. # Note that Redis will write a pid file in / var/run/redis.pid when daemonized. Daemonize yes

3. Modify file execution permissions

Chmod + x / etc/init.d/redis

4. Set up boot boot

# start redis service redis start # stop redis service redis stop # enable service self-start chkconfig redis on2, Docker install Redis

It is more convenient for Docker to install Redis as a whole. I am talking about a non-production environment, that is, a testing or learning environment on your own. The following steps are all based on the fact that you have installed Docker on your computer. Let's start the installation journey.

1. Pull redis image

Docker pull redis

2. Quick start

Docker run-p 6379 redis redis-server 6379-- name myredis-d redis redis-server-- appendonly yes

Start using the default redis.conf configuration in this way. Let's take a look at the meaning of these parameters.

-p 6379 6379: map the port, the front 6379 is the external redis port, and the last 6379 is the redis port inside the container

-- name myredis: the name of the container

Redis redis-server:redis stands for redis image redis-server represents the command to execute, and it is also the startup command for redis, just like the. / redis-server under our linux.

-- appendonly yes: enable AOF persistence

3. Use redis

Through the above steps, we have started the Redis service in Docker, so let's access it through redis-cli and start redis-cli using the following command

Docker exec-it dockerRedis redis-cli

Where dockerRedis is the name of the Redis container you launched. If nothing happens, you can start a redis-cli client, as shown below:

Docker redis-cli client

The above is a simple way to start Redis using Docker, which is much more convenient than installing boot on linux, mainly because you can run on windows system, although it still runs on linux in the end, but this process is imperceptible to us. You can ask: I want to know if redis.conf is feasible at startup? The answer is yes, but if you do not know Docker, you may encounter some holes, I encountered, because I do not know much about Docker, usually use docker only need to pass parameters, no files have been passed. About the configuration file specified at startup, there is a description in the redis image, but it is under linux, not the Docker configuration under the windows system, so I went to the following command

Docker run-v / d:/dockerdata/redis/config/redis.conf:/usr/local/etc/redis/redis.conf-- name myredis redis redis-server / usr/local/etc/redis/redis.conf

This command is a hole, there is no, start this command, you will get the following feedback:

Obviously, this command is useless, of course, it's just that I personally think that maybe I made a mistake, or maybe I don't have enough knowledge. if my friends find a mistake, please give me a lot of advice. Here, I will assume that it is wrong. The right thing to do is to store the redis.conf file on the host of Docker. Obviously, the host of Docker is not the windows system, but the virtual machine started on the windows system. So we need to enter the virtual machine. The default interface of Docker Quickstart Terminal startup does not actually log in to the virtual machine, so we need to change the login method and use the docker-machine ssh command, as shown in the following figure:

Docker Quickstart Terminal startup mode

So we get into the real virtual machine, and we operate on a virtual machine, just like our installation on linux, we first create two directories to store the Redis configuration:

/ usr/local/redis: store redis.conf / usr/local/redis/data: store persistent files

After creating the two directories, we put redis.conf in the / usr/local/redis directory and use the following Docker command to start the Redis image:

Docker run-p 6379 redis redis-server 6379-v / usr/local/redis/redis.conf:/usr/local/etc/redis/redis.conf-v / usr/local/redis/data:/data-- name dockerRedis-d redis redis-server / usr/local/etc/redis/redis.conf

This docker startup command is a little different from the one above. I'll explain two parameters here:

-v / usr/local/redis/redis.conf:/usr/local/etc/redis/redis.conf: this parameter is to copy / usr/local/redis/redis.conf to / usr/local/etc/redis/redis.conf

-v / usr/local/redis/data:/data: the location of persistent files in the container is also mapped to the host, in other words, persistent files are also stored in / usr/local/redis/data

This is the end of the introduction of "introduction to two ways to install and deploy Redis". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.