Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira not available

anshu02
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 8, 2019

Hi Everyone, 

Our Jira datacentre(6.2) instance was down yesterday, and after checking our DBA found locks in DB, these are the queries, 

UPDATE jiraissue SET pkey=:1 , issuenum=:2 , PROJECT=:3 , REPORTER=:4 , ASSIGNEE=:5 , CREATOR=:6 , issuetype=:7 , SUMMARY=:8 , DESCRIPTION=:9 , ENVIRONMENT=:10 , PRIORITY=:11 , RESOLUTION=:12 , issuestatus=:13 , CREATED=:14 , UPDATED=:15 , DUEDATE=:16 , RESOLUTIONDATE=:17 , VOTES=:18 , WATCHES=:19 , TIMEORIGINALESTIMATE=:20 , TIMEESTIMATE=:21 , TIMESPENT=:22 , WORKFLOW_ID=:23 , SECURITY=:24 , FIXFOR=:25 , COMPONENT=:26  WHERE ID=:27 

select O_S_PROPERTY_ENTRY.id, O_S_PROPERTY_ENTRY.propertytype from propertyentry O_S_PROPERTY_ENTRY where O_S_PROPERTY_ENTRY.entity_name = :1  and O_S_PROPERTY_ENTRY.entity_id = :2  and O_S_PROPERTY_ENTRY.property_key = :3  order by O_S_PROPERTY_ENTRY.id desc for update

Any idea what it is related to, i found some links which says it is related to Multi-column indexes in Jira tables. 

 https://jira.atlassian.com/browse/JRASERVER-65168?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

 

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 11, 2019

The suggestion ticket you linked of https://jira.atlassian.com/browse/JRASERVER-65168 certainly does relate to a performance improvement in Jira that has been included in the Jira 8.0.0 release.   That performance issue has found that tables in the Jira database that have multiple indexes are often left to the database to decide which index to use when searching for data that relates to that table.   In some cases that can cause several performance problems with Jira.

In turn the solution that has been used here is the creation of a multi-column index on the database.  

With the information we have so far about your system, I can't say for sure this is the problem you have seen.  It is possible it relates to that, but without knowing more about your environment, your logs, etc, it probably isn't possible for us to clearly determine if this is the case.  

If you see this happen again, it might be better to create a support case with Atlassian on https://support.atlassian.com

Suggest an answer

Log in or Sign up to answer