Redis安裝整理(window平臺和Linux平臺)及在java應用

window平臺Redis安裝

redis windows安裝文件下載地址: http://code.google.com/p/servicestack/wiki/RedisWindowsDownload#Download_32bit_Cygwin_builds_for_Windows
我選擇的redis爲最新版的安裝文件，見下圖：

 
Redis安裝文件解壓後，有如下幾個文件。見下圖

redis-server.exe：服務程序
redis-check-dump.exe：本地數據庫檢查
redis-check-aof.exe：更新日誌檢查
redis-benchmark.exe：性能測試，用以模擬同時由N個客戶端發送M個 SETs/GETs 查詢 (相似於 Apache 的ab 工具).

在解壓好redis的安裝文件到E:\根目錄後，還須要在redis根目錄增長一個redis的配置文件redis.conf，文件具體內容附件中有，不過這裏我仍然把配置文件的內容貼上來：

# Redis configuration file example

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

# When run as a daemon, Redis write a pid file in /var/run/redis.pid by default.
# You can specify a custom pid file location here.
pidfile /var/run/redis.pid

# Accept connections on the specified port, default is 6379
port 6379

# If you want you can bind a single interface, if the bind option is not
# specified all the interfaces will listen for connections.
#
# bind 127.0.0.1

# Close the connection after a client is idle for N seconds (0 to disable)
timeout 300

# Set server verbosity to 'debug'
# it can be one of:
# debug (a lot of information, useful for development/testing)
# notice (moderately verbose, what you want in production probably)
# warning (only very important / critical messages are logged)
loglevel debug

# Specify the log file name. Also 'stdout' can be used to force
# the demon 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 stdout

# Set the number of databases. The default database is DB 0, you can select
# a different one on a per-connection basis using SELECT <dbid> where
# dbid is a number between 0 and 'databases'-1
databases 16

################################ SNAPSHOTTING  #################################
#
# Save the DB on disk:
#
#   save <seconds> <changes>
#
#   Will save the DB if both the given number of seconds and the given
#   number of write operations against the DB occurred.
#
#   In the example below the behaviour will be to save:
#   after 900 sec (15 min) if at least 1 key changed
#   after 300 sec (5 min) if at least 10 keys changed
#   after 60 sec if at least 10000 keys changed
save 900 1
save 300 10
save 60 10000

# 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

# The filename where to dump the DB
dbfilename dump.rdb

# For default save/load DB in/from the working directory
# Note that you must specify a directory not a file name.
dir ./

################################# REPLICATION #################################

# Master-Slave replication. Use slaveof to make a Redis instance a copy of
# another Redis server. Note that the configuration is local to the slave
# so for example it is possible to configure the slave to save the DB with a
# different interval, or to listen to another port, and so on.
#
# slaveof <masterip> <masterport>

# If the master is password protected (using the "requirepass" configuration
# directive below) it is possible to tell the slave to authenticate before
# starting the replication synchronization process, otherwise the master will
# refuse the slave request.
#
# masterauth <master-password>

################################## SECURITY ###################################

# Require clients to issue AUTH <PASSWORD> 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).
#
# requirepass foobared

################################### LIMITS ####################################

# Set the max number of connected clients at the same time. By default there
# is no limit, and it's up to the number of file descriptors the Redis process
# is able to open. The special value '0' means no limts.
# Once the limit is reached Redis will close all the new connections sending
# an error 'max number of clients reached'.
#
# maxclients 128

# Don't use more memory than the specified amount of bytes.
# When the memory limit is reached Redis will try to remove keys with an
# EXPIRE set. It will try to start freeing keys that are going to expire
# in little time and preserve keys with a longer time to live.
# Redis will also try to remove objects from free lists if possible.
#
# If all this fails, Redis will start to reply with errors to commands
# that will use more memory, like SET, LPUSH, and so on, and will continue
# to reply to most read-only commands like GET.
#
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
# 'state' server or cache, not as a real DB. When Redis is used as a real
# database the memory usage will grow over the weeks, it will be obvious if
# it is going to use too much memory in the long run, and you'll have the time
# to upgrade. With maxmemory after the limit is reached you'll start to get
# errors for write operations, and this may even lead to DB inconsistency.
#
# maxmemory <bytes>

