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

Allow more than one keepalive connection per cache service worker #2671

Merged
merged 1 commit into from Jan 17, 2020

Conversation

kraih
Copy link
Member

@kraih kraih commented Jan 17, 2020

I made a small mistake when i copied the prefork parameters from the webui to the cache service API server. The webui has an Apache reverse proxy to handle HTTP keep-alive connections, but the cache service does not.

That means when a worker is under heavy load you can start seeing errors like [2020-01-17T11:29:56.0370 CET] [error] [pid:47664] Unable to setup job 3801895: Cache service not reachable: Inactivity timeout, because other workers were blocking access to the API server with their keep-alive connections.

Copy link
Contributor

@Martchus Martchus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I followed the discussion on the chat. So I guess it make sense (and hopefully we don't do anything blocking in that service).

@kraih
Copy link
Member Author

kraih commented Jan 17, 2020

@Martchus Fortunately everything the service does is very fast.

@kraih kraih merged commit ccebff1 into os-autoinst:master Jan 17, 2020
@kraih kraih deleted the cache_service_keepalive branch May 12, 2020 13:18
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

Successfully merging this pull request may close these issues.

None yet

3 participants