[SERVER-2253] jruby-settings profiling-mode option only enables profiling on the service startup. Created: 2018/07/17  Updated: 2018/07/23

Status: Accepted
Project: Puppet Server
Component/s: DOCS
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Normal
Reporter: Sam Woods Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to DOCUMENT-889 Update Puppet Server docs for jruby-s... Closed
Template:
Epic Link: Metrics improvements
Team: Server
QA Risk Assessment: Needs Assessment

 Description   

It turns out that the jruby profiling does not enable profiling any jruby in spawned threads, making that option not so useful. We should determine if there is a way to get it working for profiling all puppetserver jruby code.



 Comments   
Comment by Garrett Guillotte [ 2018/07/23 ]

DOCUMENT-889 requests changes to the Server docs to better align them with the current behavior. If this ticket changes the setting's behavior, DOCUMENT-889 might not be necessary.

Please coordinate changes made in this ticket with the Server docs lead so we can avoid redundant or conflicting changes.

Comment by Sam Woods [ 2018/07/23 ]

When I mentioned this to the server team they asked me to create this ticket, but that this would not happen soon, which is why I also created the docs ticket.

Comment by Garrett Guillotte [ 2018/07/23 ]

Yeah, I'm just being as explicit as possible since DOCUMENT and SERVER tickets don't have a lot of visibility across each other even when linked, and Server docs will probably get a new docs lead soon who won't already know the context.

Generated at Wed Nov 13 13:01:55 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.