-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offloading large ledgers (>2GB) fail with Google Cloud Storage #15159
Labels
Comments
The issue had no activity for 30 days, mark with Stale label. |
The issue had no activity for 30 days, mark with Stale label. |
The related JClouds issue has been fixed in version 2.6.0. |
pgier
added a commit
to pgier/pulsar
that referenced
this issue
Mar 7, 2024
This was referenced Mar 7, 2024
pgier
added a commit
to pgier/pulsar
that referenced
this issue
Mar 12, 2024
pgier
added a commit
to pgier/pulsar
that referenced
this issue
Mar 12, 2024
pgier
added a commit
to pgier/pulsar
that referenced
this issue
Mar 12, 2024
Merged
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Offloading large ledgers fail with Google Cloud Storage and the default settings. With default settings offloading ledgers over 2GB will fail to GCS since there's a limitation in JClouds (reported as [JCLOUDS-1606] Cannot upload more than 32 parts to GCS) which limits a multipart upload to 32 parts. GCS supports multipart uploads up to 10000 parts, but JClouds doesn't use the API in a way to achieve more than 32 parts.
Here's an example log entry of the problem:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Ledger offloading should work with large ledger sizes
Workaround
or
Additional context
JClouds issue reported as [JCLOUDS-1606] Cannot upload more than 32 parts to GCS.
The text was updated successfully, but these errors were encountered: