Indexing is a very large part of Git Integration for Jira app. This indexing feature displays various task entries, allowing you to easily view upcoming and ongoing tasks such as repository indexing and garbage collection.
The Indexing queue viewer displays detailed information such as:
- when was the indexing started
- when was the indexing finished
- how much time it took the indexing to complete
- ID of the task
- on which node the indexing was processed DATA CENTER
Offering ease of use and scope of features, the Indexing queue viewer:
provides users greater visibility into what’s happening with your repositories and system resources.
shows detailed information about the tasks – which node it was processed on, start time, finish time, processing time, task id, and more (mentioned above).
allows users to see which tasks are in the queue, find specific tasks by history, and filter tasks by specific parameters.
This feature can be accessed via the Jira dashboard menu Git ➜ Indexing queue.
Indexing queue dashboard
The dashboard displays the current number of processing tasks and tasks in the queue.
Click Clear queue to free up the current queue of all tasks with QUEUED status.
To the right of the dashboard is the Settings view panel. which shows information related to the general settings for scheduled indexing, garbage collection, etc.
Click Edit to go directly to the General settings page.
Filters and search
Just below the dashboard are controls for view filters. This section allow users to control which information is displayed on the screen.
- filter by status
- filter by trigger
- filter by type of operation
- filter by node
- filter by repository ID
- filter by task ID
- filter by parent task ID
- filter by name – case-sensitive:
- For ‘repository: Name’ — this is a name comprising a group and a repository name.
- For ‘integration: Name‘ — this is the name of the connected integration.
Filter the task list by clicking on the Status dropdown and selecting a category:
All – Displays the data for every Status category.
Queued — Displays tasks having QUEUED status. This indicates that the indexing tasks are still waiting in line to be processed or are still unfinished.
Indexing — Displays tasks having INDEXING status. This indicates that the indexing task is already running.
Indexed — Displays tasks having INDEXED status. This indicates that the indexing task has finished.
Error — Displays tasks having ERROR status. This indicates that the indexing task has encountered an error. Go to … Actions ➜ View log to see the error(s).
Filters the task list by clicking on the Trigger dropdown and selecting a category:
All – Displays the data for every Trigger category.
Manual — Displays tasks that was triggered manually. This includes user-triggered events such as:
reindex repositories/integrations/reindex all
reset all/reset repository
reindex triggered by bulk import
reindex triggered by Reindex REST API
reindex triggered by an update of repository
Webhook — Displays tasks triggered by webhook. Indexing triggered by webhooks fall on this category. For related information, see Webhook indexing explainer.
Scheduled — Displays tasks triggered by scheduled jobs. For more information, see Scheduler jobs.
App activity — Displays reindex tasks triggered by:
a branch creation/deletion
a manipulation with pull request
a change of commit issue association
a repository update, e.g. by a change of main branch
Initial indexing — Displays tasks triggered by initial indexing. Initial indexing is performed by the Git Integration for Jira app on the first successful connection of the git service integration.
Filter: Type of operation
Filters the view by clicking on the Type of operation dropdown and selecting a category:
All –- Displays the data for every Type of operation category.
Reindex –- Displays tasks related to indexing.
Garbage Collection -– Displays tasks related to Garbage Collection.
Remove repository –- Displays tasks related to removal of a repository.
Filters the view by clicking on the Node dropdown and selecting a category:
All –- Displays the data for every Node in the cluster.
Node[1…] – Node[n] –- Displays tasks and data only for the specified node in the cluster.
Using search to filter specific items to view
To the right of the view filter options, users can use the search bar to query for specific tasks and the indexing list view will be updated accordingly. Note that filtering by name is case-sensitive.
Sorting allows users to arrange tasks by categories such as status, trigger, and type of operation.
The default sort order applies the following rule:
INDEXING – first
QUEUED tasks (see details below):
a. raised to the top manually
b. reindex triggered manually:
* !(/wp-content/uploads/actions-icon.png) Actions ➜ Reindex repositories/integrations or Reindex all * !(/wp-content/uploads/actions-icon.png) Actions ➜ Reset all/Reset repository * via Bulk Import * via Reindex REST API * via an update from changes in the repository
c. triggered by webhooks
d. triggered by scheduled job
e. Actions ➜ Remove repository/integration
f. Garbage Collection tasks
FINISHED – last
- The first few rows are tasks being currently processed and sorted by Start time in ascending order.
- Then, the queued tasks which are sorted in the order – they will be processed from the queue.
- And the last rows – are completed tasks sorted by Finish time in descending order.
The ‘indexing status’ is displayed in the indexing log dialog that appears during manual reindex. The View log information from the Indexing Queue Qiewer is similar to the logs that can be viewed in the Manage integration screen.
For encountered errors when indexing, open the logs via Actions ➜ View log. Copy the message log and submit this to us thru [email protected] or via Support portal for analysis. For the above example error, there are several factors that caused this error – the Git service is down, no internet connection, the webhook has changed or the personal access token has expired.
Indexing queue list
On the next indexing run, the finished tasks for some repository are removed from the queue. This is regardless of the reindex trigger whether scheduled, webhook or manual. The max age for old finished tasks is 1 hour (see below).
The indexing queue does not remove the task from the queue when any of the following conditions is true:
this task is the last one of this type for this integration/repository
this task is not older than 1 hour from now
For removed integrations/repositories., the pending queued tasks related to removal are deleted from the indexing queue list.
The indexing queue can spread the indexing work across several nodes. Thus, the most volume of the indexing tasks will be performed on a multi-node Jira. We recommend using a 4-node configuration.
View indexing details
On the left of the first column, click the > symbol to expand the detailed view of the index task in the queue.
In this column, the amount of time from when the task has finished indexing is shown.
This column displays the name of the integrations where indexing tasks has been performed.
This column displays the name of the repositories where indexing tasks has been performed. Also displayed is the organization (GitHub) or group (GitLab) name before the repository name indicating it’s under that org or group.
Type of operation
The type of operation states what kind of indexing was triggered:
- Garbage collection
This column shows No delay for indexed items that were processed immediately after the previous one. Also displayed are the amount of time when the indexing has finished for the tasks.
This column shows what kind of operation triggered the reindex for this task.
This column shows the indexing status of the task in the list.
At the bottom-left portion of the indexing queue viewer, click the Refresh icon to refresh the queue list view.
At the bottom-right portion of the indexing queue viewer, use the page controls to navigate across the task page list.