Environment Variables
Overview
NIXL uses environment variables for runtime configuration. This page documents all recognized variables, grouped by subsystem. Environment variables are read at agent initialization time and cannot be changed after an agent is created.
Variables are organized into the following categories:
- Core — Logging and plug-in discovery that apply to all NIXL deployments
- etcd — Distributed metadata exchange configuration
- Telemetry — Performance monitoring, event collection, and export
- Backend-Specific — Transport-level settings for individual backends (UCX, Libfabric, Mooncake, S3, Azure Blob, GDS)
Boolean environment variables follow the convention: set to y/yes/on/true/enable/1 (case-insensitive) to enable, or n/no/off/false/disable/0 to disable. Presence-check variables are activated by setting them to any value.
Core Variables
These variables control fundamental NIXL behavior across all backends.
etcd Variables
These variables configure NIXL’s distributed metadata exchange via etcd.
For detailed etcd setup and usage, see the Metadata Exchange with etcd guide.
Telemetry Variables
These variables control NIXL’s built-in telemetry collection and export system.
For the full telemetry architecture and usage examples, see the Telemetry Guide.
Backend-Specific Variables
UCX
These variables apply when using the UCX transport backend.
Libfabric
These variables apply when using the Libfabric transport backend.
Additional NIXL_LIBFABRIC_* variables may exist for provider-specific configuration. The Libfabric backend constructs environment variable names dynamically using the NIXL_LIBFABRIC_ prefix followed by an uppercase key name. Consult the Libfabric backend README for provider-specific options.
Mooncake
These variables apply when using the Mooncake transport backend.
S3 / Object Storage
These variables apply when using the S3/Object Storage backend.
The OBJ backend also recognizes standard AWS SDK environment variables for authentication:
Azure Blob Storage
These variables apply when using the Azure Blob Storage backend.
Backend parameters passed to createBackend() take precedence over these environment variables. Supported override keys are account_url, container_name, connection_string, and ca_bundle.
GDS (GPUDirect Storage)
These variables apply when using the GDS backend.
Quick Reference
Set environment variables before launching your NIXL application: