> Our current > Ruby versions are EOL'ed, so we're moving to MRI Ruby 2.4 on the agent > and (opt-in) jruby9k on the server.
So what's the current status on that opt-in? I'm running into a nasty bug with Jruby 1.7 [1] and while I read the configure guide [2] I'm still a bit unsure whether I should switch over to 9k (which would fix my encoding issue) or I should try to work around (which I mostly can ftm). So anyone running it? What are the main issues with it? When are you hit by the performance and memory leak issues that are mentioned in the jruby github report and linked in documention [3]. Reading SERVER-1586 [4] & SERVER-1122 [5] and seeing both closed and not any further relevant tickets in the backlog regarding 9k, I assume the work on Puppet's side is mostly done and it's all about the upstream jruby issues? Also I assume I need to re-install all my gems for puppetserver that I installed with jruby 1.7, right? The docs don't mention anything like that. best ~pete [1] https://github.com/jruby/jruby/issues/4767 [2] https://docs.puppet.com/puppetserver/5.0/configuration.html#configuring-the-jruby-version [3] https://github.com/jruby/jruby/issues/4112#issuecomment-242504130 and [4] https://tickets.puppetlabs.com/browse/SERVER-1586 [5] https://tickets.puppetlabs.com/browse/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/b4bc84dc-8b0a-3048-99bf-f621cdd6b457%40immerda.ch. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
