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

Pod Idling - Don't idle mysql pods and only idle projects that didn't receive traffic for more than 4 hours #465

Closed
dasrecht opened this issue Jun 15, 2018 · 2 comments
Assignees

Comments

@dasrecht
Copy link
Contributor

dasrecht commented Jun 15, 2018

Currently we idle projects pretty fast after not receiving traffic.

We discussed that we should not idle the mysql pods as they take the most time to start back up again.

Also the idling might be happening to fast so we can idle projects after 4 hours after the last traffic occured.

To control the idling further (i.e. not just running it with --all) we could put a label in place on the services allow-idler which would be overrideable via a label.

This way we could use allow-idler: yes for service that may be idled and allow-idler:no for services that should not be idled automatically.

@Schnitzel
Copy link
Contributor

what is the use case for allowing the client to enable or disable auto idling specifically for single services? we will have global disabled services (like mysql) and project wide idling disabled, not sure if a specific service based one is really needed. Let's implement the MVP and implement in here:

  • not idling of database pods
  • idle only after 4 hours of non traffic.

@rtprio
Copy link
Contributor

rtprio commented Jul 17, 2018

this was closed in #473.

@rtprio rtprio closed this as completed Jul 17, 2018
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

3 participants