-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
keep_jobs integer intervals are too large #55295
Comments
Thanks for submitting this ticket as well as getting a PR together. Pinring @saltstack/team-core about this one so we can review the PR and address this. 😄 |
@squidpickles I'm wondering if there is not a more elegant way of accomplishing what you are trying to do. What is the motivation for running |
We've noticed a number of hosts lose salt connectivity, despite being reachable via SSH. This occasionally predicts localized network outages. Our systems team wrote a check for the monitoring system using a ping to check for responsive hosts. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Thank you for updating this issue. It is no longer marked as stale. |
@dwoz can you take a look at this one, please? |
Description of Issue
For a large installation (>3000 minions) running frequent operations, the job cache grows quite large. In our case, we don't need a job cache beyond about 5 minutes. It would be helpful to be able to specify
keep_jobs
as a fraction of an hour, to keep the cache small. (We keep ours in RAM to reduce disk IO.)Setup
1 master, 3000 minions
Steps to Reproduce Issue
Set
keep_jobs: 1
, runtest.ping
every 60 seconds, job cache grows to 10 GB over 24 hours.Versions Report
The text was updated successfully, but these errors were encountered: