lua-upstream-nginx-module

erik.l.nelson · 2016-12-29T04:52:26+00:00

Do you have a example of a cmd script sending a status code when PHP crashes or that does not exist either ?On Saturday, 31 December 2016 12:59:32 UTC, nginx...

lua-upstream-nginx-module

erik.l.nelson

lua-upstream-nginx-module has in its TODO a comment about adding or removing servers from existing upstream groups... has that been subsumed by the work in ngx.balancer?  Or is there a finer point that I'm missing?

----------------------------------------------------------------------
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer.   If you are not the intended recipient, please delete this message.

rpaprocki

I think these two projects handle (fairly slightly different things). lua-upstream-nginx-module provides an API for managing upstreams (well, upstream nodes, really), while ngx.balancer is designed to select an arbitrary upstream peer for _every_ request. If you don't need the overhead or complexity of using a lua handler to select an upstream for every request, and just want to build a wrapper/API handler for updating a pre-defined upstream group every once in a while, lua-upstream-nginx-module is probably the best bet. If you have complex upstream proxying needs, the latter is what you need.

My $0.02, it'd be worth adding a node add/remove feature to lua-upstream-nginx-module. My guess is it wouldn't be _too_ difficult (iirc peer data is kept in a shared memory zone).

On Wed, Dec 28, 2016 at 12:52 PM, 'Nelson, Erik - 2' via openresty-en <openresty-en@googlegroups.com> wrote:

lua-upstream-nginx-module has in its TODO a comment about adding or removing servers from existing upstream groups... has that been subsumed by the work in ngx.balancer? Or is there a finer point that I'm missing?

----------------------------------------------------------------------
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.
.

rpaprocki

Actually, based on https://github.com/openresty/lua-upstream-nginx-module/pull/13, it looks like ngx.balancer is the universally recommended way to go. Doesn't look like there's much interest in merging that PR (or similar work).

On Thursday, December 29, 2016 at 8:54:33 PM UTC-8, rpaprocki wrote:

I think these two projects handle (fairly slightly different things). lua-upstream-nginx-module provides an API for managing upstreams (well, upstream nodes, really), while ngx.balancer is designed to select an arbitrary upstream peer for _every_ request. If you don't need the overhead or complexity of using a lua handler to select an upstream for every request, and just want to build a wrapper/API handler for updating a pre-defined upstream group every once in a while, lua-upstream-nginx-module is probably the best bet. If you have complex upstream proxying needs, the latter is what you need.

My $0.02, it'd be worth adding a node add/remove feature to lua-upstream-nginx-module. My guess is it wouldn't be _too_ difficult (iirc peer data is kept in a shared memory zone).

On Wed, Dec 28, 2016 at 12:52 PM, 'Nelson, Erik - 2' via openresty-en <openresty-en@googlegroups.com> wrote:
lua-upstream-nginx-module has in its TODO a comment about adding or removing servers from existing upstream groups... has that been subsumed by the work in ngx.balancer? Or is there a finer point that I'm missing?

----------------------------------------------------------------------
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.
.

erik.l.nelson

Thanks for the guidance, that’s very helpful. And on a slightly tangential topic, thanks much for your openresty contributions and packaging your libs for OPM.

From: openresty-en@googlegroups.com [mailto:openresty-en@googlegroups.com] On Behalf Of rpaprocki
Sent: Friday, December 30, 2016 12:28 AM
To: openresty-en
Cc: robert@cryptobells.com
Subject: Re: [openresty-en] lua-upstream-nginx-module

My $0.02, it'd be worth adding a node add/remove feature to lua-upstream-nginx-module. My guess is it wouldn't be _too_ difficult (iirc peer data is kept in a shared memory zone).

On Wed, Dec 28, 2016 at 12:52 PM, 'Nelson, Erik - 2' via openresty-en <openresty-en@googlegroups.com> wrote:

lua-upstream-nginx-module has in its TODO a comment about adding or removing servers from existing upstream groups... has that been subsumed by the work in ngx.balancer? Or is there a finer point that I'm missing?

----------------------------------------------------------------------
This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.
.

This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.