FishEye 2.4 : How do I avoid long reindex times when I upgrade?
This page last changed on Oct 20, 2009 by edawson.
Mitigating Lengthy Re-Index TimesIf re-indexing your repository takes longer than you can allow, you can use a temporary copy of your repository and FishEye instance to reduce downtime during the re-indexing process. Re-indexing With a Temporary Copy of Your FishEye InstanceTo re-index a temporary copy of your FishEye instance: 1. Make a copy of your FishEye instance to another server. See 'How to Make a Temporary Copy of Your FishEye Instance' below for instructions. How To Make a Temporary Copy of Your FishEye InstanceTo make a copy of your FishEye instance, follow the instructions for Migrating FishEye Between Servers. How To Make a Temporary Copy of Your RepositoryTo make a copy of your repository, do the following. Use rsync (for CVS repositories in the Linux environment) or svnsync documentation (for Subversion only). How to Re-Index a Single Repository on a Test ServerIf you need to re-index your repository on your production system but don't want to burden your production server, carry out the following steps: 1. Install another instance of FishEye on a test server (the same FishEye version as the one you are using). |
![]() |
Document generated by Confluence on Oct 21, 2010 00:42 |