首页 > 代码库 > mac搭建redis环境

mac搭建redis环境

一、redis简介

  redis是一个key-value存储系统。和Memcached类似,它支持存储的value类型相对更多,包括string(字符串)、list(链表)、set(集合)、zset(sorted set --有序集合)和hash(哈希类型)。这些数据类型都支持push/pop、add/remove及取交集并集和差集及更丰富的操作,而且这些操作都是原子性的。在此基础上,redis支持各种不同方式的排序。与memcached一样,为了保证效率,数据都是缓存在内存中。区别的是redis会周期性的把更新的数据写入磁盘或者把修改操作写入追加的记录文件,并且在此基础上实现了master-slave(主从)同步。
  Redis 是一个高性能的key-value数据库。 redis的出现,很大程度补偿了memcached这类key/value存储的不足,在部 分场合可以对关系数据库起到很好的补充作用。它提供了Java,C/C++,C#,PHP,JavaScript,Perl,Object-C,Python,Ruby,Erlang等客户端,使用很方便。(转自百度百科)

二、redis环境搭建

  2.1 redis下载安装

  1、首先到官网下载redis,当前最新的版本应该是3.2.4,下载当时最新的稳定版本即可;

  官网地址:http://redis.io

  2、将下载下来的压缩文件拷贝到/usr/local/目录下;

  sudo cp redis-3.2.4.tar.gz

  3、进入redis-3.2.4目录;

  4、编译测试:sudo make test

  正常情况下应该是这样的:

技术分享

  5、redis安装:sudo make install

  至此完全安装成功,下面来说一下redis的配置

 --------------------------------------------------------------------------

  2.2 redis配置

  1、在/usr/local目录下创建三个文件夹,包括bin,etc,db三个目录,如果已有就直接用吧

  sudo mkdir /usr/local/bin

  sudo mkdir /usr/local/etc

  sudo mkdir /usr/local/db

  2、进入/usr/local/etc/文件夹,创建redis文件夹,并创建redis.conf配置文件,也可以把安装目录下(即之前解压缩的/usr/local/redis-3.2.4/redis.conf)复制过来,再进行修改;

  3、修改redis.conf配置文件,主要注意的是配置一下ip地址(如果配成127.0.0.1,那么默认只能本机访问redis服务器,如果需要其他局域网内机器或外网机器进行访问时,请配置成当前机器的ip地址),超时时间,日志文件位置等等。具体内容可以在网上搜索redis配置文件每一个含义,这里就不一一解释了。

技术分享
   1 # Redis configuration file example.
   2 #
   3 # Note that in order to read the configuration file, Redis must be
   4 # started with the file path as first argument:
   5 #
   6 # ./redis-server /path/to/redis.conf
   7 
   8 # Note on units: when memory size is needed, it is possible to specify
   9 # it in the usual form of 1k 5GB 4M and so forth:
  10 #
  11 # 1k => 1000 bytes
  12 # 1kb => 1024 bytes
  13 # 1m => 1000000 bytes
  14 # 1mb => 1024*1024 bytes
  15 # 1g => 1000000000 bytes
  16 # 1gb => 1024*1024*1024 bytes
  17 #
  18 # units are case insensitive so 1GB 1Gb 1gB are all the same.
  19 
  20 ################################## INCLUDES ###################################
  21 
  22 # Include one or more other config files here.  This is useful if you
  23 # have a standard template that goes to all Redis servers but also need
  24 # to customize a few per-server settings.  Include files can include
  25 # other files, so use this wisely.
  26 #
  27 # Notice option "include" wont be rewritten by command "CONFIG REWRITE"
  28 # from admin or Redis Sentinel. Since Redis always uses the last processed
  29 # line as value of a configuration directive, youd better put includes
  30 # at the beginning of this file to avoid overwriting config change at runtime.
  31 #
  32 # If instead you are interested in using includes to override configuration
  33 # options, it is better to use include as the last line.
  34 #
  35 # include /path/to/local.conf
  36 # include /path/to/other.conf
  37 
  38 ################################## NETWORK #####################################
  39 
  40 # By default, if no "bind" configuration directive is specified, Redis listens
  41 # for connections from all the network interfaces available on the server.
  42 # It is possible to listen to just one or multiple selected interfaces using
  43 # the "bind" configuration directive, followed by one or more IP addresses.
  44 #
  45 # Examples:
  46 #
  47 # bind 192.168.1.100 10.0.0.1
  48 # bind 127.0.0.1 ::1
  49 #
  50 # ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
  51 # internet, binding to all the interfaces is dangerous and will expose the
  52 # instance to everybody on the internet. So by default we uncomment the
  53 # following bind directive, that will force Redis to listen only into
  54 # the IPv4 lookback interface address (this means Redis will be able to
  55 # accept connections only from clients running into the same computer it
  56 # is running).
  57 #
  58 # IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
  59 # JUST COMMENT THE FOLLOWING LINE.
  60 # ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  61 # bind 127.0.0.1
  62 
  63 bind 121.49.107.233
  64 
  65 # Protected mode is a layer of security protection, in order to avoid that
  66 # Redis instances left open on the internet are accessed and exploited.
  67 #
  68 # When protected mode is on and if:
  69 #
  70 # 1) The server is not binding explicitly to a set of addresses using the
  71 #    "bind" directive.
  72 # 2) No password is configured.
  73 #
  74 # The server only accepts connections from clients connecting from the
  75 # IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
  76 # sockets.
  77 #
  78 # By default protected mode is enabled. You should disable it only if
  79 # you are sure you want clients from other hosts to connect to Redis
  80 # even if no authentication is configured, nor a specific set of interfaces
  81 # are explicitly listed using the "bind" directive.
  82 protected-mode yes
  83 
  84 # Accept connections on the specified port, default is 6379 (IANA #815344).
  85 # If port 0 is specified Redis will not listen on a TCP socket.
  86 port 6379
  87 
  88 # TCP listen() backlog.
  89 #
  90 # In high requests-per-second environments you need an high backlog in order
  91 # to avoid slow clients connections issues. Note that the Linux kernel
  92 # will silently truncate it to the value of /proc/sys/net/core/somaxconn so
  93 # make sure to raise both the value of somaxconn and tcp_max_syn_backlog
  94 # in order to get the desired effect.
  95 tcp-backlog 511
  96 
  97 # Unix socket.
  98 #
  99 # Specify the path for the Unix socket that will be used to listen for
 100 # incoming connections. There is no default, so Redis will not listen
 101 # on a unix socket when not specified.
 102 #
 103 # unixsocket /tmp/redis.sock
 104 # unixsocketperm 700
 105 
 106 # Close the connection after a client is idle for N seconds (0 to disable)
 107 timeout 300
 108 
 109 # TCP keepalive.
 110 #
 111 # If non-zero, use SO_KEEPALIVE to send TCP ACKs to clients in absence
 112 # of communication. This is useful for two reasons:
 113 #
 114 # 1) Detect dead peers.
 115 # 2) Take the connection alive from the point of view of network
 116 #    equipment in the middle.
 117 #
 118 # On Linux, the specified value (in seconds) is the period used to send ACKs.
 119 # Note that to close the connection the double of the time is needed.
 120 # On other kernels the period depends on the kernel configuration.
 121 #
 122 # A reasonable value for this option is 300 seconds, which is the new
 123 # Redis default starting with Redis 3.2.1.
 124 tcp-keepalive 300
 125 
 126 ################################# GENERAL #####################################
 127 
 128 # By default Redis does not run as a daemon. Use yes if you need it.
 129 # Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
 130 daemonize yes
 131 
 132 # If you run Redis from upstart or systemd, Redis can interact with your
 133 # supervision tree. Options:
 134 #   supervised no      - no supervision interaction
 135 #   supervised upstart - signal upstart by putting Redis into SIGSTOP mode
 136 #   supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
 137 #   supervised auto    - detect upstart or systemd method based on
 138 #                        UPSTART_JOB or NOTIFY_SOCKET environment variables
 139 # Note: these supervision methods only signal "process is ready."
 140 #       They do not enable continuous liveness pings back to your supervisor.
 141 supervised no
 142 
 143 # If a pid file is specified, Redis writes it where specified at startup
 144 # and removes it at exit.
 145 #
 146 # When the server runs non daemonized, no pid file is created if none is
 147 # specified in the configuration. When the server is daemonized, the pid file
 148 # is used even if not specified, defaulting to "/var/run/redis.pid".
 149 #
 150 # Creating a pid file is best effort: if Redis is not able to create it
 151 # nothing bad happens, the server will start and run normally.
 152 pidfile /var/run/redis_6379.pid
 153 
 154 # Specify the server verbosity level.
 155 # This can be one of:
 156 # debug (a lot of information, useful for development/testing)
 157 # verbose (many rarely useful info, but not a mess like the debug level)
 158 # notice (moderately verbose, what you want in production probably)
 159 # warning (only very important / critical messages are logged)
 160 loglevel debug
 161 
 162 # Specify the log file name. Also the empty string can be used to force
 163 # Redis to log on the standard output. Note that if you use standard
 164 # output for logging but daemonize, logs will be sent to /dev/null
 165 logfile /usr/local/etc/redis/log-redis.log
 166 
 167 # To enable logging to the system logger, just set syslog-enabled to yes,
 168 # and optionally update the other syslog parameters to suit your needs.
 169 # syslog-enabled no
 170 
 171 # Specify the syslog identity.
 172 # syslog-ident redis
 173 
 174 # Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
 175 # syslog-facility local0
 176 
 177 # Set the number of databases. The default database is DB 0, you can select
 178 # a different one on a per-connection basis using SELECT <dbid> where
 179 # dbid is a number between 0 and databases-1
 180 databases 8
 181 
 182 ################################ SNAPSHOTTING  ################################
 183 #
 184 # Save the DB on disk:
 185 #
 186 #   save <seconds> <changes>
 187 #
 188 #   Will save the DB if both the given number of seconds and the given
 189 #   number of write operations against the DB occurred.
 190 #
 191 #   In the example below the behaviour will be to save:
 192 #   after 900 sec (15 min) if at least 1 key changed
 193 #   after 300 sec (5 min) if at least 10 keys changed
 194 #   after 60 sec if at least 10000 keys changed
 195 #
 196 #   Note: you can disable saving completely by commenting out all "save" lines.
 197 #
 198 #   It is also possible to remove all the previously configured save
 199 #   points by adding a save directive with a single empty string argument
 200 #   like in the following example:
 201 #
 202 #   save ""
 203 
 204 save 900 1
 205 save 300 10
 206 save 60 10000
 207 
 208 # By default Redis will stop accepting writes if RDB snapshots are enabled
 209 # (at least one save point) and the latest background save failed.
 210 # This will make the user aware (in a hard way) that data is not persisting
 211 # on disk properly, otherwise chances are that no one will notice and some
 212 # disaster will happen.
 213 #
 214 # If the background saving process will start working again Redis will
 215 # automatically allow writes again.
 216 #
 217 # However if you have setup your proper monitoring of the Redis server
 218 # and persistence, you may want to disable this feature so that Redis will
 219 # continue to work as usual even if there are problems with disk,
 220 # permissions, and so forth.
 221 stop-writes-on-bgsave-error yes
 222 
 223 # Compress string objects using LZF when dump .rdb databases?
 224 # For default thats set to yes as its almost always a win.
 225 # If you want to save some CPU in the saving child set it to no but
 226 # the dataset will likely be bigger if you have compressible values or keys.
 227 rdbcompression yes
 228 
 229 # Since version 5 of RDB a CRC64 checksum is placed at the end of the file.
 230 # This makes the format more resistant to corruption but there is a performance
 231 # hit to pay (around 10%) when saving and loading RDB files, so you can disable it
 232 # for maximum performances.
 233 #
 234 # RDB files created with checksum disabled have a checksum of zero that will
 235 # tell the loading code to skip the check.
 236 rdbchecksum yes
 237 
 238 # The filename where to dump the DB
 239 dbfilename dump.rdb
 240 
 241 # The working directory.
 242 #
 243 # The DB will be written inside this directory, with the filename specified
 244 # above using the dbfilename configuration directive.
 245 #
 246 # The Append Only File will also be created inside this directory.
 247 #
 248 # Note that you must specify a directory here, not a file name.
 249 dir /usr/local/redis/db/
 250 
 251 ################################# REPLICATION #################################
 252 
 253 # Master-Slave replication. Use slaveof to make a Redis instance a copy of
 254 # another Redis server. A few things to understand ASAP about Redis replication.
 255 #
 256 # 1) Redis replication is asynchronous, but you can configure a master to
 257 #    stop accepting writes if it appears to be not connected with at least
 258 #    a given number of slaves.
 259 # 2) Redis slaves are able to perform a partial resynchronization with the
 260 #    master if the replication link is lost for a relatively small amount of
 261 #    time. You may want to configure the replication backlog size (see the next
 262 #    sections of this file) with a sensible value depending on your needs.
 263 # 3) Replication is automatic and does not need user intervention. After a
 264 #    network partition slaves automatically try to reconnect to masters
 265 #    and resynchronize with them.
 266 #
 267 # slaveof <masterip> <masterport>
 268 
 269 # If the master is password protected (using the "requirepass" configuration
 270 # directive below) it is possible to tell the slave to authenticate before
 271 # starting the replication synchronization process, otherwise the master will
 272 # refuse the slave request.
 273 #
 274 # masterauth <master-password>
 275 
 276 # When a slave loses its connection with the master, or when the replication
 277 # is still in progress, the slave can act in two different ways:
 278 #
 279 # 1) if slave-serve-stale-data is set to yes (the default) the slave will
 280 #    still reply to client requests, possibly with out of date data, or the
 281 #    data set may just be empty if this is the first synchronization.
 282 #
 283 # 2) if slave-serve-stale-data is set to no the slave will reply with
 284 #    an error "SYNC with master in progress" to all the kind of commands
 285 #    but to INFO and SLAVEOF.
 286 #
 287 slave-serve-stale-data yes
 288 
 289 # You can configure a slave instance to accept writes or not. Writing against
 290 # a slave instance may be useful to store some ephemeral data (because data
 291 # written on a slave will be easily deleted after resync with the master) but
 292 # may also cause problems if clients are writing to it because of a
 293 # misconfiguration.
 294 #
 295 # Since Redis 2.6 by default slaves are read-only.
 296 #
 297 # Note: read only slaves are not designed to be exposed to untrusted clients
 298 # on the internet. Its just a protection layer against misuse of the instance.
 299 # Still a read only slave exports by default all the administrative commands
 300 # such as CONFIG, DEBUG, and so forth. To a limited extent you can improve
 301 # security of read only slaves using rename-command to shadow all the
 302 # administrative / dangerous commands.
 303 slave-read-only yes
 304 
 305 # Replication SYNC strategy: disk or socket.
 306 #
 307 # -------------------------------------------------------
 308 # WARNING: DISKLESS REPLICATION IS EXPERIMENTAL CURRENTLY
 309 # -------------------------------------------------------
 310 #
 311 # New slaves and reconnecting slaves that are not able to continue the replication
 312 # process just receiving differences, need to do what is called a "full
 313 # synchronization". An RDB file is transmitted from the master to the slaves.
 314 # The transmission can happen in two different ways:
 315 #
 316 # 1) Disk-backed: The Redis master creates a new process that writes the RDB
 317 #                 file on disk. Later the file is transferred by the parent
 318 #                 process to the slaves incrementally.
 319 # 2) Diskless: The Redis master creates a new process that directly writes the
 320 #              RDB file to slave sockets, without touching the disk at all.
 321 #
 322 # With disk-backed replication, while the RDB file is generated, more slaves
 323 # can be queued and served with the RDB file as soon as the current child producing
 324 # the RDB file finishes its work. With diskless replication instead once
 325 # the transfer starts, new slaves arriving will be queued and a new transfer
 326 # will start when the current one terminates.
 327 #
 328 # When diskless replication is used, the master waits a configurable amount of
 329 # time (in seconds) before starting the transfer in the hope that multiple slaves
 330 # will arrive and the transfer can be parallelized.
 331 #
 332 # With slow disks and fast (large bandwidth) networks, diskless replication
 333 # works better.
 334 repl-diskless-sync no
 335 
 336 # When diskless replication is enabled, it is possible to configure the delay
 337 # the server waits in order to spawn the child that transfers the RDB via socket
 338 # to the slaves.
 339 #
 340 # This is important since once the transfer starts, it is not possible to serve
 341 # new slaves arriving, that will be queued for the next RDB transfer, so the server
 342 # waits a delay in order to let more slaves arrive.
 343 #
 344 # The delay is specified in seconds, and by default is 5 seconds. To disable
 345 # it entirely just set it to 0 seconds and the transfer will start ASAP.
 346 repl-diskless-sync-delay 5
 347 
 348 # Slaves send PINGs to server in a predefined interval. Its possible to change
 349 # this interval with the repl_ping_slave_period option. The default value is 10
 350 # seconds.
 351 #
 352 # repl-ping-slave-period 10
 353 
 354 # The following option sets the replication timeout for:
 355 #
 356 # 1) Bulk transfer I/O during SYNC, from the point of view of slave.
 357 # 2) Master timeout from the point of view of slaves (data, pings).
 358 # 3) Slave timeout from the point of view of masters (REPLCONF ACK pings).
 359 #
 360 # It is important to make sure that this value is greater than the value
 361 # specified for repl-ping-slave-period otherwise a timeout will be detected
 362 # every time there is low traffic between the master and the slave.
 363 #
 364 # repl-timeout 60
 365 
 366 # Disable TCP_NODELAY on the slave socket after SYNC?
 367 #
 368 # If you select "yes" Redis will use a smaller number of TCP packets and
 369 # less bandwidth to send data to slaves. But this can add a delay for
 370 # the data to appear on the slave side, up to 40 milliseconds with
 371 # Linux kernels using a default configuration.
 372 #
 373 # If you select "no" the delay for data to appear on the slave side will
 374 # be reduced but more bandwidth will be used for replication.
 375 #
 376 # By default we optimize for low latency, but in very high traffic conditions
 377 # or when the master and slaves are many hops away, turning this to "yes" may
 378 # be a good idea.
 379 repl-disable-tcp-nodelay no
 380 
 381 # Set the replication backlog size. The backlog is a buffer that accumulates
 382 # slave data when slaves are disconnected for some time, so that when a slave
 383 # wants to reconnect again, often a full resync is not needed, but a partial
 384 # resync is enough, just passing the portion of data the slave missed while
 385 # disconnected.
 386 #
 387 # The bigger the replication backlog, the longer the time the slave can be
 388 # disconnected and later be able to perform a partial resynchronization.
 389 #
 390 # The backlog is only allocated once there is at least a slave connected.
 391 #
 392 # repl-backlog-size 1mb
 393 
 394 # After a master has no longer connected slaves for some time, the backlog
 395 # will be freed. The following option configures the amount of seconds that
 396 # need to elapse, starting from the time the last slave disconnected, for
 397 # the backlog buffer to be freed.
 398 #
 399 # A value of 0 means to never release the backlog.
 400 #
 401 # repl-backlog-ttl 3600
 402 
 403 # The slave priority is an integer number published by Redis in the INFO output.
 404 # It is used by Redis Sentinel in order to select a slave to promote into a
 405 # master if the master is no longer working correctly.
 406 #
 407 # A slave with a low priority number is considered better for promotion, so
 408 # for instance if there are three slaves with priority 10, 100, 25 Sentinel will
 409 # pick the one with priority 10, that is the lowest.
 410 #
 411 # However a special priority of 0 marks the slave as not able to perform the
 412 # role of master, so a slave with priority of 0 will never be selected by
 413 # Redis Sentinel for promotion.
 414 #
 415 # By default the priority is 100.
 416 slave-priority 100
 417 
 418 # It is possible for a master to stop accepting writes if there are less than
 419 # N slaves connected, having a lag less or equal than M seconds.
 420 #
 421 # The N slaves need to be in "online" state.
 422 #
 423 # The lag in seconds, that must be <= the specified value, is calculated from
 424 # the last ping received from the slave, that is usually sent every second.
 425 #
 426 # This option does not GUARANTEE that N replicas will accept the write, but
 427 # will limit the window of exposure for lost writes in case not enough slaves
 428 # are available, to the specified number of seconds.
 429 #
 430 # For example to require at least 3 slaves with a lag <= 10 seconds use:
 431 #
 432 # min-slaves-to-write 3
 433 # min-slaves-max-lag 10
 434 #
 435 # Setting one or the other to 0 disables the feature.
 436 #
 437 # By default min-slaves-to-write is set to 0 (feature disabled) and
 438 # min-slaves-max-lag is set to 10.
 439 
 440 # A Redis master is able to list the address and port of the attached
 441 # slaves in different ways. For example the "INFO replication" section
 442 # offers this information, which is used, among other tools, by
 443 # Redis Sentinel in order to discover slave instances.
 444 # Another place where this info is available is in the output of the
 445 # "ROLE" command of a masteer.
 446 #
 447 # The listed IP and address normally reported by a slave is obtained
 448 # in the following way:
 449 #
 450 #   IP: The address is auto detected by checking the peer address
 451 #   of the socket used by the slave to connect with the master.
 452 #
 453 #   Port: The port is communicated by the slave during the replication
 454 #   handshake, and is normally the port that the slave is using to
 455 #   list for connections.
 456 #
 457 # However when port forwarding or Network Address Translation (NAT) is
 458 # used, the slave may be actually reachable via different IP and port
 459 # pairs. The following two options can be used by a slave in order to
 460 # report to its master a specific set of IP and port, so that both INFO
 461 # and ROLE will report those values.
 462 #
 463 # There is no need to use both the options if you need to override just
 464 # the port or the IP address.
 465 #
 466 # slave-announce-ip 5.5.5.5
 467 # slave-announce-port 1234
 468 
 469 ################################## SECURITY ###################################
 470 
 471 # Require clients to issue AUTH <PASSWORD> before processing any other
 472 # commands.  This might be useful in environments in which you do not trust
 473 # others with access to the host running redis-server.
 474 #
 475 # This should stay commented out for backward compatibility and because most
 476 # people do not need auth (e.g. they run their own servers).
 477 #
 478 # Warning: since Redis is pretty fast an outside user can try up to
 479 # 150k passwords per second against a good box. This means that you should
 480 # use a very strong password otherwise it will be very easy to break.
 481 #
 482 # requirepass foobared
 483 
 484 # Command renaming.
 485 #
 486 # It is possible to change the name of dangerous commands in a shared
 487 # environment. For instance the CONFIG command may be renamed into something
 488 # hard to guess so that it will still be available for internal-use tools
 489 # but not available for general clients.
 490 #
 491 # Example:
 492 #
 493 # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
 494 #
 495 # It is also possible to completely kill a command by renaming it into
 496 # an empty string:
 497 #
 498 # rename-command CONFIG ""
 499 #
 500 # Please note that changing the name of commands that are logged into the
 501 # AOF file or transmitted to slaves may cause problems.
 502 
 503 ################################### LIMITS ####################################
 504 
 505 # Set the max number of connected clients at the same time. By default
 506 # this limit is set to 10000 clients, however if the Redis server is not
 507 # able to configure the process file limit to allow for the specified limit
 508 # the max number of allowed clients is set to the current file limit
 509 # minus 32 (as Redis reserves a few file descriptors for internal uses).
 510 #
 511 # Once the limit is reached Redis will close all the new connections sending
 512 # an error max number of clients reached.
 513 #
 514 # maxclients 10000
 515 
 516 # Dont use more memory than the specified amount of bytes.
 517 # When the memory limit is reached Redis will try to remove keys
 518 # according to the eviction policy selected (see maxmemory-policy).
 519 #
 520 # If Redis cant remove keys according to the policy, or if the policy is
 521 # set to noeviction, Redis will start to reply with errors to commands
 522 # that would use more memory, like SET, LPUSH, and so on, and will continue
 523 # to reply to read-only commands like GET.
 524 #
 525 # This option is usually useful when using Redis as an LRU cache, or to set
 526 # a hard memory limit for an instance (using the noeviction policy).
 527 #
 528 # WARNING: If you have slaves attached to an instance with maxmemory on,
 529 # the size of the output buffers needed to feed the slaves are subtracted
 530 # from the used memory count, so that network problems / resyncs will
 531 # not trigger a loop where keys are evicted, and in turn the output
 532 # buffer of slaves is full with DELs of keys evicted triggering the deletion
 533 # of more keys, and so forth until the database is completely emptied.
 534 #
 535 # In short... if you have slaves attached it is suggested that you set a lower
 536 # limit for maxmemory so that there is some free RAM on the system for slave
 537 # output buffers (but this is not needed if the policy is noeviction).
 538 #
 539 # maxmemory <bytes>
 540 
 541 # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
 542 # is reached. You can select among five behaviors:
 543 #
 544 # volatile-lru -> remove the key with an expire set using an LRU algorithm
 545 # allkeys-lru -> remove any key according to the LRU algorithm
 546 # volatile-random -> remove a random key with an expire set
 547 # allkeys-random -> remove a random key, any key
 548 # volatile-ttl -> remove the key with the nearest expire time (minor TTL)
 549 # noeviction -> dont expire at all, just return an error on write operations
 550 #
 551 # Note: with any of the above policies, Redis will return an error on write
 552 #       operations, when there are no suitable keys for eviction.
 553 #
 554 #       At the date of writing these commands are: set setnx setex append
 555 #       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
 556 #       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
 557 #       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
 558 #       getset mset msetnx exec sort
 559 #
 560 # The default is:
 561 #
 562 # maxmemory-policy noeviction
 563 
 564 # LRU and minimal TTL algorithms are not precise algorithms but approximated
 565 # algorithms (in order to save memory), so you can tune it for speed or
 566 # accuracy. For default Redis will check five keys and pick the one that was
 567 # used less recently, you can change the sample size using the following
 568 # configuration directive.
 569 #
 570 # The default of 5 produces good enough results. 10 Approximates very closely
 571 # true LRU but costs a bit more CPU. 3 is very fast but not very accurate.
 572 #
 573 # maxmemory-samples 5
 574 
 575 ############################## APPEND ONLY MODE ###############################
 576 
 577 # By default Redis asynchronously dumps the dataset on disk. This mode is
 578 # good enough in many applications, but an issue with the Redis process or
 579 # a power outage may result into a few minutes of writes lost (depending on
 580 # the configured save points).
 581 #
 582 # The Append Only File is an alternative persistence mode that provides
 583 # much better durability. For instance using the default data fsync policy
 584 # (see later in the config file) Redis can lose just one second of writes in a
 585 # dramatic event like a server power outage, or a single write if something
 586 # wrong with the Redis process itself happens, but the operating system is
 587 # still running correctly.
 588 #
 589 # AOF and RDB persistence can be enabled at the same time without problems.
 590 # If the AOF is enabled on startup Redis will load the AOF, that is the file
 591 # with the better durability guarantees.
 592 #
 593 # Please check http://redis.io/topics/persistence for more information.
 594 
 595 appendonly no
 596 
 597 # The name of the append only file (default: "appendonly.aof")
 598 
 599 appendfilename "appendonly.aof"
 600 
 601 # The fsync() call tells the Operating System to actually write data on disk
 602 # instead of waiting for more data in the output buffer. Some OS will really flush
 603 # data on disk, some other OS will just try to do it ASAP.
 604 #
 605 # Redis supports three different modes:
 606 #
 607 # no: dont fsync, just let the OS flush the data when it wants. Faster.
 608 # always: fsync after every write to the append only log. Slow, Safest.
 609 # everysec: fsync only one time every second. Compromise.
 610 #
 611 # The default is "everysec", as thats usually the right compromise between
 612 # speed and data safety. Its up to you to understand if you can relax this to
 613 # "no" that will let the operating system flush the output buffer when
 614 # it wants, for better performances (but if you can live with the idea of
 615 # some data loss consider the default persistence mode thats snapshotting),
 616 # or on the contrary, use "always" thats very slow but a bit safer than
 617 # everysec.
 618 #
 619 # More details please check the following article:
 620 # http://antirez.com/post/redis-persistence-demystified.html
 621 #
 622 # If unsure, use "everysec".
 623 
 624 # appendfsync always
 625 appendfsync everysec
 626 # appendfsync no
 627 
 628 # When the AOF fsync policy is set to always or everysec, and a background
 629 # saving process (a background save or AOF log background rewriting) is
 630 # performing a lot of I/O against the disk, in some Linux configurations
 631 # Redis may block too long on the fsync() call. Note that there is no fix for
 632 # this currently, as even performing fsync in a different thread will block
 633 # our synchronous write(2) call.
 634 #
 635 # In order to mitigate this problem its possible to use the following option
 636 # that will prevent fsync() from being called in the main process while a
 637 # BGSAVE or BGREWRITEAOF is in progress.
 638 #
 639 # This means that while another child is saving, the durability of Redis is
 640 # the same as "appendfsync none". In practical terms, this means that it is
 641 # possible to lose up to 30 seconds of log in the worst scenario (with the
 642 # default Linux settings).
 643 #
 644 # If you have latency problems turn this to "yes". Otherwise leave it as
 645 # "no" that is the safest pick from the point of view of durability.
 646 
 647 no-appendfsync-on-rewrite no
 648 
 649 # Automatic rewrite of the append only file.
 650 # Redis is able to automatically rewrite the log file implicitly calling
 651 # BGREWRITEAOF when the AOF log size grows by the specified percentage.
 652 #
 653 # This is how it works: Redis remembers the size of the AOF file after the
 654 # latest rewrite (if no rewrite has happened since the restart, the size of
 655 # the AOF at startup is used).
 656 #
 657 # This base size is compared to the current size. If the current size is
 658 # bigger than the specified percentage, the rewrite is triggered. Also
 659 # you need to specify a minimal size for the AOF file to be rewritten, this
 660 # is useful to avoid rewriting the AOF file even if the percentage increase
 661 # is reached but it is still pretty small.
 662 #
 663 # Specify a percentage of zero in order to disable the automatic AOF
 664 # rewrite feature.
 665 
 666 auto-aof-rewrite-percentage 100
 667 auto-aof-rewrite-min-size 64mb
 668 
 669 # An AOF file may be found to be truncated at the end during the Redis
 670 # startup process, when the AOF data gets loaded back into memory.
 671 # This may happen when the system where Redis is running
 672 # crashes, especially when an ext4 filesystem is mounted without the
 673 # data=http://www.mamicode.com/ordered option (however this cant happen when Redis itself
 674 # crashes or aborts but the operating system still works correctly).
 675 #
 676 # Redis can either exit with an error when this happens, or load as much
 677 # data as possible (the default now) and start if the AOF file is found
 678 # to be truncated at the end. The following option controls this behavior.
 679 #
 680 # If aof-load-truncated is set to yes, a truncated AOF file is loaded and
 681 # the Redis server starts emitting a log to inform the user of the event.
 682 # Otherwise if the option is set to no, the server aborts with an error
 683 # and refuses to start. When the option is set to no, the user requires
 684 # to fix the AOF file using the "redis-check-aof" utility before to restart
 685 # the server.
 686 #
 687 # Note that if the AOF file will be found to be corrupted in the middle
 688 # the server will still exit with an error. This option only applies when
 689 # Redis will try to read more data from the AOF file but not enough bytes
 690 # will be found.
 691 aof-load-truncated yes
 692 
 693 ################################ LUA SCRIPTING  ###############################
 694 
 695 # Max execution time of a Lua script in milliseconds.
 696 #
 697 # If the maximum execution time is reached Redis will log that a script is
 698 # still in execution after the maximum allowed time and will start to
 699 # reply to queries with an error.
 700 #
 701 # When a long running script exceeds the maximum execution time only the
 702 # SCRIPT KILL and SHUTDOWN NOSAVE commands are available. The first can be
 703 # used to stop a script that did not yet called write commands. The second
 704 # is the only way to shut down the server in the case a write command was
 705 # already issued by the script but the user doesnt want to wait for the natural
 706 # termination of the script.
 707 #
 708 # Set it to 0 or a negative value for unlimited execution without warnings.
 709 lua-time-limit 5000
 710 
 711 ################################ REDIS CLUSTER  ###############################
 712 #
 713 # ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 714 # WARNING EXPERIMENTAL: Redis Cluster is considered to be stable code, however
 715 # in order to mark it as "mature" we need to wait for a non trivial percentage
 716 # of users to deploy it in production.
 717 # ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 718 #
 719 # Normal Redis instances cant be part of a Redis Cluster; only nodes that are
 720 # started as cluster nodes can. In order to start a Redis instance as a
 721 # cluster node enable the cluster support uncommenting the following:
 722 #
 723 # cluster-enabled yes
 724 
 725 # Every cluster node has a cluster configuration file. This file is not
 726 # intended to be edited by hand. It is created and updated by Redis nodes.
 727 # Every Redis Cluster node requires a different cluster configuration file.
 728 # Make sure that instances running in the same system do not have
 729 # overlapping cluster configuration file names.
 730 #
 731 # cluster-config-file nodes-6379.conf
 732 
 733 # Cluster node timeout is the amount of milliseconds a node must be unreachable
 734 # for it to be considered in failure state.
 735 # Most other internal time limits are multiple of the node timeout.
 736 #
 737 # cluster-node-timeout 15000
 738 
 739 # A slave of a failing master will avoid to start a failover if its data
 740 # looks too old.
 741 #
 742 # There is no simple way for a slave to actually have a exact measure of
 743 # its "data age", so the following two checks are performed:
 744 #
 745 # 1) If there are multiple slaves able to failover, they exchange messages
 746 #    in order to try to give an advantage to the slave with the best
 747 #    replication offset (more data from the master processed).
 748 #    Slaves will try to get their rank by offset, and apply to the start
 749 #    of the failover a delay proportional to their rank.
 750 #
 751 # 2) Every single slave computes the time of the last interaction with
 752 #    its master. This can be the last ping or command received (if the master
 753 #    is still in the "connected" state), or the time that elapsed since the
 754 #    disconnection with the master (if the replication link is currently down).
 755 #    If the last interaction is too old, the slave will not try to failover
 756 #    at all.
 757 #
 758 # The point "2" can be tuned by user. Specifically a slave will not perform
 759 # the failover if, since the last interaction with the master, the time
 760 # elapsed is greater than:
 761 #
 762 #   (node-timeout * slave-validity-factor) + repl-ping-slave-period
 763 #
 764 # So for example if node-timeout is 30 seconds, and the slave-validity-factor
 765 # is 10, and assuming a default repl-ping-slave-period of 10 seconds, the
 766 # slave will not try to failover if it was not able to talk with the master
 767 # for longer than 310 seconds.
 768 #
 769 # A large slave-validity-factor may allow slaves with too old data to failover
 770 # a master, while a too small value may prevent the cluster from being able to
 771 # elect a slave at all.
 772 #
 773 # For maximum availability, it is possible to set the slave-validity-factor
 774 # to a value of 0, which means, that slaves will always try to failover the
 775 # master regardless of the last time they interacted with the master.
 776 # (However theyll always try to apply a delay proportional to their
 777 # offset rank).
 778 #
 779 # Zero is the only value able to guarantee that when all the partitions heal
 780 # the cluster will always be able to continue.
 781 #
 782 # cluster-slave-validity-factor 10
 783 
 784 # Cluster slaves are able to migrate to orphaned masters, that are masters
 785 # that are left without working slaves. This improves the cluster ability
 786 # to resist to failures as otherwise an orphaned master cant be failed over
 787 # in case of failure if it has no working slaves.
 788 #
 789 # Slaves migrate to orphaned masters only if there are still at least a
 790 # given number of other working slaves for their old master. This number
 791 # is the "migration barrier". A migration barrier of 1 means that a slave
 792 # will migrate only if there is at least 1 other working slave for its master
 793 # and so forth. It usually reflects the number of slaves you want for every
 794 # master in your cluster.
 795 #
 796 # Default is 1 (slaves migrate only if their masters remain with at least
 797 # one slave). To disable migration just set it to a very large value.
 798 # A value of 0 can be set but is useful only for debugging and dangerous
 799 # in production.
 800 #
 801 # cluster-migration-barrier 1
 802 
 803 # By default Redis Cluster nodes stop accepting queries if they detect there
 804 # is at least an hash slot uncovered (no available node is serving it).
 805 # This way if the cluster is partially down (for example a range of hash slots
 806 # are no longer covered) all the cluster becomes, eventually, unavailable.
 807 # It automatically returns available as soon as all the slots are covered again.
 808 #
 809 # However sometimes you want the subset of the cluster which is working,
 810 # to continue to accept queries for the part of the key space that is still
 811 # covered. In order to do so, just set the cluster-require-full-coverage
 812 # option to no.
 813 #
 814 # cluster-require-full-coverage yes
 815 
 816 # In order to setup your cluster make sure to read the documentation
 817 # available at http://redis.io web site.
 818 
 819 ################################## SLOW LOG ###################################
 820 
 821 # The Redis Slow Log is a system to log queries that exceeded a specified
 822 # execution time. The execution time does not include the I/O operations
 823 # like talking with the client, sending the reply and so forth,
 824 # but just the time needed to actually execute the command (this is the only
 825 # stage of command execution where the thread is blocked and can not serve
 826 # other requests in the meantime).
 827 #
 828 # You can configure the slow log with two parameters: one tells Redis
 829 # what is the execution time, in microseconds, to exceed in order for the
 830 # command to get logged, and the other parameter is the length of the
 831 # slow log. When a new command is logged the oldest one is removed from the
 832 # queue of logged commands.
 833 
 834 # The following time is expressed in microseconds, so 1000000 is equivalent
 835 # to one second. Note that a negative number disables the slow log, while
 836 # a value of zero forces the logging of every command.
 837 slowlog-log-slower-than 10000
 838 
 839 # There is no limit to this length. Just be aware that it will consume memory.
 840 # You can reclaim memory used by the slow log with SLOWLOG RESET.
 841 slowlog-max-len 128
 842 
 843 ################################ LATENCY MONITOR ##############################
 844 
 845 # The Redis latency monitoring subsystem samples different operations
 846 # at runtime in order to collect data related to possible sources of
 847 # latency of a Redis instance.
 848 #
 849 # Via the LATENCY command this information is available to the user that can
 850 # print graphs and obtain reports.
 851 #
 852 # The system only logs operations that were performed in a time equal or
 853 # greater than the amount of milliseconds specified via the
 854 # latency-monitor-threshold configuration directive. When its value is set
 855 # to zero, the latency monitor is turned off.
 856 #
 857 # By default latency monitoring is disabled since it is mostly not needed
 858 # if you dont have latency issues, and collecting data has a performance
 859 # impact, that while very small, can be measured under big load. Latency
 860 # monitoring can easily be enabled at runtime using the command
 861 # "CONFIG SET latency-monitor-threshold <milliseconds>" if needed.
 862 latency-monitor-threshold 0
 863 
 864 ############################# EVENT NOTIFICATION ##############################
 865 
 866 # Redis can notify Pub/Sub clients about events happening in the key space.
 867 # This feature is documented at http://redis.io/topics/notifications
 868 #
 869 # For instance if keyspace events notification is enabled, and a client
 870 # performs a DEL operation on key "foo" stored in the Database 0, two
 871 # messages will be published via Pub/Sub:
 872 #
 873 # PUBLISH __keyspace@0__:foo del
 874 # PUBLISH __keyevent@0__:del foo
 875 #
 876 # It is possible to select the events that Redis will notify among a set
 877 # of classes. Every class is identified by a single character:
 878 #
 879 #  K     Keyspace events, published with __keyspace@<db>__ prefix.
 880 #  E     Keyevent events, published with __keyevent@<db>__ prefix.
 881 #  g     Generic commands (non-type specific) like DEL, EXPIRE, RENAME, ...
 882 #  $     String commands
 883 #  l     List commands
 884 #  s     Set commands
 885 #  h     Hash commands
 886 #  z     Sorted set commands
 887 #  x     Expired events (events generated every time a key expires)
 888 #  e     Evicted events (events generated when a key is evicted for maxmemory)
 889 #  A     Alias for g$lshzxe, so that the "AKE" string means all the events.
 890 #
 891 #  The "notify-keyspace-events" takes as argument a string that is composed
 892 #  of zero or multiple characters. The empty string means that notifications
 893 #  are disabled.
 894 #
 895 #  Example: to enable list and generic events, from the point of view of the
 896 #           event name, use:
 897 #
 898 #  notify-keyspace-events Elg
 899 #
 900 #  Example 2: to get the stream of the expired keys subscribing to channel
 901 #             name __keyevent@0__:expired use:
 902 #
 903 #  notify-keyspace-events Ex
 904 #
 905 #  By default all notifications are disabled because most users dont need
 906 #  this feature and the feature has some overhead. Note that if you dont
 907 #  specify at least one of K or E, no events will be delivered.
 908 notify-keyspace-events ""
 909 
 910 ############################### ADVANCED CONFIG ###############################
 911 
 912 # Hashes are encoded using a memory efficient data structure when they have a
 913 # small number of entries, and the biggest entry does not exceed a given
 914 # threshold. These thresholds can be configured using the following directives.
 915 hash-max-ziplist-entries 512
 916 hash-max-ziplist-value 64
 917 
 918 # Lists are also encoded in a special way to save a lot of space.
 919 # The number of entries allowed per internal list node can be specified
 920 # as a fixed maximum size or a maximum number of elements.
 921 # For a fixed maximum size, use -5 through -1, meaning:
 922 # -5: max size: 64 Kb  <-- not recommended for normal workloads
 923 # -4: max size: 32 Kb  <-- not recommended
 924 # -3: max size: 16 Kb  <-- probably not recommended
 925 # -2: max size: 8 Kb   <-- good
 926 # -1: max size: 4 Kb   <-- good
 927 # Positive numbers mean store up to _exactly_ that number of elements
 928 # per list node.
 929 # The highest performing option is usually -2 (8 Kb size) or -1 (4 Kb size),
 930 # but if your use case is unique, adjust the settings as necessary.
 931 list-max-ziplist-size -2
 932 
 933 # Lists may also be compressed.
 934 # Compress depth is the number of quicklist ziplist nodes from *each* side of
 935 # the list to *exclude* from compression.  The head and tail of the list
 936 # are always uncompressed for fast push/pop operations.  Settings are:
 937 # 0: disable all list compression
 938 # 1: depth 1 means "don‘t start compressing until after 1 node into the list,
 939 #    going from either the head or tail"
 940 #    So: [head]->node->node->...->node->[tail]
 941 #    [head], [tail] will always be uncompressed; inner nodes will compress.
 942 # 2: [head]->[next]->node->node->...->node->[prev]->[tail]
 943 #    2 here means: dont compress head or head->next or tail->prev or tail,
 944 #    but compress all nodes between them.
 945 # 3: [head]->[next]->[next]->node->node->...->node->[prev]->[prev]->[tail]
 946 # etc.
 947 list-compress-depth 0
 948 
 949 # Sets have a special encoding in just one case: when a set is composed
 950 # of just strings that happen to be integers in radix 10 in the range
 951 # of 64 bit signed integers.
 952 # The following configuration setting sets the limit in the size of the
 953 # set in order to use this special memory saving encoding.
 954 set-max-intset-entries 512
 955 
 956 # Similarly to hashes and lists, sorted sets are also specially encoded in
 957 # order to save a lot of space. This encoding is only used when the length and
 958 # elements of a sorted set are below the following limits:
 959 zset-max-ziplist-entries 128
 960 zset-max-ziplist-value 64
 961 
 962 # HyperLogLog sparse representation bytes limit. The limit includes the
 963 # 16 bytes header. When an HyperLogLog using the sparse representation crosses
 964 # this limit, it is converted into the dense representation.
 965 #
 966 # A value greater than 16000 is totally useless, since at that point the
 967 # dense representation is more memory efficient.
 968 #
 969 # The suggested value is ~ 3000 in order to have the benefits of
 970 # the space efficient encoding without slowing down too much PFADD,
 971 # which is O(N) with the sparse encoding. The value can be raised to
 972 # ~ 10000 when CPU is not a concern, but space is, and the data set is
 973 # composed of many HyperLogLogs with cardinality in the 0 - 15000 range.
 974 hll-sparse-max-bytes 3000
 975 
 976 # Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
 977 # order to help rehashing the main Redis hash table (the one mapping top-level
 978 # keys to values). The hash table implementation Redis uses (see dict.c)
 979 # performs a lazy rehashing: the more operation you run into a hash table
 980 # that is rehashing, the more rehashing "steps" are performed, so if the
 981 # server is idle the rehashing is never complete and some more memory is used
 982 # by the hash table.
 983 #
 984 # The default is to use this millisecond 10 times every second in order to
 985 # actively rehash the main dictionaries, freeing memory when possible.
 986 #
 987 # If unsure:
 988 # use "activerehashing no" if you have hard latency requirements and it is
 989 # not a good thing in your environment that Redis can reply from time to time
 990 # to queries with 2 milliseconds delay.
 991 #
 992 # use "activerehashing yes" if you dont have such hard requirements but
 993 # want to free memory asap when possible.
 994 activerehashing yes
 995 
 996 # The client output buffer limits can be used to force disconnection of clients
 997 # that are not reading data from the server fast enough for some reason (a
 998 # common reason is that a Pub/Sub client cant consume messages as fast as the
 999 # publisher can produce them).
