dave2wave opened a new issue #14693:
URL: https://github.com/apache/pulsar/issues/14693
**Description**
When an Offloaded Ledger's retention period has expired the JClouds call to
remove a Blob from the BlobStore silently fails.
**To Reproduce**
Steps to reproduce the behavior:
1. Setup `broker.conf` to include the following aggressive offloading options
```
# configure offloading to S3
managedLedgerOffloadDriver=aws-s3
managedLedgerMinLedgerRolloverTimeMinutes=1
managedLedgerMaxLedgerRolloverTimeMinutes=2
managedLedgerMaxEntriesPerLedger=500000
managedLedgerOffloadAutoTriggerSizeThresholdBytes=0
managedLedgerOffloadedReadPriority=tiered-storage-first
# Default message retention time - assure offloaded s3 bucket files are
deleted.
defaultRetentionTimeInMinutes=10
offloadersDirectory=./offloaders
s3ManagedLedgerOffloadBucket={{ s3_bucket }}
s3ManagedLedgerOffloadRegion={{ s3_region }}
s3ManagedLedgerOffloadServiceEndpoint={{ s3_url }}
loadBalancerAutoUnloadSplitBundlesEnabled=false
```
2. Run a pulsar workload with [OpenMessaging
Benchmark](https://github.com/datastax/openmessaging-benchmark) in AWS using
the broker configuration above.
3. Wait for 30 minutes after the worklo
4. Visit your [AWS S3 Console](https://s3.console.aws.amazon.com/s3/buckets)
and see that the offloaded blobs are still in your S3 Bucket.
**Expected behavior**
All of the S3 blobs except for the most recent should be removed.
**Additional context**
I have a fix and will be submitting a PR shortly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
