All Versions
Fisheye 4.2 DocumentationFisheye 4.1 Documentation
Fisheye 4.0 Documentation
More...
If 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.
To re-index a temporary copy of your FishEye instance:
config.xml
of your temporary FishEye instance to point to your temporary repository.FISHEYE_INST
directory.FISHEYE_INST/var/cache
directory on live FishEye with the FISHEYE_INST/var/cache
from your test server.To make a copy of your FishEye instance, follow the instructions for Migrating FishEye Between Servers.
To make a copy of your repository, do the following. Use rsync (for CVS repositories in the Linux environment) or svnsync documentation (for Subversion only).
If 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).
2. Add a repository to Crucible with the exact same name and details as that referenced by the production server.
3. Let that finish indexing. Go to 'Administration' > 'View Repository List' > 'Stop' (shown next to the name of your repository) and disable on both production and test.
4. Copy over the FISHEYE_INST/var/cache/REPO
directory on the production FishEye with the FISHEYE_INST/var/cache/REPO
directory from the test server.
For this procedure, neither server needs to be shut down.
3 Comments
Anonymous
If you have Crucible, you may have to reindex the Review Revision Index. My Commit Graphs didn't show up with associated Reviews until I did that.
Anonymous
sPacdedHi,
How to reindex the Review Revision Index?
Anonymous
"How to Re-Index a Single Repository on a Test Server" should better highlight that you have to STOP and DISABLE the repo on both sides. If you only Stop on the server that has the fully indexed copy it detects an "upgrade" which wasn't an upgrade because source was upgrade already and starts a initial index of the Repo. Even when Stopped and Disabled on the source before copying the cache files Crucible still starts "Re-indexing changesets" but judging by the speed it's working through revs this is not a full index (despite the fact that revs don't show in the change list until this re-index has reached them.
Atlassian, can you publish a document that better describes the different indexes and re-indexes so our hearts don't stop when we see a reindex pop up and think that it's going to run for the next 48 hours in Prod?