Fixing reindex issues using Indexing Queue Viewer

Use the Indexing Queue Viewer to check and look for reindex related issues.

What’s on this page:

• How to see when some indexing tasks has stuck?
• How to make sure only the dedicated node is reindexing?
• How to see the progress of an integration index?
• Why my repository hasn’t been removed yet?
• How to find a nested repository in ERROR state?
• More articles about troubleshooting, workarounds and solutions

How to see when some indexing tasks has stuck?

Sometimes the indexing process takes longer for some tasks. To see which tasks are in this state, start from the Manage integrations page and check the integration with the SCANNING or INDEXING status.

1. Go to Actions ➜ Show integration repositories. You may see some QUEUED or FETCHING status in the list and is somewhat taking a bit longer to process.

2. Open Jira System administration then click Logging and profiling on the left sidebar.

3. Under the Default loggers section, click Configure….

4. Set the Package name to com.bigbrassband.jira.git.services.indexer.

5. Set Logging Level to DEBUG.

   Setting the Logging to DEBUG level for the above package name will intruct Jira to do verbose logging on the plugin. Make sure to turn this setting off once it is confirmed that indexing is working on the said tasks. For example, the reindex is in progress if you see logs constantly adding to your atlassian-jira.log below:

   Branch: {}
   Last index revision: {}
   Adding document for repository = {}; branch = {}; revision = {}.

   style=’margin-bottom:0px’>

6. Click Add to proceed.

Take a look at Atlassian logs in dynamic. The better way is to use “Last Log for Jira” plugin (Last Log for Jira | Atlassian Marketplace). If the Git Integration for Jira app is doing something, then your logs are being flooded by a lot of messages like:

”2023-02-17 16:58:26,436+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 INFO      [c.b.j.g.s.indexer.revisions.RevisionsIndexManagerImpl] Latest indexed revision is: null
2023-02-17 16:58:26,436+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 INFO      [c.b.j.g.s.indexer.revisions.RevisionsIndexManagerImpl] Updating to: dac6a2304402a62f6410e666fa1510d129b1af93
2023-02-17 16:58:26,443+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.RevisionsIndexManagerImpl] Adding document for repository = 4; branch = master; revision = commit dac6a2304402a62f6410e666fa1510d129b1af93 1627632962 -----sp
2023-02-17 16:58:26,443+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.CommitIssueCollector] Processing commit dac6a2304402a62f6410e666fa1510d129b1af93, branch master, repo: TestGitPluginRepo
2023-02-17 16:58:26,443+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.CommitIssueCollector] Init Date: 2023-02-17 16:58:22
2023-02-17 16:58:26,444+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.CommitIssueCollector] Processing commit 3478d5dc85e5e45ddeac49ac11744b79a5fd035f, branch master, repo: TestGitPluginRepo
2023-02-17 16:58:26,444+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.CommitIssueCollector] Init Date: 2023-02-17 16:58:22
2023-02-17 16:58:26,445+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.CommitIssueCollector] Processing commit 8f6591d81b3c2d2d6e3ca5e077c897f2f7d33b98, branch master, repo: TestGitPluginRepo
2023-02-17 16:58:26,445+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.CommitIssueCollector] Init Date: 2023-02-17 16:58:22
2023-02-17 16:58:26,446+0600 bigbrassband-gitplugin-RevisionIndexerImpl:thread - 1 DEBUG      [c.b.j.g.s.indexer.revisions.RevisionsIndexManagerImpl] Adding document for repository = 4; branch = master; revision = commit cfc0cedf48b59980169daa8eccf0f6bc340447cc 1544338819 -----sp”

Remember to turn off DEBUG logging after obtaining the information that you need.

How to make sure only the dedicated node is reindexing?

1. Switch to the Indexing Queue Viewer.

2. Filter the tasks using Status: Indexing to see only the integration being indexed in the current node.

3. Use the Indexing queue Refresh icon (bottom-left of the list) to reload the list while tasks in the queue is still being processed.

4. Filter by different nodes to ensure that only the specific dedicated node(s) is indexing repositories. Dedicated node(s) can be setup via General settings ➜ Indexing: Allow all nodes to perform the repository indexing option.

