Our small company with about 15,000 issues is, out of the blue, experiencing seemingly random times where the application becomes unresponsive (not completely, but minute+ page loads that normally take a second) with high cpu usage and no indications that I am aware of to see how long it will take (today it was about 4pm). When this isn't happening, the service runs reliably and responsively enough.
I'm able to stop and restart JIRA to make it available for our people to use again but that isn't a good thing to have to do every couple days.
Any thoughts on where to begin isolating the cause for this? Google searches turn up conflicting, overly technically-deep advice.
JIRA version 7.13.0
Symptoms such as high CPU usage and no response usually are connected to memory usage by JVM, but please provide some more details on your JVM parameters (available in System->System Info section) and overall system configuration (operating system, memory, cpu, etc).
This is running on a m5a.large Amazon instance (2 vpu, 8GB RAM).
This is what I have from the System Info Section:
No idea what EazyBI is. Not using it.
We are using the following add-ons:
I've increase the max memory to your recommended setting of "2g".
JIRA started in about half the time. Seems like a deficiency in the product that it doesn't do this automatically or have a non-editing-buried-config-files way of doing this.
Anyway, I guess we'll see.
Thanks! ; )
One of the issues with this software is the sheer amount of logging it collects, which I guess isn't in itself bad except one won't know where to start.
Now, some research just now is pointing to /var/atlassian/application-data/jira/log/atlassian-jira.log as a primary log to use, however it's very difficult to read through (and seems to contain fairly low-level java debugging messages).
Any suggestions on something I can run on this headless server to help me parse through these files?
Hi @Nick Smith
What you can find as a non-developer or system admin, you can go to Jira services (System->Services) and check out backup service. In most cases it's executed twice a day, at 1AM and 1PM and it can cause some performance bottlenecks, but after you increased heap memory it shall be fine.
You can modify Cron expression to run backup only at night by entering following expression: 0 0 5 1/1 * ? *
It will start backup at 5AM each day.
It says "Each Monday at 1:00 am" which would rule it out as a cause for this issue.
Doing a quick little research indicates this it is discouraged for production systems...and since we grab routine snapshots of the whole instance and the database on a fairly granular basis, I have decided to remove this service.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event