We use Bamboo for building and Stash for our Git repository. Over the past month or so we've been seeing increasingly slow performance, especially after server restarts and particularly when listing branches and deployment plans.
At first we thought it was related to the upgrade, the size of the JVM heap or the number of remote agents. It turns out the problem was a little more subtle.
When the server is restarted it loses its Stash authentications, and we see hundreds of errors and a flood of activity as Bamboo re-authenticate. What Bamboo asks for a branch makes matters worse "Save the repository configuration to refresh the authentication details", Instead of using the default setting the branch now has its own, private settings and does its own git request. This means on the order of a hundred git requests every couple minutes. After a while this pushes CPU I/O utilization sky-high and slows the server to a crawl, especially on dynamically-generated content like the afore-mentioned deploy plans and branch listings.
Here are my questions
- Is there anyway to automatically detect which branches are using defaults, and which are using this custom/saved setting?
- Is there anyway to programmatically get the branches to use the default setting without going through each branch plan by hand?
- Is there a way of getting Bamboo to wait after it starts up and send the requests to Stash at some reasonable rate, retry in batches or in some other way avoid the flood of "Errors getting changes for HERP-DIDERP1183-1 This error may have occurred due to an authentication issue with Stash. Save the repository settings to refresh the authentication details.
(08 Jun 2015, 9:01:36 AM)"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.