-
Notifications
You must be signed in to change notification settings - Fork 51
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
fix: fix delay clean logic when multiple healthchecker was started #146
Conversation
It seems openresty has been remove old package from you deb package managment source, So i remove openresty 1.19 test
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have some questions before moving forward with this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
@oowl Concerns from #146 (comment) will it happen? |
Yeah, It will happen in some cases, you can run the newly added test in the master branch code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code change LGTM
When we have many healthchecker instance, if we need to delay clear anyone, it will add all
delay_purge
number to these target table, And then wait active healthcheck timer to check these number flag to execute real clear logic. Ideally, it's work expected, but we have one for loop bug in clear logic. which will case delay clear logic just execute once for first healthchecker instance. So this will cause delay clear can not remove some target expectedly.https://github.com/Kong/lua-resty-healthcheck/blob/master/lib/resty/healthcheck.lua#L1725
FTI-5478