-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error log #5137
Labels
Comments
This seems to be related to #5135. |
@luo985, can you share more details about this configuration so we can reproduce the issue? |
locao
added
the
pending author feedback
Waiting for the issue author to get back to a maintainer with findings, more details, etc...
label
Nov 12, 2019
@locao, i'm not sure what caused the problem. my config:
upstream config:
do you need any other information? |
locao
removed
the
pending author feedback
Waiting for the issue author to get back to a maintainer with findings, more details, etc...
label
Nov 19, 2019
locao
added a commit
to Kong/lua-resty-healthcheck
that referenced
this issue
Nov 22, 2019
When ngx.sleep API is not available (e.g. in the log phase) it's not possible to lock using lua-resty-lock and functions that must run protected were failing. This change adds a retry method that starts a new light thread that has access to ngx.sleep and will succeed to lock. Fix Kong/kong#5137
locao
added a commit
to Kong/lua-resty-healthcheck
that referenced
this issue
Dec 13, 2019
When ngx.sleep API is not available (e.g. in the log phase) it's not possible to lock using lua-resty-lock and functions that must run protected were failing. This change adds retry methods that start new light threads that have access to ngx.sleep and will succeed to lock. Fix Kong/kong#5137
hishamhm
pushed a commit
to Kong/lua-resty-healthcheck
that referenced
this issue
Dec 13, 2019
When ngx.sleep API is not available (e.g. in the log phase) it's not possible to lock using lua-resty-lock and functions that must run protected were failing. This change adds retry methods that start new light threads that have access to ngx.sleep and will succeed to lock. Fix Kong/kong#5137
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i found some error log, is this a issue?
The text was updated successfully, but these errors were encountered: