Indexed paths truncated at 10000
Problem
Some folders or files appear to be missing when browsing a repository in Fisheye.
The following appears in the atlassian-fisheye-YYYY-MM-DD.log:
INFO [METADATA-2 <repository_name>[<revisionId1>-<revisionId2>] <repository_name>] fisheye PathIndexer$1-visit - Changeset <revisionId2>: indexed paths truncated at 10000
INFO [METADATA-2 <repository_name>[<revisionId3>-<revisionId4>] <repository_name>] fisheye PathIndexer$1-visit - Changeset <revisionId4>: indexed paths truncated at 10000
INFO [METADATA-2 <repository_name>[<revisionId5>-<revisionId6>] <repository_name>] fisheye PathIndexer$1-visit - Changeset <revisionId6>: indexed paths truncated at 10000Or the following (for older Fisheye versions):
INFO [InitialPinger2 XXXXX] fisheye.app ChangesetDocBuilder-buildPathFields - Changeset 7248: indexed paths truncated at 10000
INFO [InitialPinger2 XXXXX] fisheye.app ChangesetDocBuilder-buildPathFields - Changeset 7872: indexed paths truncated at 10000
INFO [InitialPinger2 XXXXX] fisheye.app ChangesetDocBuilder-buildPathFields - Changeset 7914: indexed paths truncated at 10000
Cause
An svn copy or an svn move containing more than 10000 path changes has been performed on the repository.
By default Fisheye/Crucible processes a maximum of 10000 change paths per changeset. This is to prevent extremely large changesets (which are sometimes the result of human error) from slowing Fisheye/Crucible down. If the path changes are legitimate (copy a large trunk to a branch [FE-3949]), you can change the default value as described below.
Resolution
- Change the default value by modifying the system property fisheye.changeset.paths.limit (See environment variables for more information on setting the property):
FISHEYE_OPTS=-Dfisheye.changeset.paths.limit=20000- Restart Fisheye for the change to be considered
- Re-index the repository in order to have past changesets properly indexed.
Last modified on Nov 9, 2018
Powered by Confluence and Scroll Viewport.