Skip to content

catalog pool: keep connections at 1 aggressively #3372

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.

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 1 commit into from
Aug 20, 2025
Merged

Conversation

serprex
Copy link
Member

@serprex serprex commented Aug 20, 2025

No description provided.

@serprex serprex requested a review from iamKunalGupta August 20, 2025 14:38
config.MaxConns = 3
config.MaxConnIdleTime = 5 * time.Minute
config.MaxConnIdleTime = time.Second
Copy link
Contributor

@heavycrystal heavycrystal Aug 20, 2025

Choose a reason for hiding this comment

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

Would this cause a lot of connections "churn"? not sure how often we need a connection on aggregate but if an instance has several mirrors it could be 10+ times a minute

Copy link
Member Author

Choose a reason for hiding this comment

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

those mirrors will generally have non overlapping catalog access

@serprex serprex merged commit d4a6a45 into main Aug 20, 2025
15 of 17 checks passed
@serprex serprex deleted the aggressive-pool branch August 20, 2025 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants