I understand the typical scenario, a repository grows over the limit of 2 GB and support has to run a gc, and/or other protocols are followed to reduce the size of a repository. The thing is, in our case the repository grew from 161 mb to 14 gb suddenly while we are pushing to it. Support ran gc for us and told us to take a new clone of the fixed repo which I had all developers do. Well it happened again within 24 hours. Now we are on this continuous cycle where I have to create a case with Atlassian asking them to run gc for us. Sometimes they do it within 5 minutes, but lately it takes them 5 to 6 hours and we just don't have the luxury of time. I'm appealing to the community to see if anyone had this odd behavior, or if this is typical of a repository's behavior.
We have run gc's, prunes, took a new clone. I mean, surely we are not pushing over 13 GB's of garbage to the repository, we would know that it would take forever. I think something is inherently wrong with the repository on the server side.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.