Skip to content

Update scaling documentation #7177

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

Merged
merged 2 commits into from
Oct 20, 2021
Merged

Update scaling documentation #7177

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f8ca2f6
Update scaling documentation
benmoriceau Oct 19, 2021
6d31b0c
RM unvated changes
benmoriceau Oct 19, 2021
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
9 changes: 9 additions & 0 deletions docs/operator-guides/scaling-airbyte.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,15 @@ To be safe, make sure the Kubernetes cluster can schedule up to `2 x <number-of-

This is a **non-issue** for users running Airbyte Docker.

### Temporal DB
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 150 max column has been applied in this review. The relevant changes is here only. I will try to remove the un-relevant changes.


Temporal maintains multiple idle connexions. By the default value is `20` and you may want to lower or increase this number. One issue we noticed is
that temporal creates multiple pools and the number specified in the `SQL_MAX_IDLE_CONNS` environment variable of the `docker.compose.yaml` file
might end up allowing 4-5 times more connexions than expected.

If you want tho increase the amount of allowed idle connexion, you will also need to increase `SQL_MAX_CONNS` as well because `SQL_MAX_IDLE_CONNS`
is capped by `SQL_MAX_CONNS`.

## Feedback

The advice here is best-effort and by no means comprehensive. Please reach out on Slack if anything doesn't make sense or if something can be improved.
Expand Down