JFrog

    JFrog Help Center

    Our new portal is coming soon!
    Documentation + Knowledge Base





    JFrog Help Center - A new knowledge experience is coming your way soon!


    Skip to end of metadata
    Go to start of metadata

    Sharding-Cluster Binary Provider Overview

    The sharding-cluster binary provider can be used together with other binary providers for both local or cloud-native storage.

    它增加了crossNetworkStrategy parameter to be used as read and write behaviors for validation of the redundancy values and the balance mechanism. It must include aRemote Binary Providerin its dynamic-provider setting to allow synchronizing providers across the cluster.

    The Sharding-Cluster provider listens to cluster topology events and creates or removes dynamic providers based on the current state of nodes in the cluster.


    Page Contents

    Sharding-Cluster Binary Provider Template

    type
    		 sharding-cluster
    zones

    The zones defined in the sharding mechanism. Read/write strategies take providers based on zones.
    lenientLimit

    Default: 1 (From version 5.4. Note that for filestores configured with a custom chain and not using the built-in templates, the default value of the lenientLimit parameter is 0 to maintain consistency with previous versions.)

    Theminimumnumber of successful writes thatmust be maintained for an upload to be successful. The next balance cycle (triggered with the GC mechanism) will eventually transfer the binary to enough nodes such that the redundancy commitment is preserved.
    In other words, Leniency governs the minimal allowed redundancy in cases where the redundancy commitment was not kept temporarily.

    For example, if lenientLimit is set to 3, my setup includes 4 filestores, and 1 of them goes down, writing will continue. If a 2nd filestore goes down, writing will stop.

    The amount of currently active nodes must always be greater or equal than the configured lenientLimit. If set to 0, the redundancy value has to be kept.
    dynamic-provider
    		 The type of provider that can be added and removed dynamically based on cluster topology changes. Currently only theRemote Binary Provideris supported as a dynamic provider.

    Sharding-Cluster Binary Provider Example

               crossNetworkStrategy crossNetworkStrategy 2 1   filestore1   15000 5000 15000 200 2 remote
    • No labels
    Copyright © 2023 JFrog Ltd.