-
Bug
-
Resolution: Fixed
-
Highest
-
7.7.0, 7.6.4, 7.7.1, 7.8.0, 7.6.5, 7.9.0
-
7.06
-
2
-
Severity 1 - Critical
-
3
-
Summary
After upgrade to Jira 7.6.4 customers with 10k+ users see major performance degradation. Jira is hitting propertyentry table up to 10x times more causing DB overload.
Problem is amplified in correlation with another issue - JRASERVER-65168.
Environment
- Jira 7.6.4/7.6.5 (please note that only these versions are affected from 7.6 branch) or other Affected versions
Expected Results
The number of requests to the propertyentry table is the same as before.
Actual Results
The number of requests to the propertyentry table increased 10 times.
Notes
Root cause
As part of a fix for JRASERVER-67041 users attributes cache was switched to short leaving one to eliminate the need for cluster cache replication. Some features like user picker or Jira service desk iterate many users' attributes entries and as a result DB load is increased significantly as user attributes cache is usually empty.
Workaround
Set system property to revert the changes (code will work as pre-7.6.4):
- add to JVM_SUPPORT_RECOMMENDED_ARGS:
-Djira.cache.CachingOfBizPropertyEntityStore.ApplicationUser.remote=true
- is caused by
-
JRASERVER-67041 Jira Data Center generates too many cache replication events for some caches due to wrong remote policy
- Closed
- is related to
-
JRASERVER-65168 Add Multi-Column Index to JIRA Tables
- Closed
- relates to
-
JRASERVER-64928 Slow performance due to high number of rows in the entity_property table
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...