Operations guide
This guide covers routine procedures and operations for Deephaven system administrators managing bare-metal and Podman Enterprise deployments. For Kubernetes deployments, see the Kubernetes documentation.
A production Deephaven system comprises three categories of components:
- Network — IP subnets and associated services (DNS, NTP).
- Storage — Intraday data on high-speed local SSD volumes; historical data on NFS mounts from a highly available storage system.
- Application — Deephaven processes deployed across multiple x86_64 (64-bit) Linux nodes.
For more details on deployment architecture, see Scaling to Multiple Servers.
Deephaven services
For service descriptions, dependencies, and management procedures, see Process management. For system architecture, see Architecture overview.
The following table maps process names to their application log file prefixes. Log directories vary by service; see Application log files for location details:
| Process name | Run user | Log prefix |
|---|---|---|
configuration_server | irisadmin | ConfigurationServer |
authentication_server | irisadmin | AuthenticationServer |
iris_controller | irisadmin | PersistentQueryController |
db_query_server | dbquery | RemoteQueryDispatcher |
db_merge_server | dbmerge | RemoteQueryDispatcher |
web_api_service | dbquery | WebServer |
db_dis | dbmerge | DataImportServer |
log_aggregator_service | irisadmin | LogAggregatorService |
tailer1 | irisadmin | LogtailerMain |
db_tdcp | dbquery | TableDataCacheProxy |
db_ltds | dbquery | LocalTableDataServer |
db_acl_write_server | irisadmin | DbAclWriteServer |
Third-party components
Deephaven relies on several third-party components, including Monit. Legacy deployments may also use MariaDB, which is optional and replaced by etcd in modern deployments. See the installation guide for the dependencies for your deployment and Starting and stopping Deephaven services for Monit usage.
License agreements, maintenance, troubleshooting, and runbooks for third-party components are in their respective upstream documentation.
Troubleshooting
Deephaven is fault-tolerant and designed to retry or restart components automatically. When intervention is required, start with basic checks: network connectivity, firewall rules, configuration file settings, file permissions. For CORS errors when using DNS aliases or embedding the Web IDE, see CORS configuration. If basic checks and restarts do not resolve an incident, contact the Deephaven Support Team.