Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-17438

Allow per-node binarystore.xml property changes

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Currently the entire binarystore.xml file is synchronized between HA nodes. This is inflexible as it means the same settings are applied regardless of the host's configuration.

      Take a 2 node HA cluster where one host has 100 GB of disk space while the other has 1 TB. The binarystore.xml can only use 100GB of space as increasing this value will overload one of the nodes.

      Most Binary providers are not compatible with each other (E.G. the S3 configuration and the cluster-s3 configuration), but the same provider template has variable settings that can change.

      For example, there could be a "$cache" variable in the binarystore.xml, and a second "binary-variables.xml" file that specifies the cache-fs size on each node.

      The "binary-variables.xml" file would not be synchronized across nodes, much like the logback.xml file is not synchronized.

       

      As an alternative solution, there could be an artifactory.system.properties value that disables binarystore.xml syncing on HA nodes. The setting should be labeled as an Advanced feature, as it would further complicate any conflicts.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            patrickr Patrick Russell
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: