Optimising the Search Indexes on Restart

FishEye/Crucible allows you to optimise the search indexes when you restart your instance.

You can use this feature to:

• Reduce the size of the search indexes,
• Make the search faster if the indexes are significantly under-optimised, and
• Reduce the number of "Too many open files" errors that you might see in the logs. This is useful on systems where FishEye or Crucible have constraints on the number of files they can open.

In most circumstances, the search indexes should be fairly close to their optimal state. This is usually the case when using Crucible with FishEye, or when using FishEye alone. The search technology we use, Lucene, results in indexes fairly close to optimal when most of the operations on the indexes are additions (the additions are the changesets that are indexed as they appear in your repositories). For this reason, it should not be necessary to run the optimisation often.

When you are using this feature, the optimisation will run solely on the next start. It will not run every time FishEye or Crucible starts, to prevent slowing the start of your instance. The optimisation itself should be fast, and within 10 minutes even for large indexes.

Running the Optimisation

1. Navigate to the FishEye/Crucible administration console.
2. Click the 'Shutdown' link in the left menu. Note, you will need to confirm the shutdown at a confirmation screen before your instance is shut down.
3. In the window that appears, click the 'Optimize the search indexes the next time that FishEye and Crucible start' checkbox (or 'Optimize the search indexes the next time that FishEye/Crucible starts' if you are using either FishEye or Crucible alone).
4. Click 'Shutdown'. Your instance will be shut down, and the optimisation of the search indexes will be scheduled for the next startup.