############################## APPEND ONLY MODE ###############################

# By default Redis asynchronously dumps the dataset on disk. If you can live
# with the idea that the latest records will be lost if something like a crash
# happens this is the preferred way to run Redis. If instead you care a lot
# about your data and don't want to that a single record can get lost you should
# enable the append only mode: when this mode is enabled Redis will append
# every write operation received in the file appendonly.log. This file will
# be read on startup in order to rebuild the full dataset in memory.
#
# Note that you can have both the async dumps and the append only file if you
# like (you have to comment the "save" statements above to disable the dumps).
# Still if append only mode is enabled Redis will load the data from the
# log file at startup ignoring the dump.rdb file.
#
# The name of the append only file is "appendonly.log"
#
# IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
# log file in background when it gets too big.

appendonly no

# The fsync() call tells the Operating System to actually write data on disk
# instead to wait for more data in the output buffer. Some OS will really flush
# data on disk, some other OS will just try to do it ASAP.
#
# Redis supports three different modes:
#
# no: don't fsync, just let the OS flush the data when it wants. Faster.
# always: fsync after every write to the append only log . Slow, Safest.
# everysec: fsync only if one second passed since the last fsync. Compromise.
#
# The default is "always" that's the safer of the options. It's up to you to
# understand if you can relax this to "everysec" that will fsync every second
# or to "no" that will let the operating system flush the output buffer when
# it want, for better performances (but if you can live with the idea of
# some data loss consider the default persistence mode that's snapshotting).

appendfsync always
# appendfsync everysec
# appendfsync no

############################### ADVANCED CONFIG ###############################

# Glue small output buffers together in order to send small replies in a
# single TCP packet. Uses a bit more CPU but most of the times it is a win
# in terms of number of queries per second. Use 'yes' if unsure.
glueoutputbuf yes

# Use object sharing. Can save a lot of memory if you have many common
# string in your dataset, but performs lookups against the shared objects
# pool so it uses more CPU and can be a bit slower. Usually it's a good
# idea.
#
# When object sharing is enabled (shareobjects yes) you can use
# shareobjectspoolsize to control the size of the pool used in order to try
# object sharing. A bigger pool size will lead to better sharing capabilities.
# In general you want this value to be at least the double of the number of
# very common strings you have in your dataset.
#
# WARNING: object sharing is experimental, don't enable this feature
# in production before of Redis 1.0-stable. Still please try this feature in
# your development environment so that we can test it better.
# shareobjects no
# shareobjectspoolsize 1024

將附件中的redis_conf.rar解壓下來放到redis的根目錄中便可。到此，redis的安裝已經完畢。下面開始使用redis數據庫。

啓動redis：
輸入命令：redis-server.exe redis.conf
啓動後以下圖所示：


啓動cmd窗口要一直開着，關閉後則Redis服務關閉。
這時服務開啓着，另外開一個窗口進行，設置客戶端：
輸入命令：redis-cli.exe -h 202.117.16.133 -p 6379
輸入後以下圖所示：

而後能夠開始玩了。

這是我本地的測試：

Java中應用Redis

首先， 下載jedis.jar包：https://github.com/xetorthio/jedis/downloads 
添加到lib

而後 輸入命令：redis-server.exe redis.conf 開啓服務（必定要記得開啓服務哦）

import redis.clients.jedis.*;

public class Redis{
    public static void main(String args[]) {

        //鏈接redis服務
        Jedis jedis = new Jedis("192.168.1.102", 6379);          

        //密碼驗證-若是你沒有設置redis密碼可不驗證便可使用相關命令
        jedis.auth("abcdefg");

        //簡單的key-value 存儲
        jedis.set("tn", "thisuc");
        System.out.println(jedis.get("tn"));

        //在原有值得基礎上添加,如若以前沒有該key，則導入該key
        //以前已經設定了redis對應"myredis",此句執行便會使redis對應"myredisyourredis"
        jedis.append("redis", "yourredis");
        jedis.append("content", "rabbit");

        //mset 是設置多個key-value值 參數（key1,value1,key2,value2,...,keyn,valuen）
        //mget 是獲取多個key所對應的value值 參數（key1,key2,key3,...,keyn） 返回的是個list

        jedis.mset("name1","thisuc","name2","gaoxc","name3","lemon");
        System.out.println(jedis.mget("name1","name2","name3"));
    }
}

運行,以下顯示：

其餘方式請參考：http://yjc2020.iteye.com/blog/1128067

jedis實例請參考：http://spacecity.iteye.com/blog/1491928

===================================================

linux平臺Redis安裝：

wget http://code.google.com/p/redis/downloads/detail?name=redis-2.0.4.tar.gz
tar xvzf redis-2.0.4.tar.gz
cd  redis-2.0.4
make
mkdir /home/redis
cp redis-server  /home/redis
cp redis-benchmark  /home/redis
cp redis-cli  /home/redis
cp redis.conf  /home/redis
cd  /home/redis

在安裝過程當中可能須要用到sudo命令，可能新裝的redhat虛擬機中新用戶還不能使用sudo命令，所以須要手動的修改/etc/sudoers文件，命令以下：

cd /etc
su root ##切換爲root用戶，同時輸入密碼
chmod u+w sudoers ##放開sudoers文件的寫權限
##在root ALL = (ALL) ALL下面一行增長 "你的用戶名" ALL = (ALL) ALL
:wq ##保存退出
chmod u-w sudoers ##取消修改權限

啓動
./redis-server redis.conf
進入命令交互模式，兩種：
1:   ./redis-cli
2:   telnet 127.0.0.1 6379       (ip接端口)

=============================================================
配置文件參數說明:

1. Redis默認不是以守護進程的方式運行，能夠經過該配置項修改，使用yes啓用守護進程
    daemonize no
2. 當Redis以守護進程方式運行時，Redis默認會把pid寫入/var/run/redis.pid文件，能夠經過pidfile指定
    pidfile /var/run/redis.pid
3. 指定Redis監聽端口，默認端口爲6379，做者在本身的一篇博文中解釋了爲何選用6379做爲默認端口，由於6379在手機按鍵上MERZ對應的號碼，而MERZ取自意大利歌女Alessia Merz的名字
    port 6379
4. 綁定的主機地址
    bind 127.0.0.1
5.當 客戶端閒置多長時間後關閉鏈接，若是指定爲0，表示關閉該功能
    timeout 300
6. 指定日誌記錄級別，Redis總共支持四個級別：debug、verbose、notice、warning，默認爲verbose
    loglevel verbose
7. 日誌記錄方式，默認爲標準輸出，若是配置Redis爲守護進程方式運行，而這裏又配置爲日誌記錄方式爲標準輸出，則日誌將會發送給/dev/null
    logfile stdout
8. 設置數據庫的數量，默認數據庫爲0，可使用SELECT <dbid>命令在鏈接上指定數據庫id
    databases 16
9. 指定在多長時間內，有多少次更新操做，就將數據同步到數據文件，能夠多個條件配合
    save <seconds> <changes>
    Redis默認配置文件中提供了三個條件：
    save 900 1
    save 300 10
    save 60 10000
    分別表示900秒（15分鐘）內有1個更改，300秒（5分鐘）內有10個更改以及60秒內有10000個更改。

10. 指定存儲至本地數據庫時是否壓縮數據，默認爲yes，Redis採用LZF壓縮，若是爲了節省CPU時間，能夠關閉該選項，但會致使數據庫文件變的巨大
    rdbcompression yes
11. 指定本地數據庫文件名，默認值爲dump.rdb
    dbfilename dump.rdb
12. 指定本地數據庫存放目錄
    dir ./
13. 設置當本機爲slav服務時，設置master服務的IP地址及端口，在Redis啓動時，它會自動從master進行數據同步
    slaveof <masterip> <masterport>
14. 當master服務設置了密碼保護時，slav服務鏈接master的密碼
    masterauth <master-password>
15. 設置Redis鏈接密碼，若是配置了鏈接密碼，客戶端在鏈接Redis時須要經過AUTH <password>命令提供密碼，默認關閉
    requirepass foobared
16. 設置同一時間最大客戶端鏈接數，默認無限制，Redis能夠同時打開的客戶端鏈接數爲Redis進程能夠打開的最大文件描述符數，若是設置 maxclients 0，表示不做限制。當客戶端鏈接數到達限制時，Redis會關閉新的鏈接並向客戶端返回max number of clients reached錯誤信息
    maxclients 128
17. 指定Redis最大內存限制，Redis在啓動時會把數據加載到內存中，達到最大內存後，Redis會先嚐試清除已到期或即將到期的Key，當此方法處理 後，仍然到達最大內存設置，將沒法再進行寫入操做，但仍然能夠進行讀取操做。Redis新的vm機制，會把Key存放內存，Value會存放在swap區
    maxmemory <bytes>
18. 指定是否在每次更新操做後進行日誌記錄，Redis在默認狀況下是異步的把數據寫入磁盤，若是不開啓，可能會在斷電時致使一段時間內的數據丟失。由於 redis自己同步數據文件是按上面save條件來同步的，因此有的數據會在一段時間內只存在於內存中。默認爲no
    appendonly no
19. 指定更新日誌文件名，默認爲appendonly.aof
     appendfilename appendonly.aof
20. 指定更新日誌條件，共有3個可選值：
    no：表示等操做系統進行數據緩存同步到磁盤（快）
    always：表示每次更新操做後手動調用fsync()將數據寫到磁盤（慢，安全）
    everysec：表示每秒同步一次（折衷，默認值）
    appendfsync everysec

21. 指定是否啓用虛擬內存機制，默認值爲no，簡單的介紹一下，VM機制將數據分頁存放，由Redis將訪問量較少的頁即冷數據swap到磁盤上，訪問多的頁面由磁盤自動換出到內存中（在後面的文章我會仔細分析Redis的VM機制）
     vm-enabled no
22. 虛擬內存文件路徑，默認值爲/tmp/redis.swap，不可多個Redis實例共享
     vm-swap-file /tmp/redis.swap
23. 將全部大於vm-max-memory的數據存入虛擬內存,不管vm-max-memory設置多小,全部索引數據都是內存存儲的(Redis的索引數據 就是keys),也就是說,當vm-max-memory設置爲0的時候,實際上是全部value都存在於磁盤。默認值爲0
     vm-max-memory 0
24. Redis swap文件分紅了不少的page，一個對象能夠保存在多個page上面，但一個page上不能被多個對象共享，vm-page-size是要根據存儲的 數據大小來設定的，做者建議若是存儲不少小對象，page大小最好設置爲32或者64bytes；若是存儲很大大對象，則可使用更大的page，若是不 肯定，就使用默認值
     vm-page-size 32
25. 設置swap文件中的page數量，因爲頁表（一種表示頁面空閒或使用的bitmap）是在放在內存中的，，在磁盤上每8個pages將消耗1byte的內存。
     vm-pages 134217728
26. 設置訪問swap文件的線程數,最好不要超過機器的核數,若是設置爲0,那麼全部對swap文件的操做都是串行的，可能會形成比較長時間的延遲。默認值爲4
     vm-max-threads 4
27. 設置在向客戶端應答時，是否把較小的包合併爲一個包發送，默認爲開啓
    glueoutputbuf yes
28. 指定在超過必定的數量或者最大的元素超過某一臨界值時，採用一種特殊的哈希算法
    hash-max-zipmap-entries 64
    hash-max-zipmap-value 512
29. 指定是否激活重置哈希，默認爲開啓（後面在介紹Redis的哈希算法時具體介紹）
    activerehashing yes
30. 指定包含其它的配置文件，能夠在同一主機上多個Redis實例之間使用同一份配置文件，而同時各個實例又擁有本身的特定配置文件
    include /path/to/local.conf