Make the ClickHouse connection limit configurable

Open Beginner friendly
#4,491 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
clickhouse, typescript
Domain
backend, databases

Research direction

Start at the @clickhouse/client initialization and the existing environment-setting entry point. Verify that the optional setting accepts only positive integers and is passed as max_open_connections when present. Done means the client default remains unchanged when unset and the per-instance pool behavior is documented.

Written by the indexing model from the issue text.

Description

Problem

Umami uses @clickhouse/client's default limit of 10 open connections per server instance. At higher ingestion rates, that fixed pool can become a bottleneck even when ClickHouse has available capacity.

Proposed behavior

Add an optional positive-integer CLICKHOUSE_MAX_OPEN_CONNECTIONS setting and pass it as max_open_connections. Keep the client default when unset, and document that each Umami instance has its own pool.

AI assistance disclosure: This issue and the proposed implementation were prepared with AI assistance and reviewed by Arthur Braga Alfredo.

Dominant language
TypeScript
Stars
38.9k
Forks
8.1k
Avg merge
5d 19h
Merged PRs (30d)
21

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from umami-software/umami

All issues in umami-software/umami

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.