Hi, I was playing (one more time) with a 2.6.0rc3 puppetmaster on JRuby (which by the way is really faster than MRI for manifests compilation).
So I decided to increase the concurrency and started seeing some threading issues (mainly when multiple clients hits a fresh master (ie no AST yet) at the same time). I think most of the issues can't be found using MRI, but using JRuby native threads, it becomes easier to trigger those. I'll file some bugs for some of the issue I've found, but just so that you know what I'm talking about, I found those: * the "import" function is not threadsafe (compared to module autoloading). This one can be triggered with MRI. * rest authconfig default ACL insertion is not threadsafe (my fault) * cached attributes are not threadsafe at all. I think most of the singleton we have are not threadsafe (like rest authconfig). It might be good to review all our code following this pattern. I've also found some threading issues in rack, but that might be an issue coming from jetty-rackup or rackup itself. I plan to do a more extended testing session in the next following days, so stay tuned for some new bugs and patches :) -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
