ngx_http_lua_upstream - Nginx C module to expose Lua API to ngx_lua for Nginx upstreams
This module is production ready.
stream {
upstream foo.com {
server 127.0.0.1 fail_timeout=53 weight=4 max_fails=100;
server agentzh.org:81;
}
upstream bar {
server 127.0.0.2:80;
}
}
http {
server {
listen 8080;
# sample output for the following /upstream interface:
# upstream foo.com:
# addr = 127.0.0.1:80, weight = 4, fail_timeout = 53, max_fails = 100
# addr = 106.184.1.99:81, weight = 1, fail_timeout = 10, max_fails = 1
# upstream bar:
# addr = 127.0.0.2:80, weight = 1, fail_timeout = 10, max_fails = 1
location = /upstreams {
default_type text/plain;
content_by_lua_block {
local concat = table.concat
local upstream = require "ngx.upstream.stream"
local get_servers = upstream.get_servers
local get_upstreams = upstream.get_upstreams
local us = get_upstreams()
for _, u in ipairs(us) do
ngx.say("upstream ", u, ":")
local srvs, err = get_servers(u)
if not srvs then
ngx.say("failed to get servers in upstream ", u)
else
for _, srv in ipairs(srvs) do
local first = true
for k, v in pairs(srv) do
if first then
first = false
ngx.print(" ")
else
ngx.print(", ")
end
if type(v) == "table" then
ngx.print(k, " = {", concat(v, ", "), "}")
else
ngx.print(k, " = ", v)
end
end
ngx.print("\n")
end
end
end
}
}
}
}
syntax: names = upstream.get_upstreams()
Get a list of the names for all the named upstream groups (i.e., explicit upstream {}
blocks).
Note that implicit upstream groups created by proxy_pass
and etc are excluded.
syntax: servers = upstream.get_servers(upstream_name)
Get configurations for all the servers in the specified upstream group. Please one server may take multiple addresses when its server name can be resolved to multiple addresses.
The return value is an array-like Lua table. Each table entry is a hash-like Lua table that takes the following keys:
-
addr
socket address(es). can be either a Lua string or an array-like Lua table of Lua strings.
-
backup
-
fail_timeout
-
max_fails
-
name
-
weight
syntax: peers = upstream.get_primary_peers(upstream_name)
Get configurations for all the primary (non-backup) peers in the specified upstream group.
The return value is an array-like Lua table for all the primary peers. Each table entry is a (nested) hash-like Lua table that takes the following keys:
-
current_weight
-
effective_weight
-
fail_timeout
-
fails
-
id
Identifier (ID) for the peer. This ID can be used to reference a peer in a group in the peer modifying API.
-
max_fails
-
name
Socket address for the current peer
-
weight
-
accessed
Timestamp for the last access (in seconds since the Epoch)
-
checked
Timestamp for the last check (in seconds since the Epoch)
-
down
Holds true if the peer has been marked as "down", otherwise this key is not present
-
conns
Number of active connections to the peer (this requires NGINX 1.9.0 or above).
syntax: peers = upstream.get_backup_peers(upstream_name)
Get configurations for all the backup peers in the specified upstream group.
The return value has the same structure as get_primary_peers function.
syntax: ok, err = upstream.set_peer_down(upstream_name, is_backup, peer_id, down_value)
Set the "down" (boolean) attribute of the specified peer.
To uniquely specify a peer, you need to specify the upstream name, whether or not it is a backup peer, and the peer id (starting from 0).
Note that this method only changes the peer settings in the current Nginx worker process. You need to synchronize the changes across all the Nginx workers yourself if you want a server-wide change (for example, by means of ngx_lua's ngx.shared.DICT).
Below is an example. Consider we have a "bar" upstream block in nginx.conf
:
upstream bar {
server 127.0.0.2;
server 127.0.0.3 backup;
server 127.0.0.4 fail_timeout=23 weight=7 max_fails=200 backup;
}
then
upstream.set_peer_down("bar", false, 0, true)
will turn down the primary peer corresponding to server 127.0.0.2
.
Similarly,
upstream.set_peer_down("bar", true, 1, true)
will turn down the backup peer corresponding to server 127.0.0.4 ...
.
You can turn on a peer again by providing a false
value as the 4th argument.
syntax: name = upstream.current_upstream_name()
Returns the name of the proxied upstream for the current request.
If there is no upstream for this request (no proxy_pass
call), or this
function is called in a phase prior to the content phase, then the return value
will be nil
. If a port is explicitly included in the upstream definition or
proxy_pass
directive, it will be included in the return value of this function.
Example:
-- upstream my_upstream { ... }
-- proxy_pass my_upstream;
upstream.current_upstream_name() --> my_upstream
-- proxy_pass example.com:1234;
upstream.current_upstream_name() --> example.com:1234
Note that implicit upstreams created by proxy_pass
are included, contrary to
the output of upstream.get_upstreams()
.
- Add API to add or remove servers to existing upstream groups.
The following versions of Nginx should work with this module:
- 1.11.x (last tested: 1.11.6)
Launch build.sh.
Yichun "agentzh" Zhang (章亦春) agentzh@gmail.com, CloudFlare Inc.
Aleksey Konovkin "ZigzagAK" alkon2000@mail.ru.
This module is licensed under the BSD license.
Copyright (C) 2014-2016, by Yichun "agentzh" Zhang, CloudFlare Inc.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
-
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
-
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.