Details
-
Suggestion
-
Status: Gathering Interest (View Workflow)
-
Resolution: Unresolved
-
None
-
55
-
Description
Problem Definition
Upgrading UPM triggers all apps/applications to restart because of the licensing API provided by UPM. This can cause Jira to return 404 and other errors while the UPM upgrade is in progress, effectively causing downtime.
Impact
Depending on the plugins in the instance, this can cause 404 and 500 errors on (at least) the following pages:
- Dashboard.jpsa
- JiraHome.jspa
- Viewing any issue
This effectively renders Jira unavailable for the time it takes to update the UPM, which can be 5-10 minutes.
Suggested Solution
As a Jira Server admin I want to update UPM, but I don't want all other apps/applications to depend on UPM.
Workaround
Unfortunately there is no workaround at this time. Instances that are affected by this should have the UPM updated in a scheduled maintenance window.
Attachments
Issue Links
- is related to
-
JRASERVER-72909 Universal Plugin Manager flushing jira.properties cache causing contention and performance problem
-
- In Progress
-
-
JRASERVER-69958 More information about the impact of upgrading an app
- Gathering Interest
-
JRASERVER-69961 Add possibility to do a rolling apps update (extend ZDU functionality)
- Gathering Interest
-
JRASERVER-69962 Eliminate apps downtime while performing app update in Jira Server
- Not Being Considered
-
BSP-538 Loading...
-
BSP-539 Loading...
- relates to
-
JRASERVER-64908 UPM actions may flush internal caches, leading to performance problems
-
- Closed
-
-
JSWSERVER-15815 Updating UPM temporarily disables Jira Software and required bundled plugins
-
- Closed
-
-
JRASERVER-72442 Customfield Cache Management is sensitive to Administrator's Locale
-
- Needs Triage
-