I found that reducing the number of versions of CVs helped - clearing out old versions that weren't used any more.
cheers L. ------ The most dangerous phrase in the language is, "We've always done it this way." - Grace Hopper On 10 February 2017 at 09:56, 'Jason B. Nance' via Foreman users < [email protected]> wrote: > In the past week or two I've noticed that when I go to publish a new > version of a CV or promote it the "Planning" phase is taking 30-60 minutes > or even more. Mongodb is hogging all of the resources. This is on Katello > 3.2.2, Foreman 1.13.4, CentOS 7.3+. > > Anyone else experiencing this or found a solution? > > j > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
