We restored production data to a test environment, went through the upgrade from 3.3.4 to 4.5.2 with few issues...EXCEPT one potential show stopper - following the upgrade, scanning and indexing started on all the repos. The first time we tried this (couple of weeks ago), the reindexing took 5 days. The second attempt has been indexing for about 24 hours so far.
Why is this happening? It can't be a desired behavior, right?
When upgrading Fisheye/Crucible, a re-index can be required for a few different reasons, primarily due to an actual change in how the index is stored or created. The nice thing is, there's an easy way to prevent any downtime on your production upgrade as the index (caches) can be generated by a test server and then simply copied into place on your production server once you upgrade production itself. This will result in your production machine only needing to run a simple incremental index to track anything new rather than rebuilding the index from scratch.
This process should reduce the time it takes to get your production server back up from several days to simply how long it takes to copy the index over your network and a few minutes for the incremental index.
If you have any questions on the topic, just let us know.
We're excited to announce the release of a long-requested feature on Statuspage. Now visitors to your status page can subscribe to get notified in Slack when you report an incident or maintenance. Th...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events