storage存儲節(jié)點同步問題和tracker之間調(diào)度問題

xuledw

請教下，我的測試tracker server
192.168.4.253
group1 中2個storage
192.168.4.252 nginx+mod_fastdfs
192.168.4.254 nginx+mod_fastdfs

2個問題
1 假設(shè)上傳文件較大，上傳到192.168.4.252 此時還沒沒有同步到192.168.4.254
那么如何保證用戶請求不落在192.168.4.254
  我這邊想在4.252和4.254之前搞一個nginx+upstream 分發(fā)請求到252、254
2 我從存儲節(jié)點上下載文件的時候，存儲節(jié)點和tracker server是否有數(shù)據(jù)交互？
  看到 nginx+mod_fastdfs有模塊調(diào)用mod_fastdfs.conf
tracker_server=192.168.4.253:22122
   但我抓包沒有發(fā)現(xiàn)有數(shù)據(jù)交互
謝謝


如下上傳文件
# /usr/local/bin/fdfs_test /etc/fdfs/client.conf upload install.log
This is FastDFS client test program v5.01

Copyright (C) 2008, Happy Fish / YuQing

FastDFS may be copied only under the terms of the GNU General
Public License V3, which may be found in the FastDFS source kit.
Please visit the FastDFS Home Page http://www.csource.org/
for more detail.

[2014-02-28 17:17:26] DEBUG - base_path=/home/yuqing/fastdfs, connect_timeout=30, network_timeout=60, tracker_server_count=1, anti_steal_token=0, anti_steal_secret_key length=0, use_connection_pool=0, g_connection_pool_max_idle_time=3600s, use_storage_id=0, storage server id count: 0

tracker_query_storage_store_list_without_group:
        server 1. group_name=, ip_addr=192.168.4.252, port=23000
        server 2. group_name=, ip_addr=192.168.4.254, port=23000

group_name=group1, ip_addr=192.168.4.252, port=23000
storage_upload_by_filename
group_name=group1, remote_filename=M00/00/00/wKgE_FMQVCWAMR4mAAAk8o19T2w416.log
source ip address: 192.168.4.252
file timestamp=2014-02-28 17:17:25
file size=9458
file crc32=2373799788
example file url: http://192.168.4.252:8080/group1 ... mAAAk8o19T2w416.log
storage_upload_slave_by_filename
group_name=group1, remote_filename=M00/00/00/wKgE_FMQVCWAMR4mAAAk8o19T2w416_big.log
source ip address: 192.168.4.252
file timestamp=2014-02-28 17:17:25
file size=9458
file crc32=2373799788
example file url: http://192.168.4.252:8080/group1 ... k8o19T2w416_big.log
假設(shè)我上傳的文件比較大
當(dāng)時在http://192.168.4.252:8080/group1 ... k8o19T2w416_big.log
已經(jīng)可以訪問
但是同步到同組另一個主機(jī)
http://192.168.4.254:8080/group1 ... k8o19T2w416_big.log 還需要時間
我如何解決 這個問題？

xuledw

自己更新下：
只有在本機(jī)并沒有需要獲取的資源的情況下，才會進(jìn)行特殊的處理。
當(dāng)同組內(nèi)其他Storeage新上傳的圖片本機(jī)并沒有及時同步的時候，Nginx會根據(jù)url尋找上傳的Storeage源服務(wù)器，進(jìn)行redirect或者proxy兩種方式之一的轉(zhuǎn)發(fā)。
測試如下：
刪除其中一個節(jié)點中的數(shù)據(jù)【非源數(shù)據(jù)192.168.4.254】然后通過http請求的這個不在本地磁盤的文件
會回源去請求文件【192.168.4.252】
在192.168.4.252上抓包tcpdump -i eth0 port 8080 分析
GET /group1/M00/00/00/wKgE_FMT_SmABZFXAAAE6F4aJyc89_big.conf?redirect=1  HTTP/1.0
User-Agent: Wget/1.11.4 Red Hat modified
Accept: */*
Host: 192.168.4.254:8080
Connection: Keep-Alive

HTTP/1.1 200 OK
Server: nginx/1.4.4
Date: Mon, 03 Mar 2014 09:05:05 GMT
Content-Length: 1256
Last-Modified: Mon, 03 Mar 2014 03:55:21 GMT
Connection: keep-alive
Accept-Ranges: bytes

disabled=false
group_name=group1
bind_addr=192.168.4.252
client_bind=true
port=23000
connect_timeout=30
network_timeout=60
heart_beat_interval=30
stat_report_interval=60
base_path=/home/yuqing/fastdfs
max_connections=256
buff_size = 256KB
accept_threads=1
work_threads=4
disk_rw_separated = true
disk_reader_threads = 1
disk_writer_threads = 1
sync_wait_msec=50
sync_interval=0
sync_start_time=00:00
sync_end_time=23:59
write_mark_file_freq=500
store_path_count=1
store_path0=/home/yuqing/fastdfs
subdir_count_per_path=256
tracker_server=192.168.4.253:22122
log_level=info
run_by_group=
run_by_user=
allow_hosts=*
file_distribute_path_mode=0
file_distribute_rotate_count=100
fsync_after_written_bytes=0
sync_log_buff_interval=10
sync_binlog_buff_interval=10
sync_stat_file_interval=300
thread_stack_size=512KB
upload_priority=10
if_alias_prefix=
check_file_duplicate=0
file_signature_method=hash
key_namespace=FastDFS
keep_alive=0
use_access_log = false
rotate_access_log = false
access_log_rotate_time=00:00
rotate_error_log = false
error_log_rotate_time=00:00
rotate_access_log_size = 0
rotate_error_log_size = 0
file_sync_skip_invalid_record=false
use_connection_pool = false
connection_pool_max_idle_time = 3600
http.domain_name=
http.server_port=8888