Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Health Checks section in installation readme #567

Merged
merged 1 commit into from
Dec 9, 2024
+12 −3
Merged

Fix Health Checks section in installation readme #567

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions docs/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -318,9 +318,18 @@ reference documentation](https://github.com/trinodb/charts/blob/main/charts/gate

### Health Checks

Trino Gateway checks the health of each backend and **deactivates it if
unhealthy**. A backend that fails a health check must be manually reset to
active. Automatic recovery is not supported.
The Trino Gateway periodically performs health checks and maintains
an in-memory TrinoStatus for each backend. If a backend fails a health check,
it is marked as UNHEALTHY, and the Trino Gateway stops routing requests to it.

It is important to distinguish TrinoStatus from the active/inactive
state of a backend. The active/inactive state indicates whether a backend is
manually turned on or off, whereas TrinoStatus is programmatically determined
by the health check process. Health checks are only performed on backends
that are marked as active.

See [TrinoStatus](routing-rules.md#trinostatus) for more details on
what each Trino status means.

The type of health check is configured by setting

Expand Down