1000 #
1001 # The limit can be set differently for the three different classes of clients:
1002 #
1003 # normal -> normal clients including MONITOR clients
1004 # slave  -> slave clients
1005 # pubsub -> clients subscribed to at least one pubsub channel or pattern
1006 #
1007 # The syntax of every client-output-buffer-limit directive is the following:
1008 #
1009 # client-output-buffer-limit <class> <hard limit> <soft limit> <soft seconds>
1010 #
1011 # A client is immediately disconnected once the hard limit is reached, or if
1012 # the soft limit is reached and remains reached for the specified number of
1013 # seconds (continuously).
1014 # So for instance if the hard limit is 32 megabytes and the soft limit is
1015 # 16 megabytes / 10 seconds, the client will get disconnected immediately
1016 # if the size of the output buffers reach 32 megabytes, but will also get
1017 # disconnected if the client reaches 16 megabytes and continuously overcomes
1018 # the limit for 10 seconds.
1019 #
1020 # By default normal clients are not limited because they dont receive data
1021 # without asking (in a push way), but just after a request, so only
1022 # asynchronous clients may create a scenario where data is requested faster
1023 # than it can read.
1024 #
1025 # Instead there is a default limit for pubsub and slave clients, since
1026 # subscribers and slaves receive data in a push fashion.
1027 #
1028 # Both the hard or the soft limit can be disabled by setting them to zero.
1029 client-output-buffer-limit normal 0 0 0
1030 client-output-buffer-limit slave 256mb 64mb 60
1031 client-output-buffer-limit pubsub 32mb 8mb 60
1032 
1033 # Redis calls an internal function to perform many background tasks, like
1034 # closing connections of clients in timeout, purging expired keys that are
1035 # never requested, and so forth.
1036 #
1037 # Not all tasks are performed with the same frequency, but Redis checks for
1038 # tasks to perform according to the specified "hz" value.
1039 #
1040 # By default "hz" is set to 10. Raising the value will use more CPU when
1041 # Redis is idle, but at the same time will make Redis more responsive when
1042 # there are many keys expiring at the same time, and timeouts may be
1043 # handled with more precision.
1044 #
1045 # The range is between 1 and 500, however a value over 100 is usually not
1046 # a good idea. Most users should use the default of 10 and raise this up to
1047 # 100 only in environments where very low latency is required.
1048 hz 10
1049 
1050 # When a child rewrites the AOF file, if the following option is enabled
1051 # the file will be fsync-ed every 32 MB of data generated. This is useful
1052 # in order to commit the file to the disk more incrementally and avoid
1053 # big latency spikes.
1054 aof-rewrite-incremental-fsync yes
redis.conf

 

  4、保存文件退出,进入/usr/local/bin/目录下,启动redis

  sudo ./redis-server /usr/local/etc/redis/redis.conf

  5、启动之后,实时查看启动日志

  tail -f /usr/local/etc/redis/log-redis.log

  至此,redis完成搭建,默认端口是6379

  如果想操作redis,进入bin目录之后,使用redis客户端工具进行查看

  sudo ./redis-cli -h xxx.xxx.xx.xxx -p 6379 -a password

  如果想停止redis服务:

  1、杀掉进程;

  2、在redis-cli中使用shutdown命令

mac搭建redis环境