Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.4.13, 7.2.9
-
6.04
-
46
-
Severity 2 - Major
-
61
-
Description
Summary
JIRA Datacenter is unresponsive during deletion custom fields context.
ManageConfigurationScheme flushes cache data: fields context, config scheme issue type and custom fields across all cluster nodes for each modification. When we reload cache we load ALL RECORDS from fieldconfigschemeissuetype table. Then this data need to be loaded back into cache at each node, which is causing performance degradation.
Most data structure operation are cluster wide, so executing them from the dark node unfortunatly will have same effect and will not help.
Environment
- JIRA DC
- High load
- Large number of
- Custom-Fields: 2000+
- Number of elements in fieldconfigschemeissuetype: 10000+
Steps to Reproduce
- Configure Custom-Field, for example by changing/deleting context.
Expected Results
JIRA cluster peformance doesn't degrade significantly,
Actual Results
JIRA Datacenter is unresponsive.
Notes
- Problem can be partially mitigated by improving cache loading for fieldLayoutCache, see workaround -
JRASERVER-66013
Workaround
Execute operation during low activity.
Attachments
Issue Links
- is caused by
-
-
- Closed
-
-
JRASERVER-68168 Make FieldLayoutCache population more efficient in Jira
- Gathering Interest
- is related to
-
-
- Closed
-
-
-
- Gathering Impact
-
-
- Gathering Interest
- relates to
-
-
- Closed
-
- is mentioned by
-
CFC-5 Loading...
- Mentioned in
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- was cloned as
-