nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira high disk usage with no user activity

Joe Prevo

We are using Jira software 7.6.0 on a Ubuntu 16.4 server. Jira is generating a large amount of disk I/O (averaging 300-500 KB per second). We only have 3 users that typically use Jira twice a day. There is absolutely no reason for this kind of I/O for an idle system. We have had to move the server's disk off of an SSD to a regular hard drive due to the excessive SQL database I/O.

In investigating it, it appears to be a huge number of inserts and deletes into the rundetails table. It appears that the culprit might be scheduled jobs for com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateJob. We have more than a hundred of those jobs and they are scheduled to run every minute. To add insult to injury, if the jobs are really tied to Bamboo, we don't even use Bamboo and have no plan to do so.

Is there any way to stop these jobs or change the interval? We typically only use the system once in the morning and once in the evening. We don't need 100+ jobs running every minute!

Thanks

FYI, while no one was using Jira, I upgraded Jira software to 7.6.1 and now we have 2 more of the jobs under com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateJob than we had before the upgrade that now run every minute. Do we possible have a problem that jobs are getting created that never go away and they are just building up? If so, is there any way to safely delete the jobs?

Accepted answers

All comments

Nic Brough -Adaptavist-

I think you need to track down where all this Bamboo stuff came from.

A new, empty Jira I created this week does not do this. When I imported a shedload of data in it by importing, it does not do this. It is now linked to a Bamboo instance with a small handful of new plans created this week, and it does not do this.

You're absolutely right in saying "There is absolutely no reason for this ..." and the ... meaning not just disk I/O, but the database access and jobs.

I think the question needs to be why your system has all of this stuff - what is adding it? What are they doing? How did you get it all added?

Joe Prevo

I agree. We've been using Jira for years now and have just kept updating through the versions; nothing special. We use very little Jira functionality and there are only 3 users. We only do basic issue tracking, no integration with anything else, no add-ons, etc.

Joe Prevo

BTW, we haven't done anything with Bamboo. Never touched it. It got added to Jira as non-removable modules a while back. We'd like to get rid of it but can't. It's a shame that Atlassian keeps adding stuff that you can't get rid of to the base product. It really shouldn't be an Add-on if I can't subtract it off!

Nic Brough -Adaptavist-

Thing is, if you've not configured anything to do with it, Jira won't have any way to trigger doing stuff.

I suspect one of your users has done something you don't know about.

Start with a look at

Application links
Bamboo configuration

Make sure there's nothing there for either of them!

Matt Doar_tzgiej

My suspicion is that the many jobs could be due to the time on some server not being set as expected. Is ntp working? What timezones are involved?

Joe Prevo

Just Eastern Time; Jira calls it New York of course. NTP is working and all our systems (including the server Jira is running on) synchronize to our firewall's NTP service. Checked and they're all within a second of each other. Also, time issues would be very noticeable to us because a product we develop uses SAML authentication that is configured to fail with more than a 5 second drift between system clocks to meet one of our customer's requirements.

The fishy thing to me is that the Bamboo job count goes up by one with each restart of Jira. I never see the count increase if Jira runs without interruption. And the count never decreases unless I delete the jobs out of Clustered Job table.

Nic Brough -Adaptavist-

This is well worth checking.

It's something that bites me a lot when I'm doing SSL stuff, but I forget it might cause issues in other areas!

Shannon S

Hi Joe,

I've created you a ticket in our support system so your Support Team can have a look at your support zip directly.

You should have an email now about that ticket.

Could you please reply to that ticket with a copy of your Support Zip so we can have a look?

Thank you!

Regards,

Shannon

Matt Doar_tzgiej

Is this issue something filed for this question:

https://jira.atlassian.com/browse/JRASERVER-66593

Shannon S

Hi Matt!

That bug was raised by the support engineer who looked at the case I made for Joe.

Thank you for checking in!

Regards,

Shannon

Beheerder

Just chiming in. We are seeing the same problem on a small and quiet Jira Server (7.8.0) on Windows with Microsoft SQL Server, never had any Bamboo integration.

I just deleted 126 rows from table clusteredjob that had key "com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateJob". This finally stopped the large amounts I/O and huge transaction log backups (500 Mb per day, while the full database backup is only 82 Mb) we were seeing on the server.

The Jira bootstrap log features a line:

[c.a.j.p.e.bamboo.service.PlanStatusUpdateServiceImpl] PlanStatusUpdateJob scheduled to run every 60 seconds

Which seems to have added a new instance on every reboot of Jira, as described in the ticket linked to by Matt Doar.

If I could provide information that would help debugging the issue please let me know. For the moment the mentioned workaround of deleting those rows from the clusteredjob table is satisfactory.

Shannon S

Hi Maarten!

Please feel free to supply any details you have about the issue on the bug ticket. If we need anything further on there our development team will follow up with you!

JRASERVER-66593

Regards,
Shannon

Beheerder

Thanks Shannon, I have now. (Silly me, didn't realize I was allowed to comment on that ticket -- I just assumed it was read-only for me, and did not try.)

Shannon S

No worries, Maarten! Thank you for your feedback.

Shannon

Sue Bridges_o1cif3

Oh wow, I think this may be my issue that I'm having with heap errors etc. Like Joe a quiet system, so shouldn't get all of the log file errors I do when I analyse. I'm currently on 8.1 nothing to do with Bamboo, so sounds like 8.2.2 is the way to go. Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software