NiuBlibing commented on issue #16294:
URL: https://github.com/apache/pulsar/issues/16294#issuecomment-1171143971

   > managedLedgerOffloadReadBufferSizeInBytes
   
   s3,
   ```
   ls offloaders/*
   offloaders/tiered-storage-file-system-2.10.0.nar  
offloaders/tiered-storage-jcloud-2.10.0.nar
   ```
   ```
   ### --- Ledger Offloading --- ###
   
   # The directory for all the offloader implementations
   offloadersDirectory=./offloaders
   
   # Driver to use to offload old data to long term storage (Possible values: 
aws-s3, google-cloud-storage, azureblob, aliyun-oss, filesystem)
   # When using google-cloud-storage, Make sure both Google Cloud Storage and 
Google Cloud Storage JSON API are enabled for
   # the project (check from Developers Console -> Api&auth -> APIs).
   managedLedgerOffloadDriver=aws-s3
   
   # Maximum number of thread pool threads for ledger offloading
   managedLedgerOffloadMaxThreads=20
   
   # Maximum prefetch rounds for ledger reading for offloading
   managedLedgerOffloadPrefetchRounds=100
   
   # Use Open Range-Set to cache unacked messages
   managedLedgerUnackedRangesOpenCacheSetEnabled=true
   
   # For Amazon S3 ledger offload, AWS region
   s3ManagedLedgerOffloadRegion=[xxxx]
   
   # For Amazon S3 ledger offload, Bucket to place offloaded ledger into
   s3ManagedLedgerOffloadBucket=[xxxxx]
   
   # For Amazon S3 ledger offload, Alternative endpoint to connect to (useful 
for testing)
   s3ManagedLedgerOffloadServiceEndpoint=http://[xxxx]
   
   # For Amazon S3 ledger offload, Max block size in bytes. (64MB by default, 
5MB minimum)
   s3ManagedLedgerOffloadMaxBlockSizeInBytes=67108864
   
   # For Amazon S3 ledger offload, Read buffer size in bytes (1MB by default)
   #s3ManagedLedgerOffloadReadBufferSizeInBytes=1048576
   s3ManagedLedgerOffloadReadBufferSizeInBytes=671088640
   
   ```


-- 
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]

Reply via email to