On Thu, Apr 23, 2020 at 2:54 PM [email protected] <[email protected]> wrote:

> @MembPhis,
> The timer delays adding targets, so it will get an error if use the
> get_target_status function to get the status of a node before the targets
> assigned.
> It's the best to use the get_target_status function by pcall, and use the
> default is_healthy status as result.
>
>
Thank you very much for your explanation.

We have released version 1.0.1 of lua-resty-healthcheck-iresty. It should
have solved this problem.


>
>
>
> [email protected]
>
> From: [email protected]
> Date: 2020-04-09 09:21
> To: dev
> Subject: Re: Re: the error happend when use the healthcheck to get the
> status of upstrems.
> @MembPhis, thanks for your reply,  I 'll use the
> lua-resty-healthcheck-api7 to update my scenarios.
>
>
>
> [email protected]
>
> From: [email protected]
> Date: 2020-04-03 09:22
> To: dev
> Subject: Re: Re: the error happend when use the healthcheck to get the
> status of upstrems.
> Thx.
>
>
>
> [email protected]
>
> From: YuanSheng Wang
> Date: 2020-04-02 11:58
> To: [email protected]
> Subject: Re: Re: the error happend when use the healthcheck to get the
> status of upstrems.
> I do not know how to fix it yet.
>
>
>
> On Wed, Apr 1, 2020 at 10:47 PM [email protected] <[email protected]> wrote:
>
> > Is there any way to avoid this?
> >
> >
> >
> > [email protected]
> >
> > From: YuanSheng Wang
> > Date: 2020-04-01 22:43
> > To: [email protected]
> > Subject: Re: the error happend when use the healthcheck to get the status
> > of upstrems.
> > That is a bug of lua-resty-healthcheck, here is the related issue [1].
> >
> > It is not easy to fix it.
> >
> > [1] https://github.com/Kong/lua-resty-healthcheck/issues/36
> >
> >
> >
> > On Wed, Apr 1, 2020 at 10:22 PM [email protected] <[email protected]> wrote:
> >
> > > I got the error when I use the healthcheck to get the status of
> upstrems.
> > > Has anyone ever had the same problem?
> > >
> > > Error:
> > > 2020/03/31 17:03:01 [error] 47#47: *128805375 failed to run
> > > balancer_by_lua*: /usr/local/openresty/lualib/resty/lock.lua:153: API
> > > disabled in the context of balancer_by_lua*
> > > stack traceback:
> > >         [C]: in function 'sleep'
> > >         /usr/local/openresty/lualib/resty/lock.lua:153: in function
> > 'lock'
> > >         /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:207: in
> > > function 'locking_target_list'
> > >         /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:1315:
> in
> > > function 'new'
> > >         /opt/app/mecs//lua/travelsky/http/checker.lua:25: in function
> > > 'create_obj_fun'
> > >         /opt/app/mdcs//lua/apisix/core/lrucache.lua:50: in function
> > > 'lrucache_checker'
> > >         /opt/app/mecs//lua/travelsky/http/checker.lua:35: in function
> > > 'fetch_checker'
> > >         /opt/app/mecs//lua/travelsky/http/balancer.lua:221: in function
> > > 'pick_server'
> > >         /opt/app/mecs//lua/travelsky/http/balancer.lua:287: in function
> > > 'load_balancer'
> > >         /opt/app/mecs//lua/travelsky.lua:259: in function
> > > 'http_balancer_phase'
> > >         balancer_by_lua:2: in main chunk while connecting to upstream,
> > > client: 101.5.19.12, server: , request: "POST / HTTP/1.1", host: "
> > > 101.5.19.15:8080"
> > >
> > >
> > >
> > >
> > > [email protected]
> > >
> >
> >
> > --
> > *MembPhis*
> > My github: https://github.com/membphis
> > Apache APISIX: https://github.com/apache/incubator-apisix
> >
>
>
> --
> *MembPhis*
> My github: https://github.com/membphis
> Apache APISIX: https://github.com/apache/incubator-apisix
>


-- 
*MembPhis*
My github: https://github.com/membphis
Apache APISIX: https://github.com/apache/incubator-apisix

Reply via email to