#### Expected behavior Offload is expected to work.
#### Actual behavior The following happens when I try to offload manually using: `pulsar-admin topics offload --size-threshold 0 public/default/my-topic && pulsar-admin topics offload-status -w public/default/my-topic` > Offload triggered for persistent://public/default/my-topic for messages > before 6:0:-1 > Error in offload > null > > Reason: Error offloading: > org.apache.bookkeeper.mledger.ManagedLedgerException: > java.util.concurrent.CompletionException: > java.lang.UnsupportedOperationException > command terminated with exit code 1 The last broker log regarding offloading: > INFO org.apache.bookkeeper.mledger.impl.ManagedLedgerImpl - > [public/default/persistent/my-topic] Metadata prepared for offload of ledger > 4 with uuid da861b42-3d30-4158-babd-f8a73e5850b7 Everything else about the cluster seems to be running fine by the looks of logs and grafana. #### Steps to reproduce Spin up a new kubernetes cluster on gcp and try offloading to tiered storage following the [cookbook](https://pulsar.apache.org/docs/en/cookbooks-tiered-storage/) I have tried both the helm deployment and the gcp specific one and I have also tried both gcp and aws-s3 storage. #### System configuration **Pulsar version**: 2.1.1 [ Full content available at: https://github.com/apache/pulsar/issues/2697 ] This message was relayed via gitbox.apache.org for [email protected]
