-
Bug
-
Resolution: Fixed
-
High
-
6.4.14, 7.2.12, 7.6.3
-
6.04
-
4
-
Severity 1 - Critical
-
91
-
Summary
During plugin (add-on) installs/updates/delete/disable action UPM will flush the large number of caches (see JRASERVER-64908).
For Jira datacenter this cache flush will be propagated to other nodes, thus affecting them. Also cache flush is triggered during node startup as UPM needs to register and load modules from plugins.
Environment
- Jira datacenter
Steps to Reproduce
- Upgrade plugin (or start node)
- Check performance
Expected Results
- Starting new node will not have significant impact for cluster
- Plugin action will not cause cache flush to be propagated to other nodes, only plugin events.
- Plugin action will have performance impact due to
JRASERVER-64908and nature of action, but it will be isolated
- Plugin action will have performance impact due to
Actual Results
- Starting new node has significant impact for cluster
- Plugin action causes cache flush to be propagated to other nodes, making cluster wide replication storm and putting extra load to DB.
Notes
None
Workaround
- Please plan any plugin actions updates/delete/disable (UPM actions) during low peak hours or maintenance windows.
- Please plan node start-up during low peak hours or maintenance windows (start one node at a time).
- is caused by
-
JRASERVER-64908 UPM actions may flush internal caches, leading to performance problems
- Closed
- relates to
-
JRASERVER-67703 JIRA Datacenter start generates large network traffic result in higher response time
- Gathering Impact
(2 mentioned in)