upstream module; scope of "set_peer_down"

thijs · 2016-03-10T17:50:37+00:00

Hello! On Wed, Mar 9, 2016 at 12:20 AM, Dmitry Belyaev wrote: > I'm receiving the error: > [error] 9375#0: *1 lua entry thread aborted: runtime error:...

upstream module; scope of "set_peer_down"

thijs

Hi,

When using the upstream module; https://github.com/openresty/lua-upstream-nginx-module, if setting the peer down status using "set_peer_down", should I be doing that from each worker?

or stated otherwise; does "set_peer_down" operate on a global nginx scope, or is the scope local to the worker?

regards

Thijs

agentzh

Hello!

On Thu, Mar 10, 2016 at 1:50 AM, Thijs Schreijer wrote:
> When using the upstream module;
> https://github.com/openresty/lua-upstream-nginx-module, if setting the peer
> down status using "set_peer_down", should I be doing that from each worker?
>
> or stated otherwise; does "set_peer_down" operate on a global nginx scope,
> or is the scope local to the worker?
>

It's worker-wise. Though other workers will catch up on the next tick via shm.

Regards,
-agentzh

agentzh

Hello!

On Wed, Mar 16, 2016 at 12:35 PM, Yichun Zhang (agentzh) wrote:
>
> It's worker-wise. Though other workers will catch up on the next tick via shm.
>

It's worth noting that the sync'ing part is not the duty of this
ngx_lua_upstream module though. For example,
lua-resty-upstream-healthcheck takes care of it itself.

Regards,
-agentzh

thijs

> -----Oorspronkelijk bericht-----
> Van: openresty-en@googlegroups.com [mailto:openresty-en@googlegroups.com]
> Namens Yichun Zhang (agentzh)
> Verzonden: Wednesday, 16 March, 2016 20:36
> Aan: openresty-en
> Onderwerp: Re: [openresty-en] upstream module; scope of "set_peer_down"
> 
> Hello!
> 
> On Thu, Mar 10, 2016 at 1:50 AM, Thijs Schreijer wrote:
> > When using the upstream module;
> > https://github.com/openresty/lua-upstream-nginx-module, if setting the
> > peer down status using "set_peer_down", should I be doing that from each
> worker?
> >
> > or stated otherwise; does "set_peer_down" operate on a global nginx
> > scope, or is the scope local to the worker?
> >
> 
> It's worker-wise. Though other workers will catch up on the next tick via
> shm.
> 
> Regards,
> -agentzh
> 

Yes, noticed something similar in the healthcheck module.

thijs

> -----Oorspronkelijk bericht-----
> Van: openresty-en@googlegroups.com [mailto:openresty-en@googlegroups.com]
> Namens Yichun Zhang (agentzh)
> Verzonden: Wednesday, 16 March, 2016 20:37
> Aan: openresty-en
> Onderwerp: Re: [openresty-en] upstream module; scope of "set_peer_down"
> 
> Hello!
> 
> On Wed, Mar 16, 2016 at 12:35 PM, Yichun Zhang (agentzh) wrote:
> >
> > It's worker-wise. Though other workers will catch up on the next tick
> via shm.
> >
> 
> It's worth noting that the sync'ing part is not the duty of this
> ngx_lua_upstream module though. For example, lua-resty-upstream-
> healthcheck takes care of it itself.
> 
> Regards,
> -agentzh
> 

Haha, just replied the same.

So in general; does each worker in nginx/openresty get the overall nginx config (as in the config file) as know (in the master process) at worker creation time?

agentzh

Hello!

On Wed, Mar 16, 2016 at 12:41 PM, Thijs Schreijer wrote:
> So in general; does each worker in nginx/openresty get the overall nginx config (as in the config file) as know (in the master process) at worker creation time?
>

Yes. NGINX uses fork() to create worker processes after the master
loads the configuration file (and runs init_by_lua* and etc).

Regards,
-agentzh