On Tue, 2017-10-10 at 10:50 -0400, Andrew Kofink wrote: > Me as well. It's quite difficult to work this way.
Yeah, I know :( Openshift aren't saying much other than that this is mainly due to the number of people that decided to upgrade to Silver Tier to avoid the sunset of v2. That's putting a lot of load on the v2 cluster, which obviously is hitting us. As Ewoud said, we've made a change today in how we process the underlying cron jobs that should reduce the amount of IO we were doing - if there's any kind of quota-ing going on, that should help. We're seeing that bring the time taken to run the cron down to about 10mins (starting at the top of the hour). That should improve things during that period. Sadly I did make a mistake during a manual part of the changes that impacted the DB, but that should be resolved now. Base load now seems to be down to around 7-9 which is better but still too high. Sadly the v3 resources are unlikely to be available before November, which is a limiter. If things are not better in the next day or two, then on Thu or Fri I may migrate it to our Scaleway account anyway, as we have capacity there, although I'd rather not migrate twice... Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
