Memory issues when searching through puppet classes

Support
1

Since upgrading to 1.8.1 on 2 separate servers, we've found that the
function of searching through puppet classes is pretty much broken. I've
run multiple tests now and it seems whenever we attempt to search through
puppet classes, the process takes upwards of 10 minutes to return results
and adds an additional 4GB-6GB of RAM to the foreman process, causing the
system to quickly run out of memory. Has anyone else been experiencing
issues with searching puppet classes since the 1.8.1 update?

Thanks.

2

>
> Since upgrading to 1.8.1 on 2 separate servers, we've found that the
function of searching through puppet classes is pretty much broken. I've
run multiple tests now and it seems whenever we attempt to search through
puppet classes, the process takes upwards of 10 minutes to return results
and adds an additional 4GB-6GB of RAM to the foreman process, causing the
system to quickly run out of memory. Has anyone else been experiencing
issues with searching puppet classes since the 1.8.1 update?
>

Can you provide some more details, such as logs, and any other relevant
information?

There was another thread on memory usage on 1.8.1 vs 1.8.0 but both without
sufficient information to trouble shot.

Thanks,
Ohad
> Thanks.
>
> –
> 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 foreman-users+unsubscribe@googlegroups.com.

··· On May 30, 2015 01:53, "Jack Watroba" wrote: > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.
3

We upgraded straight from 1.7.x to 1.8.1 so I'm not sure exactly when this
happened. The interesting thing is that it seems to correlate with
searching for a class that has a lot of parameters. If I search for a class
that has 50+ params, the search takes 10-15 minutes and adds an additional
4-8GB of RAM to the foreman process. If I search for a class that has no
parameters, it comes up relatively quickly. I've set the logs to debug and
replicated the issue over and over again yet I'm not seeing anything in the
logs indicating that there's an actual problem.

After starting foreman fresh, a passenger-status shows for the foreman
process:

/usr/share/foreman#default:
App root: /usr/share/foreman
Requests in queue: 0

    • PID: 14438 Sessions: 0 Processed: 1 Uptime: 9s*
  • CPU: 85% Memory : 169M Last used: 9s ago - Fresh start,
    everything looks good*
  • PID: 14446 Sessions: 0 Processed: 1 Uptime: 9s
    CPU: 60% Memory : 116M Last used: 9s ago
  • PID: 14454 Sessions: 0 Processed: 1 Uptime: 9s
    CPU: 78% Memory : 160M Last used: 9s ago

Once I tried searching for a puppet class with a lot of params:

/usr/share/foreman#default:
App root: /usr/share/foreman
Requests in queue: 0

    • PID: 14438 Sessions: 1 Processed: 7 Uptime: 6m 24s*
  • CPU: 89% Memory : 5163M Last used: 5m 46s ago - After letting
    a search for puppet class with 50+ params run for 5+ minutes (this
    continues, some classes will never show up and we just have to restart the
    server)*
  • PID: 14446 Sessions: 0 Processed: 49 Uptime: 6m 24s
    CPU: 6% Memory : 185M Last used: 3s ago
  • PID: 14454 Sessions: 0 Processed: 6 Uptime: 6m 24s
    CPU: 2% Memory : 178M Last used: 5m 59s ago
··· On Saturday, May 30, 2015 at 11:09:44 AM UTC-7, ohad wrote: > > > On May 30, 2015 01:53, "Jack Watroba" > wrote: > > > > Since upgrading to 1.8.1 on 2 separate servers, we've found that the > function of searching through puppet classes is pretty much broken. I've > run multiple tests now and it seems whenever we attempt to search through > puppet classes, the process takes upwards of 10 minutes to return results > and adds an additional 4GB-6GB of RAM to the foreman process, causing the > system to quickly run out of memory. Has anyone else been experiencing > issues with searching puppet classes since the 1.8.1 update? > > > > Can you provide some more details, such as logs, and any other relevant > information? > > There was another thread on memory usage on 1.8.1 vs 1.8.0 but both > without sufficient information to trouble shot. > > Thanks, > Ohad > > Thanks. > > > > -- > > 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 foreman-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com > . > > Visit this group at http://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. >