先從下列結構體開始,他也被包含在ngx_http_upstream_srv_conf_s結構中
<code><span>typedef</span><span>struct</span> { <span>/*typedef ngx_int_t (*ngx_http_upstream_init_pt)(ngx_conf_t*cf,ngx_http_upstream_srv_conf_t *us);*/</span> ngx_http_upstream_init_pt init_upstream; ngx_http_upstream_init_peer_pt init; <span>void</span> *data; } ngx_http_upstream_peer_t</code>
以下重點分析下兩個成員變數init_upstream和init
init_init_init_uppstream >每個upsteam配置區塊塊執行一次;
可透過配置keepalive或ip_hash功能配置,即碰到keepalive或ip_hash配置被調用,如果沒有配置預設實作為ngx_http_upstream_init_round_robin函數,在配置初始化函數ngx_http_upstream_init_main_conf被調用,預設為主要功能是有2個 >
us->servers陣列中取得資料初始化ngx_http_upstream_rr_peers_t結構存房子us->peer.data中供init函式使用;
init函數對於每一個到oringin的請求執行一次;
<code>struct ngx_peer_connection_s { ngx_connection_t <span>*</span>connection; struct sockaddr <span>*</span>sockaddr; socklen_t socklen; ngx_str_t <span>*</span>name; ngx_uint_t tries; ngx_msec_t start_time; <span>/*类型typedef ngx_int_t (*ngx_event_get_peer_pt)(ngx_peer_connection_t *pc, void *data);*/</span><span>/* 上面init的函数中被配置,如果配置了keepalive且从cache中找到了connection将返回NGX_DONE,*/</span><span>/* 且设置复 用已经存在的连接,如果没有配置keepalive或者,没有找到存在的connection,*/</span><span>/*但找到了下一跳地址,将返回NGX_OK,*/</span> ngx_event_get_peer_pt get; <span>/*,同样在init中被设置,连接释放时被调用*/</span> ngx_event_free_peer_pt free; <span>/* 在init中被设置,用以保存init_upstream中生成的us->peer.data数据,在get和free方法中被使用*/</span><span>void</span><span>*</span><span>data</span>; <span>...</span><span>...</span><span>...</span> };</code>
ngx_http_upstream_init_request->ngx_http_upstream_connect->ngx_event_connect_peer->
rc = pc->get(pc, pc->data);
round_robin ,ip_hash,keepalive模組之間關係
round_robin和ip_hash模組都用於查找嚇一跳ip,keepalive功能用於找到嚇一跳ip位址之後,透過ip位址尋找是否已經存在可用的connection,所以兩個模組的get實作方式不同,ip_hash是現使用ip_hash找下一下,查找失敗後採用預設的round_robin功能,
而keepalive功能是在ip查找到之後才能使用,ip查找可以使用ip_hash的方法,也可以使用round_robin提供的方法,
如下
<code>static ngx_int_t ngx_http_upstream_init_keepalive_peer(ngx_http_request_t <span>*</span>r, ngx_http_upstream_srv_conf_t <span>*</span>us) { ngx_http_upstream_keepalive_peer_data_t <span>*</span>kp; ngx_http_upstream_keepalive_srv_conf_t <span>*</span>kcf; ngx_log_debug0(NGX_LOG_DEBUG_HTTP, r<span>-></span>connection<span>-></span><span>log</span>, <span>0</span>, <span>"init keepalive peer"</span>); kcf <span>=</span> ngx_http_conf_upstream_srv_conf(us, ngx_http_upstream_keepalive_module); kp <span>=</span> ngx_palloc(r<span>-></span>pool, sizeof(ngx_http_upstream_keepalive_peer_data_t)); <span>if</span> (kp <span>==</span><span>NULL</span>) { <span>return</span> NGX_ERROR; } <span>if</span> (kcf<span>-></span>original_init_peer(r, us) <span>!=</span> NGX_OK) { <span>return</span> NGX_ERROR; } kp<span>-></span>conf <span>=</span> kcf; kp<span>-></span>upstream <span>=</span> r<span>-></span>upstream; <span>/*保存默认的original_get_peer方法,仍将在新的get方法中被调用,r->upstream->peer.get;可以是round_robin,也可以是iphash模块提供的 */</span> kp<span>-></span>original_get_peer <span>=</span> r<span>-></span>upstream<span>-></span>peer<span>.</span>get; kp<span>-></span>original_free_peer <span>=</span> r<span>-></span>upstream<span>-></span>peer<span>.</span>free; <span>...</span><span>...</span><span>/*保存默认的在original_init_peer中初始化好的数据,get和free方法中需要使用*/</span> kp<span>-></span><span>data</span><span>=</span> r<span>-></span>upstream<span>-></span>peer<span>.</span><span>data</span>; <span>/*可以通过r->upstream->peer.data找到keepalive模块*/</span> r<span>-></span>upstream<span>-></span>peer<span>.</span><span>data</span><span>=</span> kp; <span>/*设置新的get和free钩子*/</span> r<span>-></span>upstream<span>-></span>peer<span>.</span>get <span>=</span> ngx_http_upstream_get_keepalive_peer; r<span>-></span>upstream<span>-></span>peer<span>.</span>free <span>=</span> ngx_http_upstream_free_keepalive_peer; <span>return</span> NGX_OK; } static ngx_int_t ngx_http_upstream_get_keepalive_peer(ngx_peer_connection_t <span>*</span>pc, <span>void</span><span>*</span><span>data</span>) { ngx_http_upstream_keepalive_peer_data_t <span>*</span>kp <span>=</span><span>data</span>; ngx_http_upstream_keepalive_cache_t <span>*</span>item; ngx_int_t rc; ngx_queue_t <span>*</span>q, <span>*</span><span>cache</span>; ngx_connection_t <span>*</span>c; <span>/* ask balancer 此源码注释应不准确*/</span><span>/*适用round_robin或者ip_hash等功能找到下一跳地址*/</span> rc <span>=</span> kp<span>-></span>original_get_peer(pc, kp<span>-></span><span>data</span>); <span>if</span> (rc <span>!=</span> NGX_OK) { <span>return</span> rc; } <span>/* search cache for suitable connection */</span><span>cache</span><span>=</span><span>&</span>kp<span>-></span>conf<span>-></span><span>cache</span>;</code>
可以看出keepalive類似於裝飾器模型,即在下一跳ip上增加一個keepalive的功能,keepalive包含origin實現的函數指針
而ip_hash和round_robin 能類似策略模型,也就是在init_upstream中設定對於request查找ip的不同策略。
而這三個模組整體關係,類似於建造者之間關係,即都必須實現且按順序調用init_upstream,init,get,free等函數。
後記:
round_robin多提供了一個create函數,用於upstream中resolved成員被設定的情況,例如透過
proxy_pass http://$vhost;的方式設定到origin的位址。 此時init被create代替,且不能在具有keepalive和ip_hash功能。 keepalive和iphash都只能用於upstream模組中。
以上就介紹了 nginx roundrobin 、keepalive、ip_hash模組分析,包括了方面的內容,希望對PHP教程有興趣的朋友有所幫助。