centos安装redis集群
当然，我会提供一个详细的步骤指南，说明如何在 CentOS 系统上使用三台服务器（IP地址分别为 10.206.0.4、10.206.0.8 和 10.206.0.13）来搭建 Redis 集群。这个集群将包括六个节点，每台服务器运行两个 Redis 实例。
步骤 1：在每台服务器上安装 Redis
对于每台服务器，执行以下步骤安装 Redis：
- 安装 Redis:
sudo yum update sudo yum install redis
步骤 2：配置 Redis 实例
在每台服务器上，为每个 Redis 实例创建并配置独立的配置文件。
-
创建配置文件目录:
sudo mkdir -p /home/redis/conf/ -
创建和编辑配置文件:
对于每个 Redis 实例，创建一个配置文件。例如，对于端口 7000 和 7001 的实例：sudo cp /etc/redis.conf /home/redis/conf/redis7000.conf sudo cp /etc/redis.conf /home/redis/conf/redis7001.conf对每个文件进行编辑，设置不同的端口号，启用集群模式等：
- 打开配置文件：
sudo vi /home/redis/conf/redis7000.conf - 设置端口为 7000（对于 redis7001.conf，设置为 7001）
- 启用集群模式：添加
cluster-enabled yes - 指定集群配置文件：
cluster-config-file nodes-7000.conf（对于 redis7001.conf，使用 nodes-7001.conf） - 设置节点超时：
cluster-node-timeout 5000 - 允许所有地址连接：
bind 0.0.0.0 - 启用 AOF 持久化：
appendonly yes
- 打开配置文件：
-
启动 Redis 实例:
使用新的配置文件启动 Redis 实例：redis-server /home/redis/conf/redis7000.conf redis-server /home/redis/conf/redis7001.conf
步骤 3：创建 Redis 集群
在其中一台服务器上执行以下步骤来初始化集群。
-
安装
ruby和redisgem (用于运行 Redis 集群创建脚本):sudo yum install ruby sudo gem install redis -
使用 redis-cli 创建集群:
运行以下命令创建集群：redis-cli --cluster create 10.206.0.4:7000 10.206.0.4:7001 10.206.0.8:7000 10.206.0.8:7001 10.206.0.13:7000 10.206.0.13:7001 --cluster-replicas 1这将创建一个六个节点的集群，每个主节点都有一个副本节点。
-
按提示确认集群创建。
步骤 4：验证和管理集群
-
验证集群状态:
连接到集群的任何一个节点，检查集群状态：redis-cli -c -p 7000 cluster nodes或者
redis-cli -c -p 7000 cluster info -
集群管理:
- 可以通过
redis-cli连接到集群的任何一个节点进行管理。 - 使用 Redis 命令进行数据操作，如设置键值对等。
- 可以通过
注意事项
- 在搭建集群之前，请确保所需端口在服务器上是开放的，并且服务器间网络互通。
- 考虑为 Redis 设置密码保护，特别是在生产环境中。
- 定期备份重要数据，并监控集群的性能和健康状况。
redis7000.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
################################## MODULES #####################################
# Load modules at startup. If the server is not able to load modules
# it will abort. It is possible to use multiple loadmodule directives.
#
# loadmodule /path/to/my_module.so
# loadmodule /path/to/other_module.so
################################## 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 loopback 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 0.0.0.0
# 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 7000
# 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 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 /var/log/redis/redis.log
# 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 where
# dbid is a number between 0 and 'databases'-1
databases 16
# By default Redis shows an ASCII art logo only when started to log to the
# standard output and if the standard output is a TTY. Basically this means
# that normally a logo is displayed only in interactive sessions.
#
# However it is possible to force the pre-4.0 behavior and always show a
# ASCII art logo in startup logs by setting the following option to yes.
always-show-logo yes
################################ SNAPSHOTTING ################################
#
# Save the DB on disk:
#
# save
#
# 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 /var/lib/redis
################################# REPLICATION #################################
# Master-Replica replication. Use replicaof to make a Redis instance a copy of
# another Redis server. A few things to understand ASAP about Redis replication.
#
# +------------------+ +---------------+
# | Master | ---> | Replica |
# | (receive writes) | | (exact copy) |
# +------------------+ +---------------+
#
# 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 replicas.
# 2) Redis replicas 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 replicas automatically try to reconnect to masters
# and resynchronize with them.
#
# replicaof
# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the replica to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the replica request.
#
# masterauth before processing any other
# commands. This might be useful in environments in which you do not trust
# others with access to the host running redis-server.
#
# This should stay commented out for backward compatibility and because most
# people do not need auth (e.g. they run their own servers).
#
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#
# requirepass foobared
# Command renaming.
#
# It is possible to change the name of dangerous commands in a shared
# environment. For instance the CONFIG command may be renamed into something
# hard to guess so that it will still be available for internal-use tools
# but not available for general clients.
#
# Example:
#
# rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
#
# It is also possible to completely kill a command by renaming it into
# an empty string:
#
# rename-command CONFIG ""
#
# Please note that changing the name of commands that are logged into the
# AOF file or transmitted to replicas may cause problems.
################################### CLIENTS ####################################
# Set the max number of connected clients at the same time. By default
# this limit is set to 10000 clients, however if the Redis server is not
# able to configure the process file limit to allow for the specified limit
# the max number of allowed clients is set to the current file limit
# minus 32 (as Redis reserves a few file descriptors for internal uses).
#
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 10000
############################## MEMORY MANAGEMENT ################################
# Set a memory usage limit to the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys
# according to the eviction policy selected (see maxmemory-policy).
#
# If Redis can't remove keys according to the policy, or if the policy is
# set to 'noeviction', Redis will start to reply with errors to commands
# that would use more memory, like SET, LPUSH, and so on, and will continue
# to reply to read-only commands like GET.
#
# This option is usually useful when using Redis as an LRU or LFU cache, or to
# set a hard memory limit for an instance (using the 'noeviction' policy).
#
# WARNING: If you have replicas attached to an instance with maxmemory on,
# the size of the output buffers needed to feed the replicas are subtracted
# from the used memory count, so that network problems / resyncs will
# not trigger a loop where keys are evicted, and in turn the output
# buffer of replicas is full with DELs of keys evicted triggering the deletion
# of more keys, and so forth until the database is completely emptied.
#
# In short... if you have replicas attached it is suggested that you set a lower
# limit for maxmemory so that there is some free RAM on the system for replica
# output buffers (but this is not needed if the policy is 'noeviction').
#
# maxmemory " if needed.
latency-monitor-threshold 0
############################# EVENT NOTIFICATION ##############################
# Redis can notify Pub/Sub clients about events happening in the key space.
# This feature is documented at http://redis.io/topics/notifications
#
# For instance if keyspace events notification is enabled, and a client
# performs a DEL operation on key "foo" stored in the Database 0, two
# messages will be published via Pub/Sub:
#
# PUBLISH __keyspace@0__:foo del
# PUBLISH __keyevent@0__:del foo
#
# It is possible to select the events that Redis will notify among a set
# of classes. Every class is identified by a single character:
#
# K Keyspace events, published with __keyspace@__ prefix.
# E Keyevent events, published with __keyevent@__ prefix.
# g Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
# $ String commands
# l List commands
# s Set commands
# h Hash commands
# z Sorted set commands
# x Expired events (events generated every time a key expires)
# e Evicted events (events generated when a key is evicted for maxmemory)
# A Alias for g$lshzxe, so that the "AKE" string means all the events.
#
# The "notify-keyspace-events" takes as argument a string that is composed
# of zero or multiple characters. The empty string means that notifications
# are disabled.
#
# Example: to enable list and generic events, from the point of view of the
# event name, use:
#
# notify-keyspace-events Elg
#
# Example 2: to get the stream of the expired keys subscribing to channel
# name __keyevent@0__:expired use:
#
# notify-keyspace-events Ex
#
# By default all notifications are disabled because most users don't need
# this feature and the feature has some overhead. Note that if you don't
# specify at least one of K or E, no events will be delivered.
notify-keyspace-events ""
############################### ADVANCED CONFIG ###############################
# Hashes are encoded using a memory efficient data structure when they have a
# small number of entries, and the biggest entry does not exceed a given
# threshold. These thresholds can be configured using the following directives.
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
# Lists are also encoded in a special way to save a lot of space.
# The number of entries allowed per internal list node can be specified
# as a fixed maximum size or a maximum number of elements.
# For a fixed maximum size, use -5 through -1, meaning:
# -5: max size: 64 Kb <-- not recommended for normal workloads
# -4: max size: 32 Kb <-- not recommended
# -3: max size: 16 Kb <-- probably not recommended
# -2: max size: 8 Kb <-- good
# -1: max size: 4 Kb <-- good
# Positive numbers mean store up to _exactly_ that number of elements
# per list node.
# The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
# but if your use case is unique, adjust the settings as necessary.
list-max-ziplist-size -2
# Lists may also be compressed.
# Compress depth is the number of quicklist ziplist nodes from *each* side of
# the list to *exclude* from compression. The head and tail of the list
# are always uncompressed for fast push/pop operations. Settings are:
# 0: disable all list compression
# 1: depth 1 means "don't start compressing until after 1 node into the list,
# going from either the head or tail"
# So: [head]->node->node->...->node->[tail]
# [head], [tail] will always be uncompressed; inner nodes will compress.
# 2: [head]->[next]->node->node->...->node->[prev]->[tail]
# 2 here means: don't compress head or head->next or tail->prev or tail,
# but compress all nodes between them.
# 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
# etc.
list-compress-depth 0
# Sets have a special encoding in just one case: when a set is composed
# of just strings that happen to be integers in radix 10 in the range
# of 64 bit signed integers.
# The following configuration setting sets the limit in the size of the
# set in order to use this special memory saving encoding.
set-max-intset-entries 512
# Similarly to hashes and lists, sorted sets are also specially encoded in
# order to save a lot of space. This encoding is only used when the length and
# elements of a sorted set are below the following limits:
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
# HyperLogLog sparse representation bytes limit. The limit includes the
# 16 bytes header. When an HyperLogLog using the sparse representation crosses
# this limit, it is converted into the dense representation.
#
# A value greater than 16000 is totally useless, since at that point the
# dense representation is more memory efficient.
#
# The suggested value is ~ 3000 in order to have the benefits of
# the space efficient encoding without slowing down too much PFADD,
# which is O(N) with the sparse encoding. The value can be raised to
# ~ 10000 when CPU is not a concern, but space is, and the data set is
# composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
hll-sparse-max-bytes 3000
# Streams macro node max size / items. The stream data structure is a radix
# tree of big nodes that encode multiple items inside. Using this configuration
# it is possible to configure how big a single node can be in bytes, and the
# maximum number of items it may contain before switching to a new node when
# appending new stream entries. If any of the following settings are set to
# zero, the limit is ignored, so for instance it is possible to set just a
# max entires limit by setting max-bytes to 0 and max-entries to the desired
# value.
stream-node-max-bytes 4096
stream-node-max-entries 100
# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
# order to help rehashing the main Redis hash table (the one mapping top-level
# keys to values). The hash table implementation Redis uses (see dict.c)
# performs a lazy rehashing: the more operation you run into a hash table
# that is rehashing, the more rehashing "steps" are performed, so if the
# server is idle the rehashing is never complete and some more memory is used
# by the hash table.
#
# The default is to use this millisecond 10 times every second in order to
# actively rehash the main dictionaries, freeing memory when possible.
#
# If unsure:
# use "activerehashing no" if you have hard latency requirements and it is
# not a good thing in your environment that Redis can reply from time to time
# to queries with 2 milliseconds delay.
#
# use "activerehashing yes" if you don't have such hard requirements but
# want to free memory asap when possible.
activerehashing yes
# The client output buffer limits can be used to force disconnection of clients
# that are not reading data from the server fast enough for some reason (a
# common reason is that a Pub/Sub client can't consume messages as fast as the
# publisher can produce them).
#
# The limit can be set differently for the three different classes of clients:
#
# normal -> normal clients including MONITOR clients
# replica -> replica clients
# pubsub -> clients subscribed to at least one pubsub channel or pattern
#
# The syntax of every client-output-buffer-limit directive is the following:
#
# client-output-buffer-limit
#
# A client is immediately disconnected once the hard limit is reached, or if
# the soft limit is reached and remains reached for the specified number of
# seconds (continuously).
# So for instance if the hard limit is 32 megabytes and the soft limit is
# 16 megabytes / 10 seconds, the client will get disconnected immediately
# if the size of the output buffers reach 32 megabytes, but will also get
# disconnected if the client reaches 16 megabytes and continuously overcomes
# the limit for 10 seconds.
#
# By default normal clients are not limited because they don't receive data
# without asking (in a push way), but just after a request, so only
# asynchronous clients may create a scenario where data is requested faster
# than it can read.
#
# Instead there is a default limit for pubsub and replica clients, since
# subscribers and replicas receive data in a push fashion.
#
# Both the hard or the soft limit can be disabled by setting them to zero.
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit replica 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
# Client query buffers accumulate new commands. They are limited to a fixed
# amount by default in order to avoid that a protocol desynchronization (for
# instance due to a bug in the client) will lead to unbound memory usage in
# the query buffer. However you can configure it here if you have very special
# needs, such us huge multi/exec requests or alike.
#
# client-query-buffer-limit 1gb
# In the Redis protocol, bulk requests, that are, elements representing single
# strings, are normally limited ot 512 mb. However you can change this limit
# here.
#
# proto-max-bulk-len 512mb
# Redis calls an internal function to perform many background tasks, like
# closing connections of clients in timeout, purging expired keys that are
# never requested, and so forth.
#
# Not all tasks are performed with the same frequency, but Redis checks for
# tasks to perform according to the specified "hz" value.
#
# By default "hz" is set to 10. Raising the value will use more CPU when
# Redis is idle, but at the same time will make Redis more responsive when
# there are many keys expiring at the same time, and timeouts may be
# handled with more precision.
#
# The range is between 1 and 500, however a value over 100 is usually not
# a good idea. Most users should use the default of 10 and raise this up to
# 100 only in environments where very low latency is required.
hz 10
# Normally it is useful to have an HZ value which is proportional to the
# number of clients connected. This is useful in order, for instance, to
# avoid too many clients are processed for each background task invocation
# in order to avoid latency spikes.
#
# Since the default HZ value by default is conservatively set to 10, Redis
# offers, and enables by default, the ability to use an adaptive HZ value
# which will temporary raise when there are many connected clients.
#
# When dynamic HZ is enabled, the actual configured HZ will be used as
# as a baseline, but multiples of the configured HZ value will be actually
# used as needed once more clients are connected. In this way an idle
# instance will use very little CPU time while a busy instance will be
# more responsive.
dynamic-hz yes
# When a child rewrites the AOF file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
aof-rewrite-incremental-fsync yes
# When redis saves RDB file, if the following option is enabled
# the file will be fsync-ed every 32 MB of data generated. This is useful
# in order to commit the file to the disk more incrementally and avoid
# big latency spikes.
rdb-save-incremental-fsync yes
# Redis LFU eviction (see maxmemory setting) can be tuned. However it is a good
# idea to start with the default settings and only change them after investigating
# how to improve the performances and how the keys LFU change over time, which
# is possible to inspect via the OBJECT FREQ command.
#
# There are two tunable parameters in the Redis LFU implementation: the
# counter logarithm factor and the counter decay time. It is important to
# understand what the two parameters mean before changing them.
#
# The LFU counter is just 8 bits per key, it's maximum value is 255, so Redis
# uses a probabilistic increment with logarithmic behavior. Given the value
# of the old counter, when a key is accessed, the counter is incremented in
# this way:
#
# 1. A random number R between 0 and 1 is extracted.
# 2. A probability P is calculated as 1/(old_value*lfu_log_factor+1).
# 3. The counter is incremented only if R < P.
#
# The default lfu-log-factor is 10. This is a table of how the frequency
# counter changes with a different number of accesses with different
# logarithmic factors:
#
# +--------+------------+------------+------------+------------+------------+
# | factor | 100 hits | 1000 hits | 100K hits | 1M hits | 10M hits |
# +--------+------------+------------+------------+------------+------------+
# | 0 | 104 | 255 | 255 | 255 | 255 |
# +--------+------------+------------+------------+------------+------------+
# | 1 | 18 | 49 | 255 | 255 | 255 |
# +--------+------------+------------+------------+------------+------------+
# | 10 | 10 | 18 | 142 | 255 | 255 |
# +--------+------------+------------+------------+------------+------------+
# | 100 | 8 | 11 | 49 | 143 | 255 |
# +--------+------------+------------+------------+------------+------------+
#
# NOTE: The above table was obtained by running the following commands:
#
# redis-benchmark -n 1000000 incr foo
# redis-cli object freq foo
#
# NOTE 2: The counter initial value is 5 in order to give new objects a chance
# to accumulate hits.
#
# The counter decay time is the time, in minutes, that must elapse in order
# for the key counter to be divided by two (or decremented if it has a value
# less <= 10).
#
# The default value for the lfu-decay-time is 1. A Special value of 0 means to
# decay the counter every time it happens to be scanned.
#
# lfu-log-factor 10
# lfu-decay-time 1
########################### ACTIVE DEFRAGMENTATION #######################
#
# WARNING THIS FEATURE IS EXPERIMENTAL. However it was stress tested
# even in production and manually tested by multiple engineers for some
# time.
#
# What is active defragmentation?
# -------------------------------
#
# Active (online) defragmentation allows a Redis server to compact the
# spaces left between small allocations and deallocations of data in memory,
# thus allowing to reclaim back memory.
#
# Fragmentation is a natural process that happens with every allocator (but
# less so with Jemalloc, fortunately) and certain workloads. Normally a server
# restart is needed in order to lower the fragmentation, or at least to flush
# away all the data and create it again. However thanks to this feature
# implemented by Oran Agra for Redis 4.0 this process can happen at runtime
# in an "hot" way, while the server is running.
#
# Basically when the fragmentation is over a certain level (see the
# configuration options below) Redis will start to create new copies of the
# values in contiguous memory regions by exploiting certain specific Jemalloc
# features (in order to understand if an allocation is causing fragmentation
# and to allocate it in a better place), and at the same time, will release the
# old copies of the data. This process, repeated incrementally for all the keys
# will cause the fragmentation to drop back to normal values.
#
# Important things to understand:
#
# 1. This feature is disabled by default, and only works if you compiled Redis
# to use the copy of Jemalloc we ship with the source code of Redis.
# This is the default with Linux builds.
#
# 2. You never need to enable this feature if you don't have fragmentation
# issues.
#
# 3. Once you experience fragmentation, you can enable this feature when
# needed with the command "CONFIG SET activedefrag yes".
#
# The configuration parameters are able to fine tune the behavior of the
# defragmentation process. If you are not sure about what they mean it is
# a good idea to leave the defaults untouched.
# Enabled active defragmentation
# activedefrag yes
# Minimum amount of fragmentation waste to start active defrag
# active-defrag-ignore-bytes 100mb
# Minimum percentage of fragmentation to start active defrag
# active-defrag-threshold-lower 10
# Maximum percentage of fragmentation at which we use maximum effort
# active-defrag-threshold-upper 100
# Minimal effort for defrag in CPU percentage
# active-defrag-cycle-min 5
# Maximal effort for defrag in CPU percentage
# active-defrag-cycle-max 75
# Maximum number of set/hash/zset/list fields that will be processed from
# the main dictionary scan
# active-defrag-max-scan-fields 1000
机器安装步骤
Welcome to TencentOS 3 64bit
Version 3.1 20230621
tlinux3.1-64bit-5.4.119-19.0009.28-20230621
Last failed login: Sat Jan 20 15:11:25 CST 2024 from 139.59.16.139 on ssh:notty
There were 26600 failed login attempts since the last successful login.
Last login: Sun Jan 7 16:09:34 2024 from 114.84.30.36
[root@master ~]# sudo yum update
Repository docker-ce-stable is listed more than once in the configuration
Repository docker-ce-stable-source is listed more than once in the configuration
Repository docker-ce-test is listed more than once in the configuration
Repository docker-ce-test-source is listed more than once in the configuration
TencentOS Server 3.1 - TencentOS 46 kB/s | 3.8 kB 00:00
TencentOS Server 3.1 - Updates 48 kB/s | 3.8 kB 00:00
TencentOS Server 3.1 - Updates 16 MB/s | 30 MB 00:01
TencentOS Server 3.1 - TencentOS-AppStream 49 kB/s | 4.2 kB 00:00
TencentOS Server 3.1 - TencentOS-AppStream 17 MB/s | 20 MB 00:01
TencentOS Server 3.1 - Base 35 kB/s | 3.0 kB 00:00
TencentOS Server 3.1 - AppStream 37 kB/s | 2.9 kB 00:00
TencentOS Server 3.1 - Extras 37 kB/s | 3.0 kB 00:00
TencentOS Server 3.1 - Extras 139 kB/s | 25 kB 00:00
TencentOS Server 3.1 - PowerTools 35 kB/s | 3.0 kB 00:00
Docker CE Stable - x86_64 45 kB/s | 3.5 kB 00:00
Extra Packages for TencentOS Server 3.1 - x86_64 247 kB/s | 4.7 kB 00:00
Extra Packages for TencentOS Server 3.1 - x86_64 34 MB/s | 16 MB 00:00
Extra Packages for TencentOS Server 3.1 Modular - x86_64 148 kB/s | 3.0 kB 00:00
Kubernetes 62 kB/s | 1.4 kB 00:00
Error:
Problem: cannot install both kubelet-1.28.2-0.x86_64 and kubelet-1.18.4-0.x86_64
- cannot install the best update candidate for package kubernetes-cni-1.2.0-0.x86_64
- cannot install the best update candidate for package kubelet-1.26.0-0.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
[root@master ~]# sudo yum install redis
Repository docker-ce-stable is listed more than once in the configuration
Repository docker-ce-stable-source is listed more than once in the configuration
Repository docker-ce-test is listed more than once in the configuration
Repository docker-ce-test-source is listed more than once in the configuration
Last metadata expiration check: 0:00:06 ago on Sat 20 Jan 2024 03:14:51 PM CST.
Dependencies resolved.
=========================================================================================================================================================
Package Architecture Version Repository Size
=========================================================================================================================================================
Installing:
redis x86_64 5.0.3-5.module+el8.6.0+196+2fe2d5b8 TencentOS-AppStream 925 k
Enabling module streams:
redis 5
Transaction Summary
=========================================================================================================================================================
Install 1 Package
Total download size: 925 k
Installed size: 3.2 M
Is this ok [y/N]: y
Downloading Packages:
redis-5.0.3-5.module+el8.6.0+196+2fe2d5b8.x86_64.rpm 2.0 MB/s | 925 kB 00:00
---------------------------------------------------------------------------------------------------------------------------------------------------------
Total 2.0 MB/s | 925 kB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: redis-5.0.3-5.module+el8.6.0+196+2fe2d5b8.x86_64 1/1
Installing : redis-5.0.3-5.module+el8.6.0+196+2fe2d5b8.x86_64 1/1
Running scriptlet: redis-5.0.3-5.module+el8.6.0+196+2fe2d5b8.x86_64 1/1
Verifying : redis-5.0.3-5.module+el8.6.0+196+2fe2d5b8.x86_64 1/1
Installed:
redis-5.0.3-5.module+el8.6.0+196+2fe2d5b8.x86_64
Complete!
[root@master ~]# sudo mkdir -p /home/redis/conf/
[root@master ~]# ls
Changelog
[root@master ~]# cd /home
[root@master home]# ls
redis
[root@master home]# cd redis/
[root@master redis]# ls
conf
[root@master redis]# cd conf/
[root@master conf]# scp [email protected]:/home/redis/conf/7000.conf .
The authenticity of host '10.206.0.13 (10.206.0.13)' can't be established.
ECDSA key fingerprint is SHA256:kCk++fRif8cOYBpWe98waBTWL/L2Wob0SWezO5e5TgE.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '10.206.0.13' (ECDSA) to the list of known hosts.
[email protected]'s password:
Permission denied, please try again.
[email protected]'s password:
scp: /home/redis/conf/7000.conf: No such file or directory
[root@master conf]# scp [email protected]:/home/redis/conf/redis7000.conf .
[email protected]'s password:
redis7000.conf 100% 61KB 67.9MB/s 00:00
[root@master conf]# scp [email protected]:/home/redis/conf/redis7001.conf .
[email protected]'s password:
redis7001.conf 100% 61KB 72.4MB/s 00:00
[root@master conf]# ls
redis7000.conf redis7001.conf
[root@master conf]# redis-server /home/redis/conf/redis7000.conf
[root@master conf]# redis-server /home/redis/conf/redis7001.conf
[root@master conf]# sudo yum install ruby
Repository docker-ce-stable is listed more than once in the configuration
Repository docker-ce-stable-source is listed more than once in the configuration
Repository docker-ce-test is listed more than once in the configuration
Repository docker-ce-test-source is listed more than once in the configuration
Last metadata expiration check: 0:57:10 ago on Sat 20 Jan 2024 03:14:51 PM CST.
Dependencies resolved.
=========================================================================================================================================================
Package Architecture Version Repository Size
=========================================================================================================================================================
Installing:
ruby x86_64 2.5.9-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 87 k
Installing dependencies:
ruby-irb noarch 2.5.9-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 102 k
ruby-libs x86_64 2.5.9-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 2.9 M
rubygem-json x86_64 2.1.0-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 91 k
rubygem-psych x86_64 3.0.2-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 95 k
Installing weak dependencies:
rubygem-bigdecimal x86_64 1.3.4-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 97 k
rubygem-did_you_mean noarch 1.2.0-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 81 k
rubygem-io-console x86_64 0.4.6-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 67 k
rubygem-openssl x86_64 2.1.2-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 190 k
rubygem-rdoc noarch 6.0.1.1-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 456 k
rubygems noarch 2.7.6.3-111.module+el8.8.0+556+0441a7bb TencentOS-AppStream 308 k
Enabling module streams:
ruby 2.5
Transaction Summary
=========================================================================================================================================================
Install 11 Packages
Total download size: 4.5 M
Installed size: 14 M
Is this ok [y/N]: y
Is this ok [y/N]: y
Downloading Packages:
(1/11): ruby-irb-2.5.9-111.module+el8.8.0+556+0441a7bb.noarch.rpm 574 kB/s | 102 kB 00:00
(2/11): ruby-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64.rpm 474 kB/s | 87 kB 00:00
(3/11): rubygem-bigdecimal-1.3.4-111.module+el8.8.0+556+0441a7bb.x86_64.rpm 566 kB/s | 97 kB 00:00
(4/11): rubygem-did_you_mean-1.2.0-111.module+el8.8.0+556+0441a7bb.noarch.rpm 422 kB/s | 81 kB 00:00
(5/11): rubygem-io-console-0.4.6-111.module+el8.8.0+556+0441a7bb.x86_64.rpm 482 kB/s | 67 kB 00:00
(6/11): rubygem-json-2.1.0-111.module+el8.8.0+556+0441a7bb.x86_64.rpm 567 kB/s | 91 kB 00:00
(7/11): ruby-libs-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64.rpm 4.3 MB/s | 2.9 MB 00:00
(8/11): rubygem-openssl-2.1.2-111.module+el8.8.0+556+0441a7bb.x86_64.rpm 876 kB/s | 190 kB 00:00
(9/11): rubygem-psych-3.0.2-111.module+el8.8.0+556+0441a7bb.x86_64.rpm 473 kB/s | 95 kB 00:00
(10/11): rubygems-2.7.6.3-111.module+el8.8.0+556+0441a7bb.noarch.rpm 1.1 MB/s | 308 kB 00:00
(11/11): rubygem-rdoc-6.0.1.1-111.module+el8.8.0+556+0441a7bb.noarch.rpm 1.2 MB/s | 456 kB 00:00
---------------------------------------------------------------------------------------------------------------------------------------------------------
Total 4.2 MB/s | 4.5 MB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : ruby-libs-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64 1/11
Installing : ruby-irb-2.5.9-111.module+el8.8.0+556+0441a7bb.noarch 2/11
Installing : rubygem-bigdecimal-1.3.4-111.module+el8.8.0+556+0441a7bb.x86_64 3/11
Installing : rubygem-did_you_mean-1.2.0-111.module+el8.8.0+556+0441a7bb.noarch 4/11
Installing : rubygem-io-console-0.4.6-111.module+el8.8.0+556+0441a7bb.x86_64 5/11
Installing : rubygem-json-2.1.0-111.module+el8.8.0+556+0441a7bb.x86_64 6/11
Installing : rubygem-openssl-2.1.2-111.module+el8.8.0+556+0441a7bb.x86_64 7/11
Installing : rubygem-psych-3.0.2-111.module+el8.8.0+556+0441a7bb.x86_64 8/11
Installing : rubygem-rdoc-6.0.1.1-111.module+el8.8.0+556+0441a7bb.noarch 9/11
Installing : rubygems-2.7.6.3-111.module+el8.8.0+556+0441a7bb.noarch 10/11
Installing : ruby-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64 11/11
Running scriptlet: ruby-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64 11/11
Verifying : ruby-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64 1/11
Verifying : ruby-irb-2.5.9-111.module+el8.8.0+556+0441a7bb.noarch 2/11
Verifying : ruby-libs-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64 3/11
Verifying : rubygem-bigdecimal-1.3.4-111.module+el8.8.0+556+0441a7bb.x86_64 4/11
Verifying : rubygem-did_you_mean-1.2.0-111.module+el8.8.0+556+0441a7bb.noarch 5/11
Verifying : rubygem-io-console-0.4.6-111.module+el8.8.0+556+0441a7bb.x86_64 6/11
Verifying : rubygem-json-2.1.0-111.module+el8.8.0+556+0441a7bb.x86_64 7/11
Verifying : rubygem-openssl-2.1.2-111.module+el8.8.0+556+0441a7bb.x86_64 8/11
Verifying : rubygem-psych-3.0.2-111.module+el8.8.0+556+0441a7bb.x86_64 9/11
Verifying : rubygem-rdoc-6.0.1.1-111.module+el8.8.0+556+0441a7bb.noarch 10/11
Verifying : rubygems-2.7.6.3-111.module+el8.8.0+556+0441a7bb.noarch 11/11
Installed:
ruby-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64 ruby-irb-2.5.9-111.module+el8.8.0+556+0441a7bb.noarch
ruby-libs-2.5.9-111.module+el8.8.0+556+0441a7bb.x86_64 rubygem-bigdecimal-1.3.4-111.module+el8.8.0+556+0441a7bb.x86_64
rubygem-did_you_mean-1.2.0-111.module+el8.8.0+556+0441a7bb.noarch rubygem-io-console-0.4.6-111.module+el8.8.0+556+0441a7bb.x86_64
rubygem-json-2.1.0-111.module+el8.8.0+556+0441a7bb.x86_64 rubygem-openssl-2.1.2-111.module+el8.8.0+556+0441a7bb.x86_64
rubygem-psych-3.0.2-111.module+el8.8.0+556+0441a7bb.x86_64 rubygem-rdoc-6.0.1.1-111.module+el8.8.0+556+0441a7bb.noarch
rubygems-2.7.6.3-111.module+el8.8.0+556+0441a7bb.noarch
Complete！
[root@master conf]# sudo gem install redis
^CERROR: Interrupted
[root@master conf]# sudo gem install redis
^CERROR: Interrupted
[root@master conf]# gem sources --add https://gems.ruby-china.com/ --remove https://rubygems.org/
https://gems.ruby-china.com/ added to sources
https://rubygems.org/ removed from sources
[root@master conf]#
[root@master conf]# sudo gem install redis
Fetching: connection_pool-2.4.1.gem (100%)
Successfully installed connection_pool-2.4.1
Fetching: redis-client-0.19.1.gem (100%)
Successfully installed redis-client-0.19.1
Fetching: redis-5.0.8.gem (100%)
Successfully installed redis-5.0.8
3 gems installed
[root@master conf]# redis-cli --cluster create 10.206.0.4:7000 10.206.0.4:7001 10.206.0.8:7000 10.206.0.8:7001 10.206.0.13:7000 10.206.0.13:7001 --cluster-replicas 1
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
Adding replica 10.206.0.8:7001 to 10.206.0.4:7000
Adding replica 10.206.0.4:7001 to 10.206.0.8:7000
Adding replica 10.206.0.13:7001 to 10.206.0.13:7000
>>> Trying to optimize slaves allocation for anti-affinity
[OK] Perfect anti-affinity obtained!
M: 774e6ed6f9982176be45bbbf89a105257ab2ecb7 10.206.0.4:7000
slots:[0-5460] (5461 slots) master
S: bc9e8d8a9ef5dfa18ae798e58943fc79459fd065 10.206.0.4:7001
replicates c5d14a0a512790b5e5cfa077871de0a1d1d29d54
M: c5d14a0a512790b5e5cfa077871de0a1d1d29d54 10.206.0.8:7000
slots:[5461-10922] (5462 slots) master
S: b1aed60de8875e05db04e1c2d963ade9de87f5bf 10.206.0.8:7001
replicates f7488d141611784206d1221e713fc4aa86964844
M: f7488d141611784206d1221e713fc4aa86964844 10.206.0.13:7000
slots:[10923-16383] (5461 slots) master
S: 1b0bc4a3b7ca6b985b9496df6ab0f2e1d8306d38 10.206.0.13:7001
replicates 774e6ed6f9982176be45bbbf89a105257ab2ecb7
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
....
>>> Performing Cluster Check (using node 10.206.0.4:7000)
M: 774e6ed6f9982176be45bbbf89a105257ab2ecb7 10.206.0.4:7000
slots:[0-5460] (5461 slots) master
1 additional replica(s)
S: b1aed60de8875e05db04e1c2d963ade9de87f5bf 10.206.0.8:7001
slots: (0 slots) slave
replicates f7488d141611784206d1221e713fc4aa86964844
S: bc9e8d8a9ef5dfa18ae798e58943fc79459fd065 10.206.0.4:7001
slots: (0 slots) slave
replicates c5d14a0a512790b5e5cfa077871de0a1d1d29d54
M: f7488d141611784206d1221e713fc4aa86964844 10.206.0.13:7000
slots:[10923-16383] (5461 slots) master
1 additional replica(s)
M: c5d14a0a512790b5e5cfa077871de0a1d1d29d54 10.206.0.8:7000
slots:[5461-10922] (5462 slots) master
1 additional replica(s)
S: 1b0bc4a3b7ca6b985b9496df6ab0f2e1d8306d38 10.206.0.13:7001
slots: (0 slots) slave
replicates 774e6ed6f9982176be45bbbf89a105257ab2ecb7
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
[root@master conf]# redis-cli -c -p 7000 cluster nodes
b1aed60de8875e05db04e1c2d963ade9de87f5bf 10.206.0.8:7001@17001 slave f7488d141611784206d1221e713fc4aa86964844 0 1705738589736 5 connected
bc9e8d8a9ef5dfa18ae798e58943fc79459fd065 10.206.0.4:7001@17001 slave c5d14a0a512790b5e5cfa077871de0a1d1d29d54 0 1705738588735 3 connected
f7488d141611784206d1221e713fc4aa86964844 10.206.0.13:7000@17000 master - 0 1705738588000 5 connected 10923-16383
774e6ed6f9982176be45bbbf89a105257ab2ecb7 10.206.0.4:7000@17000 myself,master - 0 1705738587000 1 connected 0-5460
c5d14a0a512790b5e5cfa077871de0a1d1d29d54 10.206.0.8:7000@17000 master - 0 1705738590737 3 connected 5461-10922
1b0bc4a3b7ca6b985b9496df6ab0f2e1d8306d38 10.206.0.13:7001@17001 slave 774e6ed6f9982176be45bbbf89a105257ab2ecb7 0 1705738588000 6 connected
[root@master conf]# redis-cli -c -p 7000 cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_ping_sent:26
cluster_stats_messages_pong_sent:28
cluster_stats_messages_sent:54
cluster_stats_messages_ping_received:23
cluster_stats_messages_pong_received:26
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:54
[root@master conf]#