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 installation docs on monitor configuration #626

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Fix installation docs on monitor configuration #626

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
18c4667
Fix installation docs by replacing monitorConfiguration with monitor
ricardocardante Feb 19, 2025
9cc9141
Fix explicitPrepare description
ricardocardante Feb 20, 2025
0210c75
Move section L440-L444 to the section above(L430)
ricardocardante Feb 20, 2025
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
20 changes: 10 additions & 10 deletions docs/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -401,7 +401,7 @@ are the minimum or maximum values (inclusive) that are considered healthy. By de
the only metric populated is:

```yaml
monitorConfiguration:
monitor:
metricMinimumValues:
trino_metadata_name_DiscoveryNodeManager_ActiveNodeCount: 1
```
Expand All @@ -412,7 +412,7 @@ worker count to 10 and disqualify clusters that have been experiencing frequent
Collections, set

```yaml
monitorConfiguration:
monitor:
metricMinimumValues:
trino_metadata_name_DiscoveryNodeManager_ActiveNodeCount: 10
metricMaximumValues:
Expand All @@ -428,19 +428,19 @@ method of backend clusters. Configure a username and password by adding
`backendState` to your configuration. The username and password must be valid
across all backends.

```yaml
backendState:
username: "user"
password: "password"
```

Trino Gateway uses `explicitPrepare=false` by default. This property was introduced
in Trino 431, and uses a single query for prepared statements, instead of a
`PREPARE/EXECUTE` pair. If you are using the JDBC health check option with older
versions of Trino, set
```yaml
monitorConfiguration:
explicitPrepare: false
```

```yaml
backendState:
username: "user"
password: "password"
monitor:
explicitPrepare: true
```

The query timeout can be set through
Expand Down