GC Request

[Lamak Qaizar]

Hi team,

Could you please run GC on this repo: ****wasi/metis-app/

It has crossed a 2 GB threshold due to which integration with AWS CodePipeline is failing. We've deleted some large files so a GC should help bring down the size.

Thank you very much.

[Syahrul · Accepted solution]

G'day, @Lamak Qaizar 

Welcome to the community!

I have triggered the Git GC on the affected repository, but the size remains at 1.8 GB, so we may need to review the repository further to understand why the GC did not reduce the size.

I have proceeded to raise a support ticket on behalf of you, please view it at our:

Support portal 

Regards,
Syahrul

[Lamak Qaizar]

Thank you @Syahrul

[muzzammilfarooq]

Hi @Syahrul  ,

Any update regards above request, we are close to 2.GB . This will halt our CICD operations . 

[Theodora Boudale]

Hi @muzzammilfarooq,

1. How did you delete the large files from the repo? Did you rewrite history e.g. with git filter-branch or with BFG repo cleaner? Or did you commit file deletions?

2. Could you please try the following:

Take a mirror clone of the repo with the command

git clone --mirror <repo_url>

Change directory to the mirror clone

cd <repo-name>.git

Inside the directory of the mirror clone run the command

git count-objects -Hv

The sum of size and size-pack in the output will show the size of the mirror clone. Can you please post here the output of that command? I would like to see if the size of the mirror clone is similar to the size displayed in Bitbucket UI or smaller.

Kind regards,
Theodora

[Lamak Qaizar]

Hi @Theodora Boudale. Thank you for your response. The output of (2) is as follows:

count: 0
size: 0 bytes
in-pack: 615198
packs: 1
size-pack: 1.75 GiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes

Current size shown on BitBucket UI is 1.87 GB. 

For (1), we will get back to you. The colleague that deleted files is out of office at the moment. We have not rewritten history yet (as far as I know) since I assume that will require us to freeze the repo, rewrite history and then everyone has to take a fresh clone.

Let us know if there is an easier way to do it.

[Syahrul]

Hi @Lamak Qaizar 

Thanks for the update. Our repository size limit is 4 GB, so you can still use it without being blocked until it hits the limit.

Please let me know once the user returns so we can raise a support ticket to investigate this issue further.

Regards,
Syahrul

[Lamak Qaizar]

Hi @Syahrul. Will let you know. Certain functionalities stop working at 2 GB which our pipelines are dependent on (AWS CodePipeline sourcing step stops working), so we're more concerned about the 2 GB limit.

[Syahrul]

Hi @Lamak Qaizar 

Noted. I have raised a support ticket for you to continue the investigation. Please find the ticket at:

https://support.atlassian.com/requests/

Regards,
Syahrul