The following tables describe what is required for each single-service node. In a High Availability configuration, a single-service node represents each of the HA server instances. Supported Platforms: 18.04, 20.04 Breaking Change Affecting RPM/Yum/Linux Archive Installations on Centos 7.x* As part of our commitment to our customers to maintain the security and reliability of your JFrog Platform, from Artifactory version v7.43.x, JFrog Artifactory will officially run with JDK 17 and Tomcat 9.x on all installation types. Note that JDK 17 and Tomcat 9.x are not supported on all Centos 7.x versions. CentOS 8.x Support CentOS 8.x reached its end-of-life in December 2021. CentOS 8.x support for JFrog products will be deprecated by the end of June 2022. SLES 12 SP5 supports Docker Compose installation for all products except for pipelines. Reserving Ports for Services As JFrog adds additional services to the JFrog Platform portfolio, there is a need to "reserve" ports for the Platform to ensure that the service works properly. To this end, JFrog recommends reserving ports 8000-8100 (this is addition to the existing internal ports documented below). If the Mission Control microservice is enabled, you will need to take into account a +100MB memory footprint increase. For more information, see Migrating from Mission Control to Insight. Based on expected artifact storage volume. Fast disk with free space that is at least 3 times the total size of stored artifacts. Supported: Artifactory 7.0 to 7.6: MySQL 5.7. MySQL 5.6 is no longer supported as it has reached its EOL; users are requested to upgrade to the above versions of MySQL. Artifactory does not Kerberos SSO for MS SQL. PostgreSQL: MariaDB Insight (You can install and use Insight only if you use Artifactory 7.27.3 or later) Insight will only display Xray charts if you have Xray version 3.33.3 or later. Upgrade Xray to version 3.33.3 to view the Xray charts. Min requirements. Assuming running with an external database. By default, Insight stores one year of storage information, one year of metrics information, one year of events information (like garbage collection details), and one day of requests information. The following sizing information is provided based on the default configuration. If you want to use Insight in a high-availability configuration, you must have three or more odd number of nodes. Required: PostgreSQL Elasticsearch 5 GB 120 GB 8 GB 220 GB 14 GB 420 GB Mission Control Min requirements. Assuming running with an external database. Required: PostgreSQL Elasticsearch Xray The requirements presented here are based on the size of your environment. Use a dedicated server for Xray with no other software running to alleviate performance bottlenecks, avoid port conflicts, and avoid setting uncommon configurations. Up to 100k indexed artifacts, and 1K artifacts/builds per day 8082 Required: PostgreSQL: Xray and DB: 6 CPU Xray and DB: 24 GB Xray and DB: 500 GB (SSD, 3000 IOPS) The number of nodes above refers to High Availability (HA) setups, not Disaster Recovery. Distribution (Version 2.0 and above) Min requirements. Assuming running with an external database. 200 GB SSD storage 8082 Required: Supported: Application 4 cores Build Nodes 2 cores for Linux build nodes 4 cores for Windows 19 build nodes Application 8 GB Build Nodes 3.75 GB for Linux build nodes 8 GB for Windows 19 build nodes Pipelines does not support external Redis and you cannot use TLS for Redis. Required: RabbitMQ: 3.8.3 From version 7.41.4, Artifactory supports installation on ARM64 architecture through Helm and Docker installations. You must set up an external database as the Artifactory database since Artifactory does not support the bundled database with the ARM64 installation. Artifactory installation pulls the ARM64 image automatically when you run the Helm or Docker installation on the ARM64 platform. Currently, ARM64 support is not available for other JFrog products. Artifactory, Xray, and other JFrog products all need to be set with static IP addresses. These services also need to be able to communicate directly with each other over the same LAN connection. Hosting these services in geographically distant locations may cause health checks to temporarily fail. Ensure the ports are open and no firewalls block communications between these services.Requirements Matrix
Product Debian Centos* RHEL Ubuntu Windows Server Helm Charts SLES Artifactory 9.x, 10.x 7.x 7.x, 8.x 2016 or 2019 2.x, 3.x 12 SP5 Insight 9.x, 10.x 7.x 7.x, 8.x 18.04, 20.04 
2.x, 3.x 12 SP5 Mission Control 9.x, 10.x 7.x 7.x, 8.x 18.04, 20.04 2.x, 3.x 12 SP5 Xray 9.x, 10.x 7.x 7.x, 8.x 18.04, 20.04 2.x, 3.x Distribution 10.x 7.x 7.x, 8.x 18.04, 20.04 2.x, 3.x Pipelines 7.x 7.x, 8.x 18.04, 20.04 Build nodes only 2.x, 3.x Minimum System and Application Requirements
Product Processor Memory Storage External Network Port Internal Network Ports (default) Databases/Third Party Applications Artifactory (Version 7.0 and above)
Oracle (12.2, 18, 19)
Artifactory 7.7 and above: MySQL 5.7. and 8.x.
Microsoft SQL Server
(2012 and above)
(10.2.9-10.4, 10.5.9) Note: Refrain from using MariaDB 10.5.x versions other than version 10.5.9 due to this known issue).
(Version 1.0.1 and above)
Actual values may change based on the amount of data in your application.Up to 500 Artifactory Repositories 4 cores 500 to 1500 Artifactory Repositories 4 cores 1500 to 2500 Artifactory Repositories 4 cores More Than 2500 Artifactory Repositories Contact JFrog Support for sizing requirements.
(Version 4.0 to 4.7.x)
Actual values may change based on the amount of data in your application.4 cores 12 GB 100 GB
(Obsolete from Mission Control version 4.5 and above)
(Version 3.0 and above)
Supported:
Ubuntu 20.04 from version 3.82Up to 1M indexed artifacts, and 10k artifacts/builds per day Up to 2M indexed artifacts, and 20k artifacts/builds per day Up to 10M indexed artifacts, and 50k artifacts/builds per day Over 10M indexed artifacts, and 50k artifacts/builds per day Contact JFrog Support for sizing requirements.
Actual values may change based on the amount of data in your application.4 CPU 8 GB
PostgreSQL:
Redis 6.0.5Pipelines (Version 1.0 and above) 100 GB
PostgreSQL:ARM64 Support
Network
Java
Java-based products (Artifactory, Distribution, Insight, Mission Control) must run with JDK 17+. The JDK is already bundled into the applications.
- From Distribution 2.13.2, the required JDK version is JDK 17.
- From Artifactory 7.43.x, the supported JDK version is JDK 17, which will be bundled into Artifactory.
JDK 11 is no longer supported.
JVM Memory Allocation
While not a strict requirement, we recommend that you modify the JVM memory parameters used to run Artifactory.
You should reserve at least 512MB for Artifactory. The larger your repository or number of concurrent users, the larger you need to make the -Xms and -Xmx values accordingly.
Set your JVM parameters in the system.yaml configuration file.
shared: extraJavaOpts: "-Xms512m -Xmx2g"
Browsers
Artifactory has been tested with the latest versions of:
- Chrome
- Firefox
- Safari (for Mac)
- Edge (Chromium-based versions)
System Time Synchronization
The JFrog Platform requires time synchronization between all JFrog services within the same Platform.
Unsynchronised services may cause issues during authentication and token verification.
Docker Requirements
For Docker and Docker Compose installations, JFrog services require Docker v18 and above (for Pipelines 18.09 and above) and Docker Compose v1.24 and up to be installed on the machine on which you want to run on.
For install instructions, please refer to the Docker and the Docker Compose documentation.
Helm Chart Requirements
For Helm Charts installations, JFrog services requires the following prerequisites/requirements:
- Kubernetes 1.12+ (for installation instructions, see Kubernetes installation)
- Kubernetes cluster with:
- Dynamic storage provisioning enabled
- Default StorageClass set to persistent storage
JFrog validates compatibility with the core Kubernetes distribution. Since Kubernetes distribution vendors may apply additional logic or hardening (for example, OpenShift and Rancher) JFrog Platform deployment with such platform vendors might not be fully supported.
Special Requirements
Artifactory
Working with Very Large Storage
In most cases, our recommendation is for storage that is at least 3 times the total size of stored artifacts in order to accommodate system backups. However, when working with a very large volume of artifacts, the recommendation may vary greatly according to the specific setup of your system. Therefore, when working with over 10 Tb of stored artifacts, please contact JFrog support who will work with you to provide a recommendation for storage that is customized to your specific setup.
Allocated storage space may vary
Xray downloads and then deletes fetched artifacts after indexing. However, in order to have more parallel indexing processes, and thereby more temporary files at the same time would require more space.
This is especially applicable for large BLOBs such as Docker images.
Installation Recommendation
While Artifactory can use a Networked File System (NFS) for its binary storage, you should do not install the application itself on an NFS. The Artifactory application needs very fast, reliable access to its configuration files. Any latency from an NFS will result in poor performance when the application fails to read these files. Therefore, install Artifactory on a local disk mounted directly to the host.
To use an NFS to store binaries, use the "file-system" binarystore.xml configuration with the additional "<baseDataDir>" setting.
Xray
Node Recommendations
Use a dedicated node for Xray with no other software running to alleviate performance bottlenecks, avoid port conflicts, and avoid setting uncommon configurations.
Storage Recommendations
In most cases, our recommendation is to use an SSD drive for Xray to have better performance and it is not recommended to use an NFS drive, as it is a disk I/O-intensive service, a slow NFS server can suffer from I/O bottlenecks and NFS is mostly used for storage replication.
Since the local storage used for Xray services are temporary, it does not require replication between the different nodes in a multi-node/HA deployment.
File Handle Allocation Limit
Avoid performance bottlenecks
In the process of deep recursive scan in which Xray indexes artifacts and their dependencies (metadata), Xray needs to concurrently manage many open files. The default maximum number of files that can be opened concurrently on Linux systems is usually too low for the indexing process and can therefore cause a performance bottleneck. For optimal performance, we recommend increasing the number of files that can be opened concurrently to 100,000 (or the maximum your system can handle) by following the steps below.
Use the following command to determine the current file handle allocation limit:
cat /proc/sys/fs/file-max
Then, set the following parameters in your /etc/security/limits.conf file to the lower of 100,000 or the file handle allocation limit determined above.
The example shows how the relevant parameters in the /etc/security/limits.conf file are set to 100000. The actual setting for your installation may be different depending file handle allocation limit in your system.
root hard nofile 100000 root soft nofile 100000 xray hard nofile 100000 xray soft nofile 100000 postgres hard nofile 100000 postgres soft nofile 100000
6 Comments
Yossi Shaul
system requirements are not up-to-date with the latest ports. see this - https://docs.google.com/document/d/1RVZZm9X6bYDKbUDyRR4-uFqFYQfDn1oDz61NZjeKYis/edit#heading=h.9446og9erz4k. I think we should also specify which ports we need to expose and which are internal. Also what is gRPC
Adi Atzmony
Yossi Shaul there are some ports that are missing. Should I list all ports that are in the google doc in the documentation?
Yossi Shaul
Java 11 is now required. The instructions on how to configure are also different and described here and here
Unknown User (ofira)
For Xray - I'm missing sizing based on the amount of new artifacts/builds a day as well as directions for initial onboarding - in order to know how to support a large scale.
Also - needed info for the case HA is needed.
The fact that the DBs are external - what is supported and what is not.
Unknown User (ofira)
One more question - is it for the Unified? If so, more changes are needed in this page.
Unknown User (arturoa)
I am not sure what the "Ports" section is really telling me. Are those all the ports being used? Are they ports I need to open and if so, open it them up to everyone or just between the microservices or between HA nodes. The router port is also missing from all the products other than Artifactory.