-
Notifications
You must be signed in to change notification settings - Fork 17
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
CronJob's every minute - ask teams to reduce these and possibly put them into a persistent pod. #291
Comments
Possibly something that can be added to Cailey's awesome documentation and communication push? |
@caggles could we add something to your docs about not running cronjobs too frequently? |
@caggles could we add something to your docs about not running cronjobs too frequently? @tmorik can you check if there are still active cronjobs that run too frequently on the platform? $ oc get cronjob --all-namespaces | grep -E '\* \* \* \* \*|\*/1 \* \* \* \*|NAMESPACE' | grep -v True | awk '{print $1"/"$2}' |
@sbarre-esit , Command output is like this:
|
I'm working on the docs right now, and I'm hoping to provide some guidance on what can/should be done when a job runs very often. First solution is "don't run the job so often" but I'm not sure where to find docs on how to put your cronjobs into a persistent pod - can anybody point me towards some if you're already aware of them? If not, I'll poke around some more on my own. |
https://hub.docker.com/_/jobber looks cool? |
An initial version of the doc is here: #548 I'll open another ticket to further investigate Jobber and maybe provide more guidance on using it later, but hopefully this is a good starting place for the document. |
https://trello.com/c/Qz9BuCh0/94-cronjobs-every-minute-ask-teams-to-reduce-these-and-possibly-put-them-into-a-persistent-pod
Push Cron education out to community regarding best practices for Cron scheduling
The text was updated successfully, but these errors were encountered: