Scriptrunner causing CPU load to spike

duely March 28, 2018

One of our developers is testing a script from the ScriptRunner and we noticed that the CPU load has spiked. I've asked the developer to stop the script, but I noticed that the logs are outputting the same message every second. What does this message mean and is this related to our CPU load spiking?

 

$ /var/atlassian/application-data/jira/log

2018-03-28 20:18:46,728 http-nio-8080-exec-40 INFO user-name-here 1180x15788x10 x8d5mh 12.189.102.85,10.5.60.81 /rest/scriptrunner/latest/user/exec/ [c.o.scriptrunner.runner.ScriptRunnerImpl] Not a ticket of phase type, moving to the next parent

3 answers

1 accepted

0 votes
Answer accepted
Steven F Behnke
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 28, 2018

This is a custom script ran through the console. The developer likely did not stop the script, because they likely didn't even give themselves a way to stop the script. 

This is literally a worst-case scenario -- He wrote a script that is impacting your CPU, it's iterating over all issues, it's logging some custom log message 'Not a ticket of phase type, moving to the next parent', and there's no way to stop it

Either wait it out or restart Jira.

0 votes
duely March 28, 2018

Thanks everyone for the reply! I've restarted the Jira service and it looks to be operating normal.

Steven F Behnke
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 28, 2018

Excellent, that's good news. :) 

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 28, 2018

It's rare that ScriptRunner itself will do this, it's going to be the scripts it is running.

Some of the built-in scripts can spike sometimes, when there's unexpected data (e.g. 1,000 subtasks on an issue, or 30,000 comments).

There's no real way to tell you want it might be without knowing what the script is trying to do.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events