fix: running stale healthchecker when new node count <= 1#12118
Merged
Revolyssup merged 7 commits intoApr 7, 2025
Conversation
membphis
previously approved these changes
Apr 4, 2025
nic-6443
reviewed
Apr 6, 2025
membphis
approved these changes
Apr 7, 2025
nic-chen
approved these changes
Apr 7, 2025
nic-6443
approved these changes
Apr 7, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Problem description
The customer has a domain name configured with health check (the upstream type is K8S service discovery). Now it is found that after the upstream service node is updated, the nodes in the health check are not updated, resulting in a large number of health check failure logs:
*content:2025/03/28 16:36:17 [error] 42#42: 309692373 [lua] healthcheck.lua:1150: log(): [healthcheck] (upstream#/common/ontest/internal/routes/570) failed to send http request to 'nil (10.24.64.115:14699)': connection timed out, context: ngx.timer, client: 172.24.128.181, server: 0.0.0.0:9443
Reproduction steps
Solution
There are 3 possible solutions and in this PR I have decided to go with 1st one though reviewers can tell their opinion.
Fix can be any of the following
OR
OR
Conclusion
Solution 1 looks more general so we can go with it.
Logic of added test
Checklist