Eventual Binary Provider Configuration
To overcome potential latency, files are first written to a folder called “eventual” under thebaseDataDirin local storage, and then later uploaded to persistent storage with the cloud provider. The default location of theeventual
folder is under the $JFROG_HOME/artifactory/data/artifactory
folder and is not configurable. You need to make sure that Artifactory has full read/write permissions to this location.
There are three additional folders under theeventua
l folder:
- _pre: part of the persistence mechanism that ensures all files are valid before being uploaded to the remote filestore
- _add: handles upload of files to the remote filestore
- _delete: handles deletion of files from the remote filestore
Example
The example below shows a configuration that uses S3 for persistent storage after temporary storage with an eventual binary provider. The eventual provider configures 10 parallel threads for uploading and a lock timeout of 180 seconds.
XXXXXXXXX XXXXXXXX false 10 180000
Where:
type |
eventual |
timeout |
The maximum amount of time a file may be locked while it is being written to or deleted from the filesystem. |
dispatcherInterval |
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 并行线程的数量应该是紧密相联的cated for uploading files to persistent storage. |