On 08/31/2017 01:21 AM, Peter Meier wrote: >> 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?
So to report back after running it for >2 weeks: 0 problems so far and I don't really feel a difference to 1.7 AND JRuby devs really urge you to move to 9k, 1.7 is a dead end: https://github.com/jruby/jruby/issues/4767#issuecomment-327939620 So when will we officially ove to 9k? > 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. I did do that, without testing whether it actually works or not. best ~pete -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/9e1ccae9-788d-b010-8fe1-4cfefc8c27ac%40immerda.ch. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
