Configure Memory Settings

This applies to: Visual Data Discovery

Unified service memory configuration recommendations can help you avoid out of memory issues, unpredictable service stability, and memory allocation. We strongly recommend you use the new default for Java: Xms=Xmx. These updated default memory allocations are designed configure your services more effectively for a production load after installation or upgrade.

Symphony v23.2 requires slightly higher memory expectations than previous releases. Upgrading will not overwrite your memory configuration if you’ve already overwritten the default configuration settings.

If you’re upgrading your environment:

  • Review your data source connector usage; stop unused connectors.

  • Review your memory settings based on the chart below.

  7.x / 23.1 Xms/Xmx 23.2 Xms/Xmx
Admin Server 512M/1024M Deprecated
Config Server 512M/1024M Deprecated
Data Writer 128M/256M 512M/512M
EDC * 128M/512M 512M/512M
EDC hdfs/s3 512M/3584M 1500M/1500M
Query Engine 1G/6G 4G/4G
Screenshot Service 128M/1G 750M/750M
Zoomdata Web 1G/2G 4G/4G

To change memory allocation settings for Symphony microservices:

  1. From your terminal, SSH to your Symphony server.

  2. To modify the memory settings for Symphony microservices, you need to edit or create the corresponding .jvm files in /etc/zoomdata/. Perform the following steps:

    vi/etc/zoomdata/<component_name>.jvm

    For complete information on editing configuration files, see Edit a Symphony Configuration File.

  3. Add or update the following line(s) in the corresponding .jvm files.

    Do not allocate more than 85% of your total system memory to all microservices.

    The following example configures the Symphony server to use 20 GB of RAM in the zoomdata.jvm configuration file. You can adjust the number to fit your system's needs. Replace the 20 with the necessary memory allocation for your operating environment. 

    -Xms20g
    -Xmx20g
  4. Save and exit the .jvm file.

  5. Restart the microservice for which you have modified the settings:

    For CentOS 7 Ubuntu 18, 20, or 22:

    sudo systemctl restart <service-name>

Wait a few minutes for the microservice to restart completely, then open a new browser window to log back into Symphony.