[#JRA-15190] Deterioration of performance due to CachingVersionStore lock

JIRA

Deterioration of performance due to CachingVersionStore lock

Created: 02/Jul/08 09:14 PM Updated: 28/Aug/08 11:44 PM

Component/s:

Performance, Project Management, Refactoring

Affects Version/s:

3.12.2

Fix Version/s:

3.13

Time Tracking:

Original Estimate:

1 week

Remaining Estimate:

0 minutes

Time Spent:

2 days, 6 hours

File Attachments:

VersionStorePatch.zip (14 kB)

Environment:

Customer environment: Weblogic 8.x and DB2

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-15494~~ Take too much time to create a version in the administration section

Participants:	Akshaya Kumar Naik, Anton Mazkovoi [Atlassian], Diego Alonso [Atlassian] and Mark Lassau [Atlassian]
Since last comment:	10 weeks, 4 days ago
Resolution Date:	24/Jul/08 11:22 PM
Labels:

Description

« Hide

Customer experiences very long delays while adding a version to a project, with the "Schedule:Before First Version" property. An analysis of the log file shows a lot of threads waiting on an object lock from class CachingVersionStore. Please investigate if it is possible to improve the locking mechanism. Thread dump attached in the support case.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Mark Lassau [Atlassian] added a comment - 17/Jul/08 02:10 AM

To make matters worse, when adding a version before, say, 20 other versions, you will end up with 20 updates, 1 insert and re-load the entire cache 21 times.

[ Permlink | « Hide ]

Akshaya Kumar Naik added a comment - 24/Jul/08 07:46 AM

Do you have an ETA on this? Jira is becoming unresponsive every now and then and we are rebooting our weblogic server multiple times every week to keep it running.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 24/Jul/08 11:19 PM

We are working on this at the moment.

We are trying to ship a fix in JIRA 3.13 which we hope to release in late August or early September.

Once we have a fix we will see if we can put up patches here.

Could you confirm the version of JIRA you are using?

Cheers,
Anton

[ Permlink | « Hide ]

Akshaya Kumar Naik added a comment - 25/Jul/08 01:22 AM

Thanks Anton, appreciate the quick response! We are using jira 3.12.2 and planning to upgrade to jira 3.12.3 soon. We will appreciate if we can get a patch for jira 3.12.3.

[ Permlink | « Hide ]

Mark Lassau [Atlassian] added a comment - 27/Jul/08 09:40 PM

Attached a patch for v3.12.3
Unzip the file "VersionStorePatch.zip", and copy this into your webapp folder (on standalone this is "atlassian-jira").

If you are using this patch, you may want to add the following to your log configuration file (log4j.properties):

log4j.category.com.atlassian.jira.project.version = DEBUG, console, filelog
log4j.additivity.com.atlassian.jira.project.version = false

[ Permlink | « Hide ]

Akshaya Kumar Naik added a comment - 29/Jul/08 05:23 AM

Hi Mark, Thank you very much for the patch, appreciate it!

[ Permlink | « Hide ]

Mark Lassau [Atlassian] added a comment - 31/Jul/08 01:11 AM

Glad to help - thats what we are here for

I would be interested in any feedback you have after installing the patch.

I would also recommend that you upgrade to v3.13 at your earliest convenience after it is released.
Running a patched version of software always has some risk, and is harder to support.
Please remember to mention that you have a patch installed if you happen to raise any support tickets.