Skip to content

check module failing at high cpu #1

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

Open
gfrankliu opened this issue Jun 8, 2017 · 4 comments
Open

check module failing at high cpu #1

gfrankliu opened this issue Jun 8, 2017 · 4 comments

Comments

@gfrankliu
Copy link
Collaborator

Moving weibocom/nginx-upsync-module#157 here.

When cpu is high, other requests still work but slower. Will that affect the check timer? If I have check timeout to be 5s, when cpu is busy, will check thread not get a chance to validate the response within 5s maybe?

@xiaokai-wang
Copy link
Owner

The question is about upstream_check_module, not upsync_module.

Ok, when cpu is high to 100%, other requests can work normally? No independently thread or progress do check things, all checks is used timer, not attached to the fixed progress.

@gfrankliu
Copy link
Collaborator Author

Yes, when cpu is high, other requests still work but slower. Will that affect the check timer? If I have check timeout to be 5s, when cpu is busy, will check thread not get a chance to validate the response within 5s maybe?

@xiaokai-wang
Copy link
Owner

the progress first will handle the requests, then go on to timer. Though nginx can still work, I guess part requests are lost.

@gfrankliu
Copy link
Collaborator Author

When cpu is high, I am ok some request will lost, but the problem I saw is ALL request lost because health check marks ALL upstream servers as "down".

Are you saying if nginx is busy serving requests, it will not go to the timer until it is free? By the time when nginx gets to the timer, all those health checks already timeout. This may be the reason why all upstream servers are down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants