Skip to main content
Geneva supports various environment variables that start with GENEVA_ to configure advanced behavior and fine-tune system settings.
All GENEVA_ environment variables are optional and have sensible defaults. Only set them if you need to override the default behavior.

Admission Control

Admission control validates cluster resources before starting jobs to prevent failures due to insufficient resources.

Commit and Retry Configuration

Control retry behavior for commits and version conflicts.

Lance Retry Configuration

This section configures retry logic for Lance I/O operations. Retries occur on OSError, ValueError, and RuntimeError("Too many concurrent writers") exceptions, and are retried with exponential backoff with jitter.

Checkpoint Storage

Checkpoint storage configuration is experimental. The environment variable names and behavior may change in a future release.
Configure where Geneva stores checkpoint data during job execution. Checkpoints enable fault-tolerant processing by saving intermediate results so that failed jobs can resume without reprocessing completed work. By default, Geneva stores checkpoints in a _ckp/ subdirectory inside the table’s own storage location. This means checkpoints share the same bucket and IOPS budget as the table data. You can override this to store checkpoints in a separate location.
This variable maps to the config path job.checkpoint.object_store.path. It can also be set via config files in .config/ or pyproject.toml under the [geneva] section.

Why use a separate checkpoint path?

At scale, checkpoint I/O and data I/O compete for the same object store IOPS budget when they share a bucket prefix. Setting JOB__CHECKPOINT__OBJECT_STORE__PATH to a different bucket or prefix decouples checkpoint I/O from data I/O, giving each its own IOPS budget and preventing shared-prefix rate limiting.
Equivalent programmatic configuration:

Other Configuration