> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Availability

> availability

ReferenceApplies to: Unified engine deployments

`[availability]`

## Settings

### `startup`

Chooses whether this process starts serving immediately or waits for a separate system to activate it.

* **Default:** `"Active"`
* **Type:** choice: `Active`, `Standby`

> **Example**
>
> `"Active"` starts normal initialization. `"Standby"` waits for promotion before opening the service databases, so an external coordinator can decide which controller becomes active.

### `control_listen`

Opens a separate address for health checks and commands that activate or drain this process.

* **Default:** Unset
* **Type:** string; optional

> **Example**
>
> `"0.0.0.0:50064"` lets a management system reach `/readyz` on port 50064, even while the main services are still starting. It does not change the SQL or UI address.

### `control_token_environment`

Names the environment variable that contains the token required to activate or drain the process.

* **Default:** Unset
* **Type:** string; optional

> **Example**
>
> Set the name to `"LAMINAR_CONTROL_TOKEN"` and supply a token of at least 32 bytes in that environment variable. The setting contains the variable name, not the token itself.

### `ownership_check_interval`

Sets how often the process checks that it still owns the databases it is writing to.

* **Default:** `1 s`
* **Type:** duration

> **Example**
>
> `{ secs = 1, nanos = 0 }` checks once per second. This helps a process notice when it has lost database ownership; it does not elect a new controller.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.