Skip to content
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

Health monitor server status #1988

Closed
const-t opened this issue Oct 18, 2023 · 7 comments
Closed

Health monitor server status #1988

const-t opened this issue Oct 18, 2023 · 7 comments
Assignees
Labels
question Questions and support tasks test
Milestone

Comments

@const-t
Copy link
Contributor

const-t commented Oct 18, 2023

Scope

Looks strange following condition in tfw_http_hm_control() if we take into account that tfw_apm_hm_srv_alive() must be called for alive server at least once to calculate valid crc32 in case when directive resp_crc32 is auto:

if (!tfw_srv_suspended(srv) ||
	    !tfw_apm_hm_srv_alive(resp->status, &resp->body, srv->apmref))

Discussion in PR

Need to find out is there a bug or not and develop functional test for this case.

@krizhanovsky krizhanovsky added question Questions and support tasks test labels Oct 18, 2023
@krizhanovsky krizhanovsky added this to the 0.9 - LA milestone Oct 18, 2023
@enuribekov-tempesta
Copy link
Contributor

It looks code itself is correct, but number of issues was found around this code:
typos, bugs, unused function arguments etc.

@enuribekov-tempesta
Copy link
Contributor

Created issue for bug found during testing HM.

#2128

@enuribekov-tempesta
Copy link
Contributor

Sometime could't receive correct answer from monitored server.
The reason was tempesta-tech/tempesta-test#625
Reworked test for using nginx and got correct answer.

@enuribekov-tempesta
Copy link
Contributor

tfw_http_hm_suspend() worked incorrectly, reworked.

@enuribekov-tempesta
Copy link
Contributor

In a function tfw_apm_hm_srv_alive() hm->codes bitmap is empty, so always return error during comparation with any real status code.

@enuribekov-tempesta
Copy link
Contributor

It looks like instead of saving server_failover_http configuration we got memory leak.
#2130

@krizhanovsky
Copy link
Contributor

fixed in #2151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions and support tasks test
Projects
None yet
Development

No branches or pull requests

3 participants