Search code examples
artifactory

Artifactory OSS - Missing "eventual" binary provider?

I am using Artifactory OSS 7.55.3, on a Windows host, attempting to set up a simple cached NFS binary store. I cannot, for the life of me, get the "eventual" binary provider to load, I'm starting to believe it's simply not included in the release, but I see no indications of that in the documentation. Instead, Artifactory will fail to start with an error.

My binarystore.xml is as follows:

<config version="1">
    <chain>
        <provider id="cache-fs" type="cache-fs">
            <provider id="eventual" type="eventual">
                <provider id="file-system" type="file-system"/>
            </provider>
        </provider>
    </chain>
    <provider id="eventual" type="eventual">
        <numberOfThreads>10</numberOfThreads>
    </provider>
    <provider id="cache-fs" type="cache-fs">
        <maxCacheSize>15000000000</maxCacheSize>
    </provider>
    <provider id="file-system" type="file-system">
        <fileStoreDir>\\NAS\filestore\location</fileStoreDir>
    </provider>
</config>

While all docs seem to indicate this is a valid setup, Artifactory will fail to start with the following error (and a massive stacktrace that will not bother posting):

[jfrt ] [ERROR] [1f17a84536975ce6] [ctoryContextConfigListener:126] [art-init ] - Application could not be initialized: Cannot invoke "java.lang.Class.newInstance()" because "binaryProviderClass" is null

Is there something I'm missing? Is the "eventual" binary provider not available in OSS, and is there a version where it is? The transfer to the NFS is pretty slow, making artifact upload times pretty unusably bad for large artifacts (10+gb), and it'd be great to use the local ssd as a temporary filestore to keep upload times down.

Solution

  • The eventual binary provider connects to the cloud providers buckets such as S3, and Azure blob storage as explained in the JFrog wiki page.

    As per this S3 wiki, the cloud providers are supported for JCR, Pro, Enterprise and Enterprise+ subscriptions therefore it is expected that the eventual is not getting considered in the OSS version.

    As suggested here in this wiki, you should skip using the eventual binary provider and use the cache-fs and file-system templates.