For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Welcome
    • Overview
    • Release Notes
  • Installation and Configuration
    • System Requirements
    • Installation
    • Services and Utilities
    • Executor Resource Manager
    • Configuration Parameters
      • Parameters Overview
      • Configuration Parameters for HeavyDB
      • Configuration Parameters for HEAVY.AI Web Server
      • Configuration Parameters for HeavyIQ
    • Security
    • Distributed Configuration
  • Loading and Exporting Data
    • Supported Data Sources
    • Command Line
  • SQL
    • Data Definition (DDL)
    • Data Manipulation (DML)
  • HeavyImmerse
    • Introduction to HeavyImmerse
    • Admin Portal
    • Control Panel
    • Working with Dashboards
    • Measures and Dimensions
    • Using Parameters
    • Using Filters
    • Using Cross-link
    • Color Consistency
    • Chart Animation
    • Multilayer Charts
    • SQL Editor
    • Customization
    • Joins (Beta)
    • Chart Types
    • Deprecated Charts
    • HeavyIQ SQL Notebook
  • HeavyIQ Conversational Analytics
    • HeavyIQ Overview
    • HeavyIQ Model Overview (HeavyLM)
  • HeavyRF
    • Introduction to HeavyRF
    • Getting Started
    • HeavyRF Table Functions
  • HeavyConnect
    • HeavyConnect Release Overview
    • Getting Started
    • Best Practices
    • Examples
    • Command Reference
    • Parquet Data Wrapper Reference
    • ODBC Data Wrapper Reference
    • Raster Data Wrapper Reference
  • HeavyML (BETA)
    • HeavyML Overview
    • Clustering Algorithms
    • Regression Algorithms
    • Principal Components Analysis
  • Python / Data Science
    • Data Science Foundation
    • JupyterLab Installation and Configuration
    • Using HEAVY.AI with JupyterLab
    • Python User-Defined Functions (UDFs) with RBC
    • Ibis
    • Interactive Data Exploration with Altair
    • Additional Examples
  • APIs and Interfaces
    • heavysql
    • Thrift
    • JDBC
    • ODBC
    • Vega
    • RJDBC
    • SQuirreL SQL
    • heavyai-connector
  • Tutorials and Demos
    • Loading Data
    • Using Heavy Immerse
    • Hello World
    • Creating a Kafka Streaming Application
    • Getting Started with Open Source
    • Try Vega
  • Troubleshooting and Special Topics
    • Vulkan Renderer
    • Optimizing
    • Known Issues and Limitations
    • Logs and Monitoring
    • Archived Release Notes
NVIDIANVIDIA
Developer-friendly docs for your API
Privacy Policy | Your Privacy Choices | Terms of Service | Accessibility | Corporate Policies | Product Security | Contact

Copyright © 2026, NVIDIA Corporation.

LogoLogoDocumentation
On this page
  • Storage Directory
  • Configuring a Custom Heavy Immerse Subdirectory
  • Configuration File
Installation and ConfigurationConfiguration Parameters

Overview

||View as Markdown|
Previous

Configuration Parameters

Next

Configuration Parameters for HeavyDB

HEAVY.AI has minimal configuration requirements with a number of additional configuration options. This topic describes the required and optional configuration changes you can use in your HEAVY.AI instance.

In release 4.5.0 and higher, HEAVY.AI requires that all configuration flags used at startup match a flag on the HEAVY.AI server. If any flag is misspelled or invalid, the server does not start. This helps ensure that all settings are intentional and will not have an unexpected impact on performance or data integrity.

Storage Directory

Before starting the HEAVY.AI server, you must initialize the persistent storage directory. To do so, create an empty directory at the desired path, such as /var/lib/heavyai.

  1. Create the environment variable $HEAVYAI_BASE.
1export HEAVYAI_BASE=/var/lib/heavyai
  1. Then, change the owner of the directory to the user that the server will run as ($HEAVYAI_USER):
sudo mkdir -p $HEAVYAI_BASE sudo chown -R $HEAVYAI_USER $HEAVYAI_BASE

where HEAVYAI_USERisthesystemuseraccountthattheserverrunsas,suchas‘heavyai‘,andHEAVYAI\_USER is the system user account that the server runs as, such as `heavyai`, and HEAVYAI_USERisthesystemuseraccountthattheserverrunsas,suchas‘heavyai‘,andHEAVYAI_BASE is the path to the parent of the HEAVY.AI server storage directory.

  1. Run $HEAVYAI_PATH/bin/initheavy with the storage directory path as the argument:
$HEAVYAI_PATH/bin/initheavy $HEAVYAI_BASE/storage

Configuring a Custom Heavy Immerse Subdirectory

Immerse serves the application from the root path (/) by default. To serve the application from a sub-path, you must modify the $HEAVYAI_PATH/frontend/app-config.js file to change the IMMERSE_PATH_PREFIX value. The Heavy Immerse path must start with a forward slash (/).

Configuration File

The configuration file stores runtime options for your HEAVY.AI servers. You can use the file to change the default behavior.

The heavy.conf file is stored in the $HEAVYAI_BASE directory. The configuration settings are picked up automatically by the sudo systemctl start heavydb and sudo systemctl start heavy_web_server commands.

Set the flags in the configuration file using the format <flag> = <value>. Strings must be enclosed in quotes.

The following is a sample configuration file. The entry for data path is a string and must be in quotes. The last entry in the first section, for null-div-by-zero, is the Boolean value true and does not require quotes.

$port = 6274
$http-port = 6278
$data = "/var/lib/heavyai/storage"
$null-div-by-zero = true
$
$[web]
$port = 6273
$frontend = "/opt/heavyai/frontend"
$servers-json = "/var/lib/heavyai/servers.json"
$enable-https = true

To comment out a line in heavy.conf, prepend the line with the pound sign (#) character.

For encrypted backend connections, if you do not use a configuration file to start the database, Calcite expects passwords to be supplied through the command line, and calcite passwords will be visible in the processes table. If a configuration file is supplied, then passwords must be supplied in the file. If they are not, Calcite will fail.