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
| Process name | Run user | Log prefix |
|---|---|---|
authentication_server | irisadmin | AuthenticationServer |
db_acl_write_server | irisadmin | DbAclWriteServer |
db_tdcp | dbquery | TableDataCacheProxy |
configuration_server | irisadmin | ConfigurationServer |
iris_controller | irisadmin | PersistentQueryController |
log_aggregator_service | irisadmin | LogAggregatorService |
tailer1 | irisadmin | LogtailerMain |
db_dis | dbmerge | DataImportServer |
db_merge_server | dbmerge | RemoteQueryDispatcher |
db_ltds | dbquery | LocalTableDataServer |
db_query_server | dbquery | RemoteQueryDispatcher |
web_api_service | dbquery | WebServer |
Deephaven also depends on the following third-party processes:
| Process | Run user | Executable |
|---|---|---|
MariaDB | mysql | /usr/libexec/mysqld |
Third-party components
Deephaven relies on several third-party components — for example, Monit is covered in Starting and stopping Deephaven services. These components are installed as prerequisites before Deephaven installation. See the installation guide for the full list of dependencies.
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. If basic checks and restarts do not resolve an incident, contact the Deephaven Support Team.