This push is too large to process when pushing large amount of data
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When pushing a large amount of data, Bitbucket Server responds with This push is too large to process.
1
2
3
4
5
6
7
8
9
$ git push --tags bitbucket
Counting objects: 14216, done.
Delta compression using up to 12 threads.
Compressing objects: 100% (5834/5834), done.
Writing objects: 100% (13883/13883), 652.76 MiB | 5.09 MiB/s, done.
Total 13883 (delta 9575), reused 11455 (delta 7654)
remote: This push is too large to process.
remote: Communication breakdown with Bitbucket Server.Cause
This is caused by the amount of data exceeding the buffer size used when marshaling data between the SSH or HTTP socket and the Git process.
Resolution
Double the buffer size by adding the following to
$BITBUCKET_HOME/shared/bitbucket.properties:bitbucket.properties
1 2 3 4 5# If using SSH for pushing add the following: plugin.bitbucket-scm-git.backend.ssh.buffer.size=65536 # If using HTTP for pushing add the following: plugin.bitbucket-scm-git.backend.http.buffer.size=65536
Was this helpful?