Yes, I'm experiencing the exact same problem when hitting the destroy button. Mysql and ruby1.8 are eating all resources.
In my test env I had the agent runinterval set to 600 seconds to get lots of reports and stress the server a little. When I tried to take the node out of service by hitting 'DESTROY' it took ages and I eventually killed the process myself. I keep a close eye on the bug. -- Kind regards Martin Willemsma 2011/3/24 Randall Hansen <rand...@puppetlabs.com> > On Mar 24, 2011, at 9:06 AM, Stefan Goethals wrote: > > > Dashboard removes the reports for nodes one by one... > > This can take a long time with many reports. > > If this is true (and I have no reason to doubt it), it's Very Bad. I've > filed it as a bug: > > http://projects.puppetlabs.com/issues/6828 > > If this affects you, please watch the bug. > > r > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
