I recently needed to reindex a repository on Fisheye. Since my last index, we deleted several hundred branches from the repository, many of them during one day of cleanup. Fisheye has been hung indexing for almost 3 weeks running a diff one revision (the one where we deleted hundreds of branches).
If I run the command locally, it looks like it is comparing against each file in the repository for each of those hundreds of revisions. But even so I feel like it is taking way to long to index. Any ideas would be greatly appreciated.
We appreciate you coming to Community for your long-running index issue after you did a large cleanup of your branches. With this said, depending on the amount of data that was cleaned, the re-index has been reported to take hours or days to complete. With this said, 3 weeks does sound like a long time but this will be relative to the amount of data needing to be re-indexed and also the performance of your fisheye server. Additionally, if your storage that your Fisheye server resides on are not optimal then you may also experience slower than expected re-indexing times due to I/O speed issues. Further information on the hardware requirements can be found at Supported platforms under Hardware requirements.
Here is additional information to know about re-indexing:
Due to the complexity of SCM repositories, an indexing scan may take many hours or even days to complete. During this time, your Fisheye users may be inconvenienced as they will not by able to view the repository being indexed. Furthermore, Crucible users will not be able to carry out reviews unless you have Crucible set to store all revisions offline.
Source documentation: Re-indexing your repository
Alternatively, if you believe the issue is the application having a problem then please review the logs and let us know of any warning or errors present in the logs. This will help us to understand what could also be causing the delay in completing the re-index.
I appreciate the response. The index has been running since 09/23 on the same changeset. To speed things up, I had previously moved the repository locally to speed up indexing and the disk is actually an SSD. At this point I'm just waiting to see if it will ever finish.
I'm honestly not sure if we did something incorrectly in Subversion when we deleted those branches, or if this is just a normal outcome as part of the Fisheye index. Any suggestions on how to get through this would be greatly appreciated.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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