How Do I Manually Delete The Repository Cache And Trigger The Reindexing

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

To manually delete the repository cache and trigger the reindexing of the repository, the following steps can be performed against the repository in your instance.

  1. Navigate to Fisheye administration page Repository Settings > Repositories

  2. Stop the affected repository by selecting from the dropdown option in the Action column

  3. Shutdown Fisheye instance

  4. Backup and delete the cache folder of the affected repository at FISHEYE_INST/var/cache/MyRepoName directory

  5. Start Fisheye instance

  6. Start the repository from the dropdown option in the Action column and this will trigger the reindexing of the repository

This can also be achieved through Fisheye's User Interface by following the below steps:

  1. Navigate to Fisheye administration page Repository Settings > Repositories

  2. Select the repository under the Name column

  3. Select the Maintenance link

  4. Select Start for Re-clone and Re-index

This deletes the existing clone and cache and re-index the repository from scratch. For large or slow repositories this may take some time, during which some functionality will be unavailable. This action will also restart the repository.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.