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

Scale up based on past OOM counts #7

Open
kitsuya0828 opened this issue Apr 14, 2024 · 0 comments
Open

Scale up based on past OOM counts #7

kitsuya0828 opened this issue Apr 14, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@kitsuya0828
Copy link
Collaborator

Expected Behavior

  • When memory usage spikes, only job restarts are performed to reduce costs
  • Add a feature that would also raise the memory limit on the specs if OOM occurs continuously
    • Counting the most recent OOM count for CronJob, etc. is possible

Actual Behavior

  • Always update the memory limit after one OOM occurs
    • There may be no need to permanently increase the memory limit for one time only when a spike in memory usage occurs

Steps to Reproduce the Problem

  1. As in Getting Started

Specifications

  • Version: v0.0.1
@kitsuya0828 kitsuya0828 added the enhancement New feature or request label Apr 14, 2024
@kitsuya0828 kitsuya0828 changed the title Scale down based on past OOM counts Scale up based on past OOM counts Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant