配置FastDFS時。改動配置文件是很是重要的一個步驟,理解配置文件裏每一項的意義更加劇要,因此我參考了大神的帖子,整理了配置文件的解釋。原帖例如如下:http://bbs.chinaunix.net/thread-1941456-1-1.html,因爲原帖中的版本號比較早。因此我針對現有的版本號進行了改動。原帖中沒有client.conf的介紹。這裏我給加上了。html
下文中帶有凝視的配置文件下載:http://download.csdn.net/detail/xingjiarong/9445515web
1、tracker.conf服務器
# 這個配置文件是否無效,false表示有效
# is this config file disabled
# false for enabled
# true for disabled
disabled=false
# 是否綁定IP
# bind_addr= 後面爲綁定的IP地址 (常用於服務器有多個IP但僅僅但願一個IP提供服務)。假設不填則表示所有的(通常不填就OK)
# bind an address of this host
# empty for bind all addresses of this host
bind_addr=
# 提供服務的端口
# the tracker server port
port=22122
# 鏈接超時時間,針對socket套接字函數connect
# connect timeout in seconds
# default value is 30s
connect_timeout=30
# tracker server的網絡超時,單位爲秒。發送或接收數據時。假設在超時時間後還不能發送或接收數據,則本次網絡通訊失敗 # network timeout in seconds # default value is 30s network_timeout=60 # the base path to store data and log files base_path=/home/yuqing/fastdfs # base_path 文件夾地址(根文件夾必須存在,子文件夾會本身主動建立) # 附文件夾說明: # tracker server文件夾及文件結構: # ${base_path} # |__data # | |__storage_groups.dat:存儲分組信息 # | |__storage_servers.dat:存儲服務器列表 # |__logs # |__trackerd.log:tracker server日誌文件 #數據文件storage_groups.dat和storage_servers.dat中的記錄之間以換行符(\n)分隔,字段之間以西文逗號(,)分隔。 #storage_groups.dat中的字段依次爲: # 1. group_name:組名 # 2. storage_port:storage server端口號 #storage_servers.dat中記錄storage server相關信息,字段依次爲: # 1. group_name:所屬組名 # 2. ip_addr:ip地址 # 3. status:狀態 # 4. sync_src_ip_addr:向該storage server同步已有數據文件的源服務器 # 5. sync_until_timestamp:同步已有數據文件的截至時間(UNIX時間戳) # 6. stat.total_upload_count:上傳文件次數 # 7. stat.success_upload_count:成功上傳文件次數 # 8. stat.total_set_meta_count:更改meta data次數 # 9. stat.success_set_meta_count:成功更改meta data次數 # 10. stat.total_delete_count:刪除文件次數 # 11. stat.success_delete_count:成功刪除文件次數 # 12. stat.total_download_count:下載文件次數 # 13. stat.success_download_count:成功下載文件次數 # 14. stat.total_get_meta_count:獲取meta data次數 # 15. stat.success_get_meta_count:成功獲取meta data次數 # 16. stat.last_source_update:近期一次源頭更新時間(更新操做來自客戶端) # 17. stat.last_sync_update:近期一次同步更新時間(更新操做來自其它storage server的同步) # 系統提供服務時的最大鏈接數。markdown
對於V1.x,因一個鏈接由一個線程服務,也就是工做線程數。 # 對於V2.x。最大鏈接數和工做線程數沒有不論什麼關係 # max concurrent connections this server supported max_connections=256 # work thread count, should <= max_connections # default value is 4 # since V2.00 # V2.0引入的這個參數,工做線程數,一般設置爲CPU數 work_threads=4 # 上傳組(卷) 的方式 0:輪詢方式 1: 指定組 2: 平衡負載(選擇最大剩餘空間的組(卷)上傳) # 這裏假設在應用層指定了上傳到一個固定組,那麼這個參數被繞過 # the method of selecting group to upload files # 0: round robin # 1: specify group # 2: load balance, select the max free space group to upload file store_lookup=2 # 當上一個參數設定爲1 時 (store_lookup=1,即指定組名時),必須設置本參數爲系統中存在的一個組名。假設選擇其它的上傳方式。這個參數就沒有效了 # which group to upload file # when store_lookup set to 1, must set store_group to the group name store_group=group2 # 選擇哪一個storage server 進行上傳操做(一個文件被上傳後,這個storage server就至關於這個文件的storage server源,會對同組的storage server推送這個文件達到同步效果) # 0: 輪詢方式 # 1: 依據ip 地址進行排序選擇第一個服務器(IP地址最小者) # 2: 依據優先級進行排序(上傳優先級由storage server來設置,參數名爲upload_priority) # which storage server to upload file # 0: round robin (default) # 1: the first server order by ip address # 2: the first server order by priority (the minimal) store_server=0 # 選擇storage server 中的哪一個文件夾進行上傳。網絡
storage server可以有多個存放文件的base path(可以理解爲多個磁盤)。app
# 0: 輪流方式。多個文件夾依次存放文件 # 2: 選擇剩餘空間最大的文件夾存放文件(注意:剩餘磁盤空間是動態的。所以存儲到的文件夾或磁盤可能也是變化的) # which path(means disk or mount point) of the storage server to upload file # 0: round robin # 2: load balance, select the max free space path to upload file store_path=0 # 選擇哪一個 storage server 做爲下載服務器 # 0: 輪詢方式,可以下載當前文件的任一storage server # 1: 哪一個爲源storage server 就用哪個 (前面說過了這個storage server源 是怎樣產生的) 就是以前上傳到哪一個storage server服務器就是哪一個了 # which storage server to download file # 0: round robin (default) # 1: the source storage server which the current file uploaded to download_server=0 # storage server 上保留的空間,保證系統或其它應用需求空間。可以用絕對值或者百分比(V4開始支持百分比方式)。 #(指出 假設同組的服務器的硬盤大小同樣,以最小的爲準,也就是僅僅要同組中有一臺服務器達到這個標準了,這個標準就生效,緣由就是因爲他們進行備份) # reserved storage space for system or other applications. # if the free(available) space of any stoarge server in # a group <= reserved_storage_space, # no file can be uploaded to this group. # bytes unit can be one of follows: ### G or g for gigabyte(GB) ### M or m for megabyte(MB) ### K or k for kilobyte(KB) ### no unit for byte(B) ### XX.XX% as ratio such as reserved_storage_space = 10% reserved_storage_space = 10% # 選擇日誌級別 #standard log level as syslog, case insensitive, value list: ### emerg for emergency ### alert ### crit for critical ### error ### warn for warning ### notice ### info ### debug log_level=info # 操做系統執行FastDFS的用戶組 (不填 就是當前用戶組,哪一個啓動進程就是哪一個) #unix group name to run this program, #not set (empty) means run by the group of current user run_by_group= # 操做系統執行FastDFS的用戶 (不填 就是當前用戶,哪一個啓動進程就是哪一個) #unix username to run this program, #not set (empty) means run by current user run_by_user= # 可以鏈接到此 tracker server 的ip範圍(對所有類型的鏈接都有影響,包含客戶端,storage server) # allow_hosts can ocur more than once, host can be hostname or ip address, # "*" means match all ip addresses, can use range like this: 10.0.1.[1-15,20] or # host[01-08,20-25].domain.com, for example: # allow_hosts=10.0.1.[1-15,20] # allow_hosts=host[01-08,20-25].domain.com allow_hosts=* # 同步或刷新日誌信息到硬盤的時間間隔,單位爲秒 # 注意:tracker server 的日誌不是時時寫硬盤的,而是先寫內存 # sync log buff to disk every interval seconds # default value is 10 seconds sync_log_buff_interval = 10 # 檢測 storage server 存活的時間隔,單位爲秒。 # storage server按期向tracker server 發心跳。假設tracker server在一個check_active_interval內尚未收到storage server的一次心跳,那邊將以爲該storage server已經下線。因此本參數值必須大於storage server配置的心跳時間間隔。一般配置爲storage server心跳時間間隔的2倍或3倍 # check storage server alive interval seconds check_active_interval = 120 # 線程棧的大小。less
FastDFS server端採用了線程方式。dom
tracker server線程棧不該小於64KB # 線程棧越大,一個線程佔用的系統資源就越多。socket
假設要啓動不少其它的線程(V1.x相應的參數爲max_connections, V2.0爲work_threads)。可以適當減小本參數值 # thread stack size, should >= 64KB # default value is 64KB thread_stack_size = 64KB # 這個參數控制當storage server IP地址改變時,集羣是否本身主動調整。tcp
注:僅僅有在storage server進程從新啓動時才完畢本身主動調整 # auto adjust when the ip address of the storage server changed # default value is true storage_ip_changed_auto_adjust = true # V2.0引入的參數。存儲服務器之間同步文件的最大延遲時間。缺省爲1天。
依據實際狀況進行調整 # 注:本參數並不影響文件同步過程。本參數僅在下載文件時,推斷文件是否已經被同步完畢的一個閥值(經驗值) # storage sync file max delay seconds # default value is 86400 seconds (one day) # since V2.00 storage_sync_file_max_delay = 86400 # V2.0引入的參數。存儲服務器同步一個文件需要消耗的最大時間。缺省爲300s。即5分鐘。
# 注:本參數並不影響文件同步過程。本參數僅在下載文件時,做爲推斷當前文件是否被同步完畢的一個閥值(經驗值) # the max time of storage sync a file # default value is 300 seconds # since V2.00 storage_sync_file_max_time = 300 # V3.0引入的參數。
是否使用小文件合併存儲特性,缺省是關閉的 # if use a trunk file to store several small files # default value is false # since V3.00 use_trunk_file = false # V3.0引入的參數。
# trunk file分配的最小字節數。比方文件僅僅有16個字節。系統也會分配slot_min_size個字節 # the min slot size, should <= 4KB # default value is 256 bytes # since V3.00 slot_min_size = 256 # V3.0引入的參數。 # 僅僅有文件大小<=這個參數值的文件。纔會合併存儲。
假設一個文件的大小大於這個參數值。將直接保存到一個文件裏(即不採用合併存儲方式)。 # the max slot size, should > slot_min_size # store the upload file to trunk file when it's size <= this value # default value is 16MB # since V3.00 slot_max_size = 16MB # V3.0引入的參數。 # 合併存儲的trunk file大小,至少4MB,缺省值是64MB。
不建議設置得過大 # the trunk file size, should >= 4MB # default value is 64MB # since V3.00 trunk_file_size = 64MB # 是否提早建立trunk file。僅僅有當這個參數爲true,如下3個以trunk_create_file_打頭的參數纔有效 # if create trunk file advancely # default value is false # since V3.06 trunk_create_file_advance = false # 提早建立trunk file的起始時間點(基準時間)。02:00表示第一次建立的時間點是凌晨2點 # the time base to create trunk file # the time format: HH:MM # default value is 02:00 # since V3.06 trunk_create_file_time_base = 02:00 # 建立trunk file的時間間隔,單位爲秒。假設天天僅僅提早建立一次,則設置爲86400 # the interval of create trunk file, unit: second # default value is 38400 (one day) # since V3.06 trunk_create_file_interval = 86400 # 提早建立trunk file時,需要達到的空暇trunk大小 # 比方本參數爲20G。而當前空暇trunk爲4GB,那麼僅僅需要建立16GB的trunk file就能夠 # the threshold to create trunk file # when the free trunk file size less than the threshold, will create # the trunk files # default value is 0 # since V3.06 trunk_create_file_space_threshold = 20G # trunk初始化時,是否檢查可用空間是否被佔用 # if check trunk space occupying when loading trunk free spaces # the occupied spaces will be ignored # default value is false # since V3.09 # NOTICE: set this parameter to true will slow the loading of trunk spaces # when startup. you should set this parameter to true when neccessary. trunk_init_check_occupying = false # 是否無條件從trunk binlog中載入trunk可用空間信息 # FastDFS缺省是從快照文件storage_trunk.dat中載入trunk可用空間。 # 該文件的第一行記錄的是trunk binlog的offset,而後從binlog的offset開始載入 # if ignore storage_trunk.dat, reload from trunk binlog # default value is false # since V3.10 # set to true once for version upgrade when your version less than V3.10 trunk_init_reload_from_binlog = false # 是否使用server ID做爲storage server標識 # if use storage ID instead of IP address # default value is false # since V4.00 use_storage_id = false # use_storage_id 設置爲true,才需要設置本參數 # 在文件裏設置組名、server ID和相應的IP地址。參見源代碼文件夾下的配置演示樣例:conf/storage_ids.conf # specify storage ids filename, can use relative or absolute path # since V4.00 storage_ids_filename = storage_ids.conf #文件名稱中的id類型,有ip和id兩種,僅僅有當use_storage_id設置爲true時該參數纔有效 # id type of the storage server in the filename, values are: ## ip: the ip address of the storage server ## id: the server id of the storage server # this paramter is valid only when use_storage_id set to true # default value is ip # since V4.03 id_type_in_filename = ip # 存儲從文件是否採用symbol link(符號連接)方式 # 假設設置爲true。一個從文件將佔用兩個文件:原始文件及指向它的符號連接 # if store slave file use symbol link # default value is false # since V4.01 store_slave_file_use_link = false # 是否認期輪轉error log。眼下僅支持一天輪轉一次 # if rotate the error log every day # default value is false # since V4.02 rotate_error_log = false # error log按期輪轉的時間點,僅僅有當rotate_error_log設置爲true時有效 # rotate error log time base, time format: Hour:Minute # Hour from 0 to 23, Minute from 0 to 59 # default value is 00:00 # since V4.02 error_log_rotate_time=00:00 # error log按大小輪轉 # 設置爲0表示不按文件大小輪轉。不然當error log達到該大小。就會輪轉到新文件裏 # rotate error log when the log file exceeds this size # 0 means never rotates log file by log file size # default value is 0 # since V4.02 rotate_error_log_size = 0 # 是否使用鏈接池 # if use connection pool # default value is false # since V4.05 use_connection_pool = false # 假設一個鏈接的空暇時間超過這個值將會被本身主動關閉 # connections whose the idle time exceeds this time will be closed # unit: second # default value is 3600 # since V4.05 connection_pool_max_idle_time = 3600 # 用於提供http服務的端口 # HTTP port on this tracker server http.server_port=8080 # 檢查http server是否還在工做的時間間隔。假設該值小於0則永遠不檢查 # check storage HTTP server alive interval seconds # <= 0 for never check # default value is 30 http.check_alive_interval=30 # 檢查http server是否存活的類型,有tcp和http兩種 # tcp方式僅僅有http端口被鏈接 # http方式檢查必須返回狀態值200 # check storage HTTP server alive type, values are: # tcp : connect to the storge server with HTTP port only, # do not request and get response # http: storage check alive url must return http status 200 # default value is tcp http.check_alive_type=tcp # check storage HTTP server alive uri/url # NOTE: storage embed HTTP server support uri: /status.html http.check_alive_uri=/status.html
2、storage.conf
# 這個配置文件是否無效,false表示有效
# is this config file disabled
# false for enabled
# true for disabled
disabled=false
# 指定 此 storage server 所在組(卷)
# the name of the group this storage server belongs to
group_name=group1
# 是否綁定IP
# bind_addr= 後面爲綁定的IP地址 (常用於服務器有多個IP但僅僅但願一個IP提供服務)。假設不填則表示所有的(通常不填就OK) # bind an address of this host # empty for bind all addresses of this host bind_addr= # bind_addr通常是針對server的。
當指定bind_addr時。本參數纔有效。
# 本storage server做爲client鏈接其它服務器(如tracker server、其它storage server)。是否綁定bind_addr。 # if bind an address of this host when connect to other servers # (this storage server as a client) # true for binding the address configed by above parameter: "bind_addr" # false for binding any address of this host client_bind=true # storage server服務端口 # the storage server port port=23000 # 鏈接超時時間,針對socket套接字函數connect # connect timeout in seconds # default value is 30s connect_timeout=30 # storage server 網絡超時時間,單位爲秒。發送或接收數據時,假設在超時時間後還不能發送或接收數據,則本次網絡通訊失敗。
# network timeout in seconds # default value is 30s network_timeout=60 # 心跳間隔時間。單位爲秒 (這裏是指主動向tracker server 發送心跳) # heart beat interval in seconds heart_beat_interval=30 # storage server向tracker server報告磁盤剩餘空間的時間間隔,單位爲秒 # disk usage report interval in seconds stat_report_interval=60 # base_path 文件夾地址,根文件夾必須存在 子文件夾會本身主動生成 (注 :這裏不是上傳的文件存放的地址,以前是的,在某個版本號後更改了) # the base path to store data and log files base_path=/home/yuqing/fastdfs # 系統提供服務時的最大鏈接數 # max concurrent connections the server supported # default value is 256 # more max_connections means more memory will be used max_connections=256 # V2.0引入本參數。
設置隊列結點的buffer大小。工做隊列消耗的內存大小 = buff_size * max_connections # 設置得大一些,系統整體性能會有所提高。 # 消耗的內存請不要超過系統物理內存大小。
另外,對於32位系統,請注意使用到的內存不要超過3GB # the buff size to recv / send data # this parameter must more than 8KB # default value is 64KB # since V2.00 buff_size = 256KB # 工做線程的數量。工做線程用於處理網絡IO,應當小於max_connections的值 # work thread count, should <= max_connections # work thread deal network io # default value is 4 # since V2.00 work_threads=4 # V2.0引入本參數。
磁盤IO讀寫是否分離。缺省是分離的 # if disk read / write separated ## false for mixed read and write ## true for separated read and write # default value is true # since V2.00 disk_rw_separated = true # V2.0引入本參數。針對單個存儲路徑的讀線程數。缺省值爲1。 # 讀寫分離時,系統中的讀線程數 = disk_reader_threads * store_path_count # 讀寫混合時,系統中的讀寫線程數 = (disk_reader_threads + disk_writer_threads) * store_path_count # disk reader thread count per store base path # for mixed read / write, this parameter can be 0 # default value is 1 # since V2.00 disk_reader_threads = 1 # V2.0引入本參數。針對單個存儲路徑的寫線程數,缺省值爲1。 # 讀寫分離時,系統中的寫線程數 = disk_writer_threads * store_path_count # 讀寫混合時,系統中的讀寫線程數 = (disk_reader_threads + disk_writer_threads) * store_path_count # disk writer thread count per store base path # for mixed read / write, this parameter can be 0 # default value is 1 # since V2.00 disk_writer_threads = 1 # 同步文件時,假設從binlog中沒有讀到要同步的文件。休眠N毫秒後又一次讀取。0表示不休眠,立刻再次嘗試讀取。 # 出於CPU消耗考慮,不建議設置爲0。怎樣但願同步儘量快一些,可以將本參數設置得小一些,比方設置爲10ms # when no entry to sync, try read binlog again after X milliseconds # must > 0, default value is 200ms sync_wait_msec=50 # 同步上一個文件後,再同步下一個文件的時間間隔。單位爲毫秒,0表示不休眠。直接同步下一個文件。
# after sync a file, usleep milliseconds # 0 for sync successively (never call usleep) sync_interval=0 # 如下二個一塊兒解釋。贊成系統同步的時間段 (默認是全天) 。通常用於避免高峯同步產生一些問題而設定,相信sa都會明確 # storage sync start time of a day, time format: Hour:Minute # Hour from 0 to 23, Minute from 0 to 59 sync_start_time=00:00 # storage sync end time of a day, time format: Hour:Minute # Hour from 0 to 23, Minute from 0 to 59 sync_end_time=23:59 # 同步完N個文件後,把storage的mark文件同步到磁盤 # 注:假設mark文件內容沒有變化,則不會同步 # write to the mark file after sync N files # default value is 500 write_mark_file_freq=500 # 存放文件時storage server支持多個路徑(好比磁盤)。這裏配置存放文件的基路徑數目。一般僅僅配一個文件夾。 # path(disk or mount point) count, default value is 1 store_path_count=1 # 逐一配置store_path個路徑,索引號基於0。注意配置方法後面有0,1,2 ......,需要配置0到store_path - 1。
# 假設不配置base_path0,那邊它就和base_path相應的路徑同樣。
# store_path#, based 0, if store_path0 not exists, it's value is base_path # the paths must be exist store_path0=/home/yuqing/fastdfs #store_path1=/home/yuqing/fastdfs2 # FastDFS存儲文件時,採用了兩級文件夾。
這裏配置存放文件的文件夾個數 (系統的存儲機制,你們看看文件存儲的文件夾就知道了) # 假設本參數僅僅爲N(如:256),那麼storage server在初次執行時。會本身主動建立 N * N 個存放文件的子文件夾。 # subdir_count * subdir_count directories will be auto created under each # store_path (disk), value can be 1 to 256, default value is 256 subdir_count_per_path=256 # tracker_server 的列表 要寫端口的哦 (再次提醒是主動鏈接tracker_server ) # 有多個tracker server時,每個tracker server寫一行 # tracker_server can ocur more than once, and tracker_server format is # "host:port", host can be hostname or ip address tracker_server=192.168.209.121:22122 # 日誌級別 #standard log level as syslog, case insensitive, value list: ### emerg for emergency ### alert ### crit for critical ### error ### warn for warning ### notice ### info ### debug log_level=info # 操做系統執行FastDFS的用戶組 (不填 就是當前用戶組,哪一個啓動進程就是哪一個) #unix group name to run this program, #not set (empty) means run by the group of current user run_by_group= # 操做系統執行FastDFS的用戶 (不填 就是當前用戶,哪一個啓動進程就是哪一個) #unix username to run this program, #not set (empty) means run by current user run_by_user= # 贊成鏈接本storage server的IP地址列表 (不包含自帶HTTP服務的所有鏈接) # 可以配置多行,每行都會起做用 # allow_hosts can ocur more than once, host can be hostname or ip address, # "*" means match all ip addresses, can use range like this: 10.0.1.[1-15,20] or # host[01-08,20-25].domain.com, for example: # allow_hosts=10.0.1.[1-15,20] # allow_hosts=host[01-08,20-25].domain.com allow_hosts=* # 文件在data文件夾下分散存儲策略。 # 0: 輪流存放。在一個文件夾下存儲設置的文件數後(參數file_distribute_rotate_count中設置文件數),使用下一個文件夾進行存儲。 # 1: 隨機存儲,依據文件名稱相應的hash code來分散存儲。
# the mode of the files distributed to the data path # 0: round robin(default) # 1: random, distributted by hash code file_distribute_path_mode=0 # 當上面的參數file_distribute_path_mode配置爲0(輪流存放方式)時,本參數有效。 # 當一個文件夾下的文件存放的文件數達到本參數值時,興許上傳的文件存儲到下一個文件夾中。 # valid when file_distribute_to_path is set to 0 (round robin), # when the written file count reaches this number, then rotate to next path # default value is 100 file_distribute_rotate_count=100 # 當寫入大文件時,每寫入N個字節,調用一次系統函數fsync將內容強行同步到硬盤。0表示從不調用fsync # call fsync to disk when write big file # 0: never call fsync # other: call fsync when written bytes >= this bytes # default value is 0 (never call fsync) fsync_after_written_bytes=0 # 同步或刷新日誌信息到硬盤的時間間隔,單位爲秒 # 注意:storage server 的日誌信息不是時時寫硬盤的。而是先寫內存。 # sync log buff to disk every interval seconds # must > 0, default value is 10 seconds sync_log_buff_interval=10 # 同步binglog(更新操做日誌)到硬盤的時間間隔。單位爲秒 # 本參數會影響新上傳文件同步延遲時間 # sync binlog buff / cache to disk every interval seconds # default value is 60 seconds sync_binlog_buff_interval=10 # 把storage的stat文件同步到磁盤的時間間隔,單位爲秒。
# 注:假設stat文件內容沒有變化,不會進行同步 # sync storage stat info to disk every interval seconds # default value is 300 seconds sync_stat_file_interval=300 # 線程棧的大小。
FastDFS server端採用了線程方式。
# 對於V1.x,storage server線程棧不該小於512KB;對於V2.0。線程棧大於等於128KB就能夠。
# 線程棧越大,一個線程佔用的系統資源就越多。
# 對於V1.x,假設要啓動不少其它的線程(max_connections),可以適當減小本參數值。 # thread stack size, should >= 512KB # default value is 512KB thread_stack_size=512KB # 本storage server做爲源服務器,上傳文件的優先級,可以爲負數。值越小。優先級越高。這裏就和 tracker.conf 中store_server= 2時的配置相相應了 # the priority as a source server for uploading file. # the lower this value, the higher its uploading priority. # default value is 10 upload_priority=10 # 網卡別名前綴,就像Linux中的eth,可以使用ifconfig -a命令來查看 # 多個別名之間使用逗號分隔。假設不設置這個值表示本身主動的被系統類型設置 # the NIC alias prefix, such as eth in Linux, you can see it by ifconfig -a # multi aliases split by comma. empty value means auto set by OS type # default values is empty if_alias_prefix= # 是否檢測上傳文件已經存在。假設已經存在,則不存在文件內容,創建一個符號連接以節省磁盤空間。 # 這個應用要配合FastDHT 使用。因此打開前要先安裝FastDHT # 1或yes 是檢測,0或no 是不檢測 # if check file duplicate, when set to true, use FastDHT to store file indexes # 1 or yes: need check # 0 or no: do not check # default value is 0 check_file_duplicate=0 # 文件去重時,文件內容的簽名方式: # hash: 4個hash code # md5:MD5 # file signature method for check file duplicate ## hash: four 32 bits hash code ## md5: MD5 signature # default value is hash # since V4.01 file_signature_method=hash # 當上個參數設定爲1 或 yes時 (true/on也是可以的) 。 在FastDHT中的命名空間 # namespace for storing file indexes (key-value pairs) # this item must be set when check_file_duplicate is true / on key_namespace=FastDFS # 與FastDHT servers 的鏈接方式 (是否爲持久鏈接) 。默認是0(短鏈接方式)。可以考慮使用長鏈接,這要看FastDHT server的鏈接數是否夠用。 # set keep_alive to 1 to enable persistent connection with FastDHT servers # default value is 0 (short connection) keep_alive=0 # 如下是關於FastDHT servers 的設定 需要對FastDHT servers 有所瞭解,這裏僅僅說字面意思了 # 可以經過 #include filename 方式來載入 FastDHT servers 的配置。裝上FastDHT就知道該怎樣配置啦。 # 相同要求 check_file_duplicate=1 時才實用。否則系統會忽略 # fdht_servers.conf 記載的是 FastDHT servers 列表 # you can use "#include filename" (not include double quotes) directive to # load FastDHT server list, when the filename is a relative path such as # pure filename, the base path is the base path of current/this config file. # must set FastDHT server list when check_file_duplicate is true / on # please see INSTALL of FastDHT for detail ##include /home/yuqing/fastdht/conf/fdht_servers.conf # 是否將文件操做記錄到access log # if log to access log # default value is false # since V4.00 use_access_log = false # 是否認期輪轉access log。眼下僅支持一天輪轉一次 # if rotate the access log every day # default value is false # since V4.00 rotate_access_log = false # access log按期輪轉的時間點,僅僅有當rotate_access_log設置爲true時有效 # rotate access log time base, time format: Hour:Minute # Hour from 0 to 23, Minute from 0 to 59 # default value is 00:00 # since V4.00 access_log_rotate_time=00:00 # 是否認期輪轉error log。眼下僅支持一天輪轉一次 # if rotate the error log every day # default value is false # since V4.02 rotate_error_log = false # error log按期輪轉的時間點。僅僅有當rotate_error_log設置爲true時有效 # rotate error log time base, time format: Hour:Minute # Hour from 0 to 23, Minute from 0 to 59 # default value is 00:00 # since V4.02 error_log_rotate_time=00:00 # access log按文件大小輪轉 # 設置爲0表示不按文件大小輪轉。不然當access log達到該大小。就會輪轉到新文件裏 # rotate access log when the log file exceeds this size # 0 means never rotates log file by log file size # default value is 0 # since V4.02 rotate_access_log_size = 0 # error log按文件大小輪轉 # 設置爲0表示不按文件大小輪轉,不然當error log達到該大小,就會輪轉到新文件裏 # rotate error log when the log file exceeds this size # 0 means never rotates log file by log file size # default value is 0 # since V4.02 rotate_error_log_size = 0 # 文件同步的時候,是否忽略無效的binlog記錄 # if skip the invalid record when sync file # default value is false # since V4.02 file_sync_skip_invalid_record=false # 是否使用鏈接池 # if use connection pool # default value is false # since V4.05 use_connection_pool = false # 假設一個鏈接的空暇時間超過這個值將會被本身主動關閉 # connections whose the idle time exceeds this time will be closed # unit: second # default value is 3600 # since V4.05 connection_pool_max_idle_time = 3600 # storage server上web server域名。一般僅針對單獨部署的web server。
這樣URL中就可以經過域名方式來訪問storage server上的文件了, # 這個參數爲空就是IP地址的方式。 # use the ip address of this storage server if domain_name is empty, # else this domain name will ocur in the url redirected by the tracker server http.domain_name= # web server的端口 # the port of the web server on this storage server http.server_port=8888
3、client.conf
# 鏈接超時時間,針對socket套接字函數connect
# connect timeout in seconds
# default value is 30s
connect_timeout=30
# client的網絡超時,單位爲秒。發送或接收數據時。假設在超時時間後還不能發送或接收數據,則本次網絡通訊失敗 # network timeout in seconds # default value is 30s network_timeout=60 # 存儲日誌的根文件夾 # the base path to store log files base_path=/home/yuqing/fastdfs # tracker_server 的列表 要寫端口 # tracker_server can ocur more than once, and tracker_server format is # "host:port", host can be hostname or ip address tracker_server=192.168.0.197:22122 # 日誌的級別 #standard log level as syslog, case insensitive, value list: ### emerg for emergency ### alert ### crit for critical ### error ### warn for warning ### notice ### info ### debug log_level=info # 是否使用鏈接池 # if use connection pool # default value is false # since V4.05 use_connection_pool = false # 假設一個鏈接的空暇時間超過這個值將會被本身主動關閉 # connections whose the idle time exceeds this time will be closed # unit: second # default value is 3600 # since V4.05 connection_pool_max_idle_time = 3600 # 是否從FastDFS的tracker server載入參數 # if load FastDFS parameters from tracker server # since V4.05 # default value is false load_fdfs_parameters_from_tracker=false 是否使用storage ID 取代IP,僅僅有當load_fdfs_parameters_from_tracker爲false時纔有效 # if use storage ID instead of IP address # same as tracker.conf # valid only when load_fdfs_parameters_from_tracker is false # default value is false # since V4.05 use_storage_id = false # 指定storage_ids的路徑,可以使用絕對路徑和相對路徑,僅僅有當load_fdfs_parameters_from_tracker爲false時纔有效 # specify storage ids filename, can use relative or absolute path # same as tracker.conf # valid only when load_fdfs_parameters_from_tracker is false # since V4.05 storage_ids_filename = storage_ids.conf #tracker server的http端口 #HTTP settings http.tracker_server_port=8080 #use "#include" directive to include HTTP other settiongs ##include http.conf