How to see the progress of an integration index?

When an integration has pending indexing tasks, it becomes inconvenient to monitor its progress in the Manage integrations page using  Actions ➜ Show integration repositories.

If you have an integration in INDEXING progress, then we recommend to use Indexing Queue Viewer instead:

1. Switch to the Indexing Queue Viewer page then click the Refresh icon at the bottom-left portion of the task list.

2. Use the Status: Indexing filter to see only the integration being indexed in the current node.

3. Click to view the details for the indexing task that has the INDEXING status then copy the Parent ID value. The Parent ID for processed tasks are displayed on the filtered list. Since your integration is in INDEXING progress then the parent ID is the id you are interested in.

4. Use this value into the Search bar on the filters panel then press Enter to do a filter search. The index queue will show results based on the set filters and search criteria.

5. Click the Refresh icon to reload the task list during the indexing process.

Here are some suggestions for Status filter and search combination to control the displayed results:

• Set Status to Queued and enter the value of the Parent ID into the Search bar to see the rest of the indexing tasks to be processed relating to the reindex of the integration.

• Set Status to Indexing and enter the value of the Parent ID into the Search bar to see reindex tasks in progress relating to the reindex of the integration.

• Set Status to All and enter the value of the Parent ID into the Search bar to see the full scope of tasks relating to the reindex of the integration.

Why my repository hasn’t been removed yet?

You have removed a repository or integration and can still see it among repositories on Manage integrations page in DISABLED status for long time. This issue happens because the deletion task in still queued for processing. For instance, this could happen if General Settings ➜ Scheduled jobs ➜ Repository reindexing interval is lower than Indexing Queue Viewer ➜ Last run duration for scheduled indexing.

To resolve this issue:

1. Go to the Indexing Queue Viewer.

2. You should see a queue task with Remove repository state in the last page. This is because deletion tasks have one of the lowest priorities in the indexing queue.

3. Move this item to the top of the list via … Actions ➜ Move to top.

   a. Do a couple of indexing list page refreshes (using the Refresh icon) and see if the integration of repository is successfully removed.

   b. In addition, the proper way is to set the value of Repository reindexing interval to greater than the Last run duration of the task in question for scheduled indexing. Otherwise, this issue may appear again.

How to find a nested repository in ERROR state?

If you’re suspecting a indexing issue from a certain repository in an integration:

1. Switch to Indexing Queue Viewer and set the filter to Status: Error. This will narrow down the list for queued index items with the ERROR status.

2. View the logs of the error via ⋯ Actions ➜ View log. You may send the logs with errors or issues to us at GIJ Support for analysis.

More articles about troubleshooting, workarounds and solutions

Why I am getting the error, “git-upload-pack not permitted”?

Avoid OutOfMemory exceptions by configuring or memory allocation with Jira to accommodate large repositories

Cannot auto-deploy some tracked repositories: Specified origin is incorrect or not supported

Connection Reset when Accessing the Database

“Dangerous use of multiple connections” error on local database

Duplicate entry 0 for key PRIMARY exceptions in log

Error while reindexing – Java heap space / Object too large, rejecting the pack

Error creating git branches and also using NFS

Fix performance issues for nested cloned repositories with enabled Git Service Permissions mode

Fixing reindex issues using Indexing Queue Viewer (this page)

Gitolite integration: Why the Git integration app not see the master branch?

Health Check: Database Collation

Indexing error – Too many open files

Installation fails when installing manually

Jira index error: IndexNotFoundException: no segments* file found

Malformed input or input contains unmappable characters

Personal access token failing Azure DevOps integration with Not Authorized error

Problems with shared home on Azure Storage

Pull request index error: org.json.JSONException

Repositories missing from Azure DevOps integration

“Service proxy has been destroyed” exceptions in log

SQLException ‘Incorrect string value’ in merge requests

SSH key file format is invalid

TFS – Not authorized exception when Jira works thru proxy

Unexpected exception parsing XML document from URL error in log

Why don’t I see the Create Branch or Pull Request features?

Your token has not been granted the required scopes

When a GIJ license expires, it shows up as a session error to the user

edDSA provider not supported WARN in logs