• 3
    • 22
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Issue Summary

      On every Jira restart, Insight indexing(freetext-reindex) is triggered (i.e., irrespective of nodes).

      Though we have options to "Persist Insight index to file" & increasing the "Tomcat shutdown time" which is not useful to not have auto re-index during restart.

      As a result - Insight will always re-index on restart.

      Jira administrator should have control to disable auto re-indexing of Insight.

      Steps to Reproduce

      1. Restart Jira.

      Expected Results

      1. Once the application is started, Insight should not re-index automatically.

      Actual Results

      1. Once the application is started, you'll see that the Insight re-indexing is started.

            [JSDSERVER-11974] Ability to control Insight full re-index on restart

            Iz added a comment -

            Thank you very much Gonzalo,

            In our case (v9.12.4), we have 45 million objects related to 3 million tickets. 45 million that are reindexed on each restart. It takes more than 4h30m reindexing. While reindexing is running, no values are displayed in asset customfields.

            This is not a suggestion. This is an important and determining bug.

            In addition to this issue, with a significant volume of connectedTickets, there are performance issues when accessing asset views.

            Iz added a comment - Thank you very much Gonzalo, In our case (v9.12.4), we have 45 million objects related to 3 million tickets. 45 million that are reindexed on each restart. It takes more than 4h30m reindexing. While reindexing is running, no values are displayed in asset customfields. This is not a suggestion. This is an important and determining bug. In addition to this issue, with a significant volume of connectedTickets, there are performance issues when accessing asset views.

            Good day,

            We have been able to investigate in deep this issue and here you have what we found:

            1. There is a DB table called "AO_8542F1_IFJ_OBJ_JIRAISSUE" that keeps track of all issues related which each Asset object.
            2. This table is indexed with Asset index.
            3. When you restart Jira with the options Persist Insight index to file and Restore Assets index from file (even if you have increased the shutdown time and the file is saved on time as support probably has suggested) if only one new ticket is created with an Assets customField, this will be reflected in the mentioned table.
            4. Due to that, there is a mismatch in the objects present in the DB and in the index, therefore, the index is discarded and recreated again.
            5. In our case, we had more than 7 million objects related with this connections (7 million that should be reindexed!!!).
            6. We have done this in our DEV, PRE and PRO environment:
              1. Shut down JIRA 
              2. Clear the DB table (you can delete all or all but some issue types - DO NOT DROP THE TABLE, ONLY THE ROWS).
              3. Start Jira

            I would not recommend anybody to modify tables directly from DB, neither Atlassian support, but in our case, the reindex time was reduced from 30-40 min to 1 min, so I can certainly point to this issue as the one causing the incredible slow Asset index time.

            Hope this information is useful for someone, take this into account when deleting the information:

            • Cross search in JQL is still posible: customfield_XXX in aqlFunction(XXXX) OK
            • Searches in AQL for the cases you have deleted will no longer be available: connectedTickets(XXXXX) KO
            • Related Jira issues at the right in Assets view will disappear KO

             
            Thank you and kind regards,
            Gonzalo.
             
            QUERY TO CLEAR THE DB BUT SOME ISSUE TYPES (change it based on your IDs):
            DELETE FROM "AO_8542F1_IFJ_OBJ_JIRAISSUE"
            USING "jiraissue"
            WHERE "AO_8542F1_IFJ_OBJ_JIRAISSUE"."JIRA_ISSUE_ID" = "jiraissue"."id" AND
            "jiraissue"."issuetype" IN ('10001','10100','14000','14100','14500','10200','11100','12500','13100','10004');

            Gonzalo Arteaga Ruiz added a comment - Good day, We have been able to investigate in deep this issue and here you have what we found: There is a DB table called " AO_8542F1_IFJ_OBJ_JIRAISSUE " that keeps track of all issues related which each Asset object. This table is indexed with Asset index. When you restart Jira with the options Persist Insight index to file and Restore Assets index from file (even if you have increased the shutdown time and the file is saved on time as support probably has suggested) if only one new ticket is created with an Assets customField, this will be reflected in the mentioned table. Due to that, there is a mismatch in the objects present in the DB and in the index, therefore, the index is discarded and recreated again. In our case, we had more than 7 million objects related with this connections (7 million that should be reindexed!!!). We have done this in our DEV, PRE and PRO environment: Shut down JIRA  Clear the DB table (you can delete all or all but some issue types - DO NOT DROP THE TABLE, ONLY THE ROWS ). Start Jira I would not recommend anybody to modify tables directly from DB, neither Atlassian support, but in our case, the reindex time was reduced from 30-40 min to 1 min, so I can certainly point to this issue as the one causing the incredible slow Asset index time. Hope this information is useful for someone, take this into account when deleting the information: Cross search in JQL is still posible: customfield_XXX in aqlFunction(XXXX) OK Searches in AQL for the cases you have deleted will no longer be available: connectedTickets(XXXXX) KO Related Jira issues at the right in Assets view will disappear KO   Thank you and kind regards, Gonzalo.   QUERY TO CLEAR THE DB BUT SOME ISSUE TYPES (change it based on your IDs): DELETE FROM "AO_8542F1_IFJ_OBJ_JIRAISSUE" USING "jiraissue" WHERE "AO_8542F1_IFJ_OBJ_JIRAISSUE"."JIRA_ISSUE_ID" = "jiraissue"."id" AND "jiraissue"."issuetype" IN ('10001','10100','14000','14100','14500','10200','11100','12500','13100','10004');

            agente added a comment -

            Issue still in:

            • Jira Service Management 5.4.10
            • Assets 10.4.10

             

            Regards,

            Juan Fran

            agente added a comment - Issue still in: Jira Service Management 5.4.10 Assets 10.4.10   Regards, Juan Fran

            Issue is still reproducible on Jira 9.4.6, JSM 5.4.6

            Oleksii Zvarych added a comment - Issue is still reproducible on Jira 9.4.6, JSM 5.4.6

            Babu R added a comment -

            Issue is still reproducible on Jira 9.4.2, JSM 5.4.2 and Asset 10.4.2

            Babu R added a comment - Issue is still reproducible on Jira 9.4.2, JSM 5.4.2 and Asset 10.4.2

            Babu R added a comment -

            Issue is still reproducible on Jira 9.4.0, JSM 5.4.0 and Asset 10.4.0

            Babu R added a comment - Issue is still reproducible on Jira 9.4.0, JSM 5.4.0 and Asset 10.4.0

            Babu R added a comment -

            We're able to reproduce the issue in below version. (i.e., still freetext-reindex is being triggered on every restart of Jira application)

            Jira Software v9.3.0
            Jira Service Management v5.3.0
            Insight/Assets version is v10.0.17

            Babu R added a comment - We're able to reproduce the issue in below version. ( i.e., still  freetext-reindex  is being triggered on every restart of Jira application) Jira Software v9.3.0 Jira Service Management v5.3.0 Insight/Assets version is v10.0.17

              Unassigned Unassigned
              580fc054682a Babu R
              Votes:
              28 Vote for this issue
              Watchers:
              29 Start watching this issue

                Created:
                Updated: