S3 Configuration - With Artifactory
Eventual Binary Provider
This provider is useful when configuring any storage that may exhibit upload latency (e.g. S3 or GCS). To overcome potential latency, files are first written to a folder called “eventual” under the baseDataDir in local storage, and then later uploaded to persistent storage with the cloud provider.
id
eventual
timeout
The maximum amount of time a file may be locked while it is being written to or deleted from the filesystem.
dispatchInterval
Default: 5000 ms
The interval between which the provider scans the “eventual” folder to check for files that should be uploaded to persistent storage.
numberOfThreads
Default: 5
The number of parallel threads that should be allocated for uploading files to persistent storage.
This provider is useful when configuring any storage that may exhibit upload latency (e.g. S3 or GCS). To overcome potential latency, files are first written to a folder called “eventual” under the baseDataDir in local storage, and then later uploaded to persistent storage with the cloud provider.
id
eventual
timeout
The maximum amount of time a file may be locked while it is being written to or deleted from the filesystem.
dispatchInterval
Default: 5000 ms
The interval between which the provider scans the “eventual” folder to check for files that should be uploaded to persistent storage.
numberOfThreads
Default: 5
The number of parallel threads that should be allocated for uploading files to persistent storage.
Comments
Post a Comment