During the snapshot phase of a PeerDB mirror creation, the sync fails while uploading multipart files to S3-compliant storage (OCI). The error indicates that the storage provider does not support AWS chunked encoding, which is often enabled by default in modern S3 SDKs for multipart uploads.
Error Message
failed to sync records: failed to write records to S3: failed to upload file: upload multipart failed, upload id: feb71ad6-06e3-5392-f8c4-604f7b9e94bd, cause: operation error S3: UploadPart, https response error StatusCode: 501, RequestID: jed-1:NRdVWcmDciKAhlAG6Ew9JdGtjaq38Ymcu_7ac06hxrNp3ATasbwGQYO-KkJ91Xr1, HostID: , api error NotImplemented: AWS chunked encoding not supported.
Environment
- PeerDB Version: stable-v0.36.4
- Storage Provider: OCI (Oracle Cloud Infrastructure) S3-Compliant Object Storage
- Deployment: Kubernetes
Steps to Reproduce
- Configure a PeerDB mirror using OCI Object Storage for staging .
- Initiate the mirror creation.
- Observe the logs during the initial snapshot phase.
Attempted Workarounds
- Reduced
PEERDB_S3_PART_SIZE to 5MB to see if smaller parts would bypass the chunked encoding requirement; however, the error persisted.
During the snapshot phase of a PeerDB mirror creation, the sync fails while uploading multipart files to S3-compliant storage (OCI). The error indicates that the storage provider does not support AWS chunked encoding, which is often enabled by default in modern S3 SDKs for multipart uploads.
Error Message
Environment
Steps to Reproduce
Attempted Workarounds
PEERDB_S3_PART_SIZEto5MBto see if smaller parts would bypass the chunked encoding requirement; however, the error persisted.