Linux 安装redis单点

末蓝、 2022-06-16 05:00 187阅读 0赞

一、安装gcc编译环境

\[root@dev01 Downloads\]\# yum install gcc

二、下载并安装

\[root@dev01 Downloads\]\# wget http://download.redis.io/releases/redis-3.2.3.tar.gz  
\[root@dev01 Downloads\]\# ls  
redis-3.2.3.tar.gz  
\[root@dev01 Downloads\]\# tar -xzvf redis-3.2.3.tar.gz  
\[root@dev01 Downloads\]\# mkdir -p /usr/redis-3.2.3/6379  
\[root@dev01 Downloads\]\# cd redis-3.2.3

\[root@dev01 redis-3.2.3\]\# make PREFIX=/usr/redis-3.2.3/6379 install

三、redis服务

\[root@dev01 redis-3.2.3\]\# cd utils/  
\[root@dev01 utils\]\# cp redis\_init\_script /etc/rc.d/init.d/redis6379  
\[root@dev01 utils\]\# vi /etc/rc.d/init.d/redis6379  
      \#!/bin/sh  
      \# chkconfig: 2345 80 90  
      \#  
      \# Simple Redis init.d script conceived to work on Linux systems  
      \# as it does use of the /proc filesystem.  
        
      REDISPORT=6379  
      EXEC=/usr/redis-3.2.3/6379/bin/redis-server  
      CLIEXEC=/usr/redis-3.2.3/6379/bin/redis-cli  
        
      PIDFILE=/var/run/redis\_$\{REDISPORT\}.pid  
      CONF="/etc/redis/$\{REDISPORT\}.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

\[root@dev01 utils\]\# cd ..

\[root@dev01 redis-3.2.3\]\# mkdir -p /etc/redis  
\[root@dev01 redis-3.2.3\]\# cp redis.conf /etc/redis/6379.conf  
\# Redis configuration file example.  
\#  
\# Note that in order to read the configuration file, Redis must be  
\# started with the file path as first argument:  
\#  
\# ./redis-server /path/to/redis.conf  
  
  
\# Note on units: when memory size is needed, it is possible to specify  
\# it in the usual form of 1k 5GB 4M and so forth:  
\#  
\# 1k => 1000 bytes  
\# 1kb => 1024 bytes  
\# 1m => 1000000 bytes  
\# 1mb => 1024\*1024 bytes  
\# 1g => 1000000000 bytes  
\# 1gb => 1024\*1024\*1024 bytes  
\#  
\# units are case insensitive so 1GB 1Gb 1gB are all the same.  
  
  
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\# INCLUDES \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#  
  
  
\# Include one or more other config files here.  This is useful if you  
\# have a standard template that goes to all Redis servers but also need  
\# to customize a few per-server settings.  Include files can include  
\# other files, so use this wisely.  
\#  
\# Notice option "include" won't be rewritten by command "CONFIG REWRITE"  
\# from admin or Redis Sentinel. Since Redis always uses the last processed  
\# line as value of a configuration directive, you'd better put includes  
\# at the beginning of this file to avoid overwriting config change at runtime.  
\#  
\# If instead you are interested in using includes to override configuration  
\# options, it is better to use include as the last line.  
\#  
\# include /path/to/local.conf  
\# include /path/to/other.conf  
  
  
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\# NETWORK \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#  
  
  
\# By default, if no "bind" configuration directive is specified, Redis listens  
\# for connections from all the network interfaces available on the server.  
\# It is possible to listen to just one or multiple selected interfaces using  
\# the "bind" configuration directive, followed by one or more IP addresses.  
\#  
\# Examples:  
\#  
\# bind 192.168.1.100 10.0.0.1  
\# bind 127.0.0.1 ::1  
\#  
\# ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the  
\# internet, binding to all the interfaces is dangerous and will expose the  
\# instance to everybody on the internet. So by default we uncomment the  
\# following bind directive, that will force Redis to listen only into  
\# the IPv4 lookback interface address (this means Redis will be able to  
\# accept connections only from clients running into the same computer it  
\# is running).  
\#  
\# IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES  
\# JUST COMMENT THE FOLLOWING LINE.  
\# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
bind 192.168.99.57 127.0.0.1  
  
  
\# Protected mode is a layer of security protection, in order to avoid that  
\# Redis instances left open on the internet are accessed and exploited.  
\#  
\# When protected mode is on and if:  
\#  
\# 1) The server is not binding explicitly to a set of addresses using the  
\#    "bind" directive.  
\# 2) No password is configured.  
\#  
\# The server only accepts connections from clients connecting from the  
\# IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain  
\# sockets.  
\#  
\# By default protected mode is enabled. You should disable it only if  
\# you are sure you want clients from other hosts to connect to Redis  
\# even if no authentication is configured, nor a specific set of interfaces  
\# are explicitly listed using the "bind" directive.  
protected-mode yes  
  
  
\# Accept connections on the specified port, default is 6379 (IANA \#815344).  
\# If port 0 is specified Redis will not listen on a TCP socket.  
port 6379  
  
  
\# TCP listen() backlog.  
\#  
\# In high requests-per-second environments you need an high backlog in order  
\# to avoid slow clients connections issues. Note that the Linux kernel  
\# will silently truncate it to the value of /proc/sys/net/core/somaxconn so  
\# make sure to raise both the value of somaxconn and tcp\_max\_syn\_backlog  
\# in order to get the desired effect.  
tcp-backlog 511  
  
  
\# Unix socket.  
\#  
\# Specify the path for the Unix socket that will be used to listen for  
\# incoming connections. There is no default, so Redis will not listen  
\# on a unix socket when not specified.  
\#  
\# unixsocket /tmp/redis.sock  
\# unixsocketperm 700  
  
  
\# Close the connection after a client is idle for N seconds (0 to disable)  
timeout 0  
  
  
\# TCP keepalive.  
\#  
\# If non-zero, use SO\_KEEPALIVE to send TCP ACKs to clients in absence  
\# of communication. This is useful for two reasons:  
\#  
\# 1) Detect dead peers.  
\# 2) Take the connection alive from the point of view of network  
\#    equipment in the middle.  
\#  
\# On Linux, the specified value (in seconds) is the period used to send ACKs.  
\# Note that to close the connection the double of the time is needed.  
\# On other kernels the period depends on the kernel configuration.  
\#  
\# A reasonable value for this option is 300 seconds, which is the new  
\# Redis default starting with Redis 3.2.1.  
tcp-keepalive 300  
  
  
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\# 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 no

