Fix performance issues for nested cloned repositories with enabled Git Service Permissions mode

Problem

There will be some performance issues when the following conditions are met:

• you are using GIJ 4.19 or earlier

• you have enabled “Enforced git permissions” in General settings

• with each reindex of some of your integration, GIJ also tries to detect new nested repositories, which for some reason, can’t be cloned. The root cause could be one or some of the following:

  • Corrupt pack file errors

  • Max object size error

  • Git -upload pack errors for multiple repositories

  • Timeout errors

  • 401 error with a different user

  • Error getting repository permissions for user XXXXXXXX – 401 unauthorized error

Diagnosis

With each reindex of the integration, permissions for all the users PATs are recalculated. It’s a heavy calculation degrading performance, high CPU usage and increasing a possibility of exceeding GitService rate limit.

Solution

Upgrade to GIJ 4.20 or later.

If you can’t upgrade due to production workflow policies for now, then setup a JMESPath filter for the integration to exclude the affected nested repositories.

More articles about troubleshooting, workarounds and solutions

Why I am getting the error, “git-upload-pack not permitted”?

Avoid OutOfMemory exceptions by configuring or memory allocation with Jira to accommodate large repositories

Cannot auto-deploy some tracked repositories: Specified origin is incorrect or not supported

Connection Reset when Accessing the Database

“Dangerous use of multiple connections” error on local database

Duplicate entry 0 for key PRIMARY exceptions in log

Error while reindexing – Java heap space / Object too large, rejecting the pack

Error creating git branches and also using NFS

Fix performance issues for nested cloned repositories with enabled Git Service Permissions mode (this page)

Fixing reindex issues using Indexing Queue Viewer

Gitolite integration: Why the Git integration app not see the master branch?

Health Check: Database Collation

Indexing error – Too many open files

Installation fails when installing manually

Jira index error: IndexNotFoundException: no segments* file found

Malformed input or input contains unmappable characters

Personal access token failing Azure DevOps integration with Not Authorized error

Problems with shared home on Azure Storage

Pull request index error: org.json.JSONException

Repositories missing from Azure DevOps integration

“Service proxy has been destroyed” exceptions in log

SQLException ‘Incorrect string value’ in merge requests

SSH key file format is invalid

TFS – Not authorized exception when Jira works thru proxy

Unexpected exception parsing XML document from URL error in log

Why don’t I see the Create Branch or Pull Request features?