s3ManagedLedgerOffloadReadBufferSizeInBytes not work when set in broker
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 160
Description
**Describe the bug**
When set s3ManagedLedgerOffloadReadBufferSizeInBytes,managedLedgerOffloadMaxThreads,managedLedgerOffloadPrefetchRounds in the broker.conf,it not work in namespace.
**To Reproduce**
Steps to reproduce the behavior:
1. set the configures in the broker.conf
2. trigger the offload for a namespace `bin/pulsar-admin namespaces set-offload-threshold --size 100M test-tenant2/ns2`
3. check the policy `bin/pulsar-admin namespaces get-offload-policies test-tenant2/ns2` and get the following
```
{
"offloadersDirectory" : "./offloaders",
"managedLedgerOffloadMaxThreads" : 2,
"managedLedgerOffloadPrefetchRounds" : 1,
"managedLedgerOffloadThresholdInBytes" : 104857600,
"managedLedgerOffloadedReadPriority" : "TIERED_STORAGE_FIRST",
"s3ManagedLedgerOffloadMaxBlockSizeInBytes" : 67108864,
"s3ManagedLedgerOffloadReadBufferSizeInBytes" : 1048576,
"s3ManagedLedgerOffloadRoleSessionName" : "pulsar-s3-offload",
"gcsManagedLedgerOffloadMaxBlockSizeInBytes" : 67108864,
"gcsManagedLedgerOffloadReadBufferSizeInBytes" : 1048576,
"s3Driver" : false,
"gcsDriver" : false,
"fileSystemDriver" : false
}
```
**Desktop (please complete the following information):**
- OS: Centos7
Contributor guide
Assessment
This issue has not been assessed yet.