3 git processes killing stash!

Timothy Harris July 5, 2016

Our Stash instance, 3.9.2 has some serious problems right now. The red banner saying that there was a resource issue showed up.

 

We stopped the service. There were three 3 git processes running wild and eating CPU and memory. We killed them. We shut down our CI server, in case it was the culprit. When we restarted the 3 git processes are back and eating the memory and cpu.

Looks like it is the following processes:
atlstash 9097 1 0 12:52 ? 00:00:00 git upload-pack --stateless-rpc .
atlstash 9098 9097 0 12:52 ? 00:00:00 git-upload-pack --stateless-rpc .
atlstash 9099 9098 81 12:52 ? 00:16:29 git pack-objects --revs --thin --stdout --delta-base-offset --include-tag
atlstash 9240 1 0 12:54 ? 00:00:00 git upload-pack --stateless-rpc .
atlstash 9241 9240 0 12:54 ? 00:00:00 git-upload-pack --stateless-rpc .
atlstash 9242 9241 75 12:54 ? 00:14:00 git pack-objects --revs --thin --stdout --delta-base-offset --include-tag
atlstash 9667 1 0 13:02 ? 00:00:00 git upload-pack --stateless-rpc .
atlstash 9668 9667 0 13:02 ? 00:00:00 git-upload-pack --stateless-rpc .
atlstash 9669 9668 63 13:02 ? 00:06:27 git pack-objects --revs --thin --stdout --delta-base-offset --include-tag

This is quite critical for us and is causing major pain! Anyone have any ideas?

 

 

1 answer

1 accepted

0 votes
Answer accepted
Ben Stuart
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 5, 2016

This issue is most likely caused by server side corruption of your Git repository. Please open up a support request at  https://support.atlassian.com

For more information please see our article here: 

https://confluence.atlassian.com/bitbucketserverkb/recommended-action-plan-if-a-repository-becomes-corrupted-on-a-bitbucket-server-779171653.html

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events