daemonize yes

\# If you run Redis from upstart or systemd, Redis can interact with your  
\# supervision tree. Options:  
\#   supervised no      - no supervision interaction  
\#   supervised upstart - signal upstart by putting Redis into SIGSTOP mode  
\#   supervised systemd - signal systemd by writing READY=1 to $NOTIFY\_SOCKET  
\#   supervised auto    - detect upstart or systemd method based on  
\#                        UPSTART\_JOB or NOTIFY\_SOCKET environment variables  
\# Note: these supervision methods only signal "process is ready."  
\#       They do not enable continuous liveness pings back to your supervisor.  
supervised no  
  
  
\# If a pid file is specified, Redis writes it where specified at startup  
\# and removes it at exit.  
\#  
\# When the server runs non daemonized, no pid file is created if none is  
\# specified in the configuration. When the server is daemonized, the pid file  
\# is used even if not specified, defaulting to "/var/run/redis.pid".  
\#  
\# Creating a pid file is best effort: if Redis is not able to create it  
\# nothing bad happens, the server will start and run normally.  
pidfile /var/run/redis\_6379.pid  
  
  
\# Specify the server verbosity level.  
\# This can be one of:  
\# debug (a lot of information, useful for development/testing)  
\# verbose (many rarely useful info, but not a mess like the debug level)  
\# notice (moderately verbose, what you want in production probably)  
\# warning (only very important / critical messages are logged)  
loglevel notice  
  
  
\# Specify the log file name. Also the empty string can be used to force  
\# Redis to log on the standard output. Note that if you use standard  
\# output for logging but daemonize, logs will be sent to /dev/null  
logfile ""  
  
  
\# To enable logging to the system logger, just set 'syslog-enabled' to yes,  
\# and optionally update the other syslog parameters to suit your needs.  
\# syslog-enabled no  
  
  
\# Specify the syslog identity.  
\# syslog-ident redis  
  
  
\# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.  
\# syslog-facility local0  
  
  
\# Set the number of databases. The default database is DB 0, you can select  
\# a different one on a per-connection basis using SELECT <dbid> where  
\# dbid is a number between 0 and 'databases'-1  
databases 16  
  
  
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\# SNAPSHOTTING  \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#  
\#  
\# Save the DB on disk:  
\#  
\#   save <seconds> <changes>  
\#  
\#   Will save the DB if both the given number of seconds and the given  
\#   number of write operations against the DB occurred.  
\#  
\#   In the example below the behaviour will be to save:  
\#   after 900 sec (15 min) if at least 1 key changed  
\#   after 300 sec (5 min) if at least 10 keys changed  
\#   after 60 sec if at least 10000 keys changed  
\#  
\#   Note: you can disable saving completely by commenting out all "save" lines.  
\#  
\#   It is also possible to remove all the previously configured save  
\#   points by adding a save directive with a single empty string argument  
\#   like in the following example:  
\#  
\#   save ""  
  
  
save 900 1  
save 300 10  
save 60 10000  
  
  
\# By default Redis will stop accepting writes if RDB snapshots are enabled  
\# (at least one save point) and the latest background save failed.  
\# This will make the user aware (in a hard way) that data is not persisting  
\# on disk properly, otherwise chances are that no one will notice and some  
\# disaster will happen.  
\#  
\# If the background saving process will start working again Redis will  
\# automatically allow writes again.  
\#  
\# However if you have setup your proper monitoring of the Redis server  
\# and persistence, you may want to disable this feature so that Redis will  
\# continue to work as usual even if there are problems with disk,  
\# permissions, and so forth.  
stop-writes-on-bgsave-error yes  
  
  
\# Compress string objects using LZF when dump .rdb databases?  
\# For default that's set to 'yes' as it's almost always a win.  
\# If you want to save some CPU in the saving child set it to 'no' but  
\# the dataset will likely be bigger if you have compressible values or keys.  
rdbcompression yes  
  
  
\# Since version 5 of RDB a CRC64 checksum is placed at the end of the file.  
\# This makes the format more resistant to corruption but there is a performance  
\# hit to pay (around 10%) when saving and loading RDB files, so you can disable it  
\# for maximum performances.  
\#  
\# RDB files created with checksum disabled have a checksum of zero that will  
\# tell the loading code to skip the check.  
rdbchecksum yes  
  
  
\# The filename where to dump the DB  
dbfilename dump.rdb  
  
  
\# The working directory.  
\#  
\# The DB will be written inside this directory, with the filename specified  
\# above using the 'dbfilename' configuration directive.  
\#  
\# The Append Only File will also be created inside this directory.  
\#  
\# Note that you must specify a directory here, not a file name.  
dir ./  
  
  
\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\# REPLICATION \#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#  
  
  
\# Master-Slave replication. Use slaveof to make a Redis instance a copy of  
\# another Redis server. A few things to understand ASAP about Redis replication.  
\#  
\# 1) Redis replication is asynchronous, but you can configure a master to  
\#    stop accepting writes if it appears to be not connected with at least  
\#    a given number of slaves.  
\# 2) Redis slaves are able to perform a partial resynchronization with the  
\#    master if the replication link is lost for a relatively small amount of  
\#    time. You may want to configure the replication backlog size (see the next  
\#    sections of this file) with a sensible value depending on your needs.  
\# 3) Replication is automatic and does not need user intervention. After a  
\#    network partition slaves automatically try to reconnect to masters  
\#    and resynchronize with them.  
\#  
\# slaveof <masterip> <masterport>  
  
  
\# If the master is password protected (using the "requirepass" configuration  
\# directive below) it is possible to tell the slave to authenticate before  
\# starting the replication synchronization process, otherwise the master will  
\# refuse the slave request.  
\#  
\# masterauth <master-password>  
  
  
\# When a slave loses its connection with the master, or when the replication  
\# is still in progress, the slave can act in two different ways:  
\#  
\# 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will  
\#    still reply to client requests, possibly with out of date data, or the  
\#    data set may just be empty if this is the first synchronization.  
\#  
\# 2) if slave-serve-stale-data is set to 'no' the slave will reply with  
\#    an error "SYNC with master in progress" to all the kind of commands  
\#    but to INFO and SLAVEOF.  
\#  
slave-serve-stale-data yes  
  
  
\# You can configure a slave instance to accept writes or not. Writing against  
\# a slave instance may be useful to store some ephemeral data (because data  
\# written on a slave will be easily deleted after resync with the master) but  
\# may also cause problems if clients are writing to it because of a  
\# misconfiguration.  
\#  
\# Since Redis 2.6 by default slaves are read-only.  
\#  
\# Note: read only slaves are not designed to be exposed to untrusted clients  
\# on the internet. It's just a protection layer against misuse of the instance.  
\# Still a read only slave exports by default all the administrative commands  
\# such as CONFIG, DEBUG, and so forth. To a limited extent you can improve  
\# security of read only slaves using 'rename-command' to shadow all the  
\# administrative / dangerous commands.  
slave-read-only yes  
  
  
\# Replication SYNC strategy: disk or socket.  
\#  
\# -------------------------------------------------------  
\# WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY  
\# -------------------------------------------------------  
\#  
\# New slaves and reconnecting slaves that are not able to continue the replication  
\# process just receiving differences, need to do what is called a "full  
\# synchronization". An RDB file is transmitted from the master to the slaves.  
\# The transmission can happen in two different ways:  
\#  
\# 1) Disk-backed: The Redis master creates a new process that writes the RDB  
\#                 file on disk. Later the file is transferred by the parent  
\#                 process to the slaves incrementally.  
\# 2) Diskless: The Redis master creates a new process that directly writes the  
\#              RDB file to slave sockets, without touching the disk at all.  
\#  
\# With disk-backed replication, while the RDB file is generated, more slaves  
\# can be queued and served with the RDB file as soon as the current child producing  
\# the RDB file finishes its work. With diskless replication instead once  
\# the transfer starts, new slaves arriving will be queued and a new transfer  
\# will start when the current one terminates.  
\#  
\# When diskless replication is used, the master waits a configurable amount of  
\# time (in seconds) before starting the transfer in the hope that multiple slaves  
\# will arrive and the transfer can be parallelized.  
\#  
\# With slow disks and fast (large bandwidth) networks, diskless replication  
\# works better.  
repl-diskless-sync no  
  
  
\# When diskless replication is enabled, it is possible to configure the delay  
\# the server waits in order to spawn the child that transfers the RDB via socket  
\# to the slaves.  
\#  
\# This is important since once the transfer starts, it is not possible to serve  
\# new slaves arriving, that will be queued for the next RDB transfer, so the server  
\# waits a delay in order to let more slaves arrive.  
\#  
\# The delay is specified in seconds, and by default is 5 seconds. To disable  
\# it entirely just set it to 0 seconds and the transfer will start ASAP.  
repl-diskless-sync-delay 5  
  
  
\# Slaves send PINGs to server in a predefined interval. It's possible to change  
\# this interval with the repl\_ping\_slave\_period option. The default value is 10  
\# seconds.  
\#  
\# repl-ping-slave-period 10  
  
  
\# The following option sets the replication timeout for:  
\#  
\# 1) Bulk transfer I/O during SYNC, from the point of view of slave.  
\# 2) Master timeout from the point of view of slaves (data, pings).  
\# 3) Slave timeout from the point of view of masters (REPLCONF ACK pings).  
\#  
\# It is important to make sure that this value is greater than the value  
\# specified for repl-ping-slave-period otherwise a timeout will be detected  
\# every time there is low traffic between the master and the slave.  
\#  
\# repl-timeout 60  
  
  
\# Disable TCP\_NODELAY on the slave socket after SYNC?  
\#  
\# If you select "yes" Redis will use a smaller number of TCP packets and  
\# less bandwidth to send data to slaves. But this can add a delay for  
\# the data to appear on the slave side, up to 40 milliseconds with  
\# Linux kernels using a default configuration.  
\#  
\# If you select "no" the delay for data to appear on the slave side will  
\# be reduced but more bandwidth will be used for replication.  
\#  
\# By default we optimize for low latency, but in very high traffic conditions  
\# or when the master and slaves are many hops away, turning this to "yes" may  
\# be a good idea.  
repl-disable-tcp-nodelay no  
  
  
\# Set the replication backlog size. The backlog is a buffer that accumulates  
\# slave data when slaves are disconnected for some time, so that when a slave  
\# wants to reconnect again, often a full resync is not needed, but a partial  
\# resync is enough, just passing the portion of data the slave missed while  
\# disconnected.  
\#  
\# The bigger the replication backlog, the longer the time the slave can be  
\# disconnected and later be able to perform a partial resynchronization.  
\#  
\# The backlog is only allocated once there is at least a slave connected.  
\#  
\# repl-backlog-size 1mb  
  
  
\# After a master has no longer connected slaves for some time, the backlog  
\# will be freed. The following option configures the amount of seconds that  
\# need to elapse, starting from the time the last slave disconnected, for  
\# the backlog buffer to be freed.  
\#  
\# A value of 0 means to never release the backlog.  
\#  
\# repl-backlog-ttl 3600  
  
  
\# The slave priority is an integer number published by Redis in the INFO output.  
\# It is used by Redis Sentinel in order to select a slave to promote into a  
\# master if the master is no longer working correctly.  
\#  
\# A slave with a low priority number is considered better for promotion, so  
\# for instance if there are three slaves with priority 10, 100, 25 Sentinel will  
\# pick the one with priority 10, that is the lowest.  
\#  
\# However a special priority of 0 marks the slave as not able to perform the  
\# role of master, so a slave with priority of 0 will never be selected by  
  
  
  
  
  
  
\[root@dev01 redis-3.2.3\]\# chkconfig --add redis