Skip to content

Conversation

@sopel39
Copy link
Member

@sopel39 sopel39 commented Jun 3, 2025

softMemoryLimit was previously required. However, it's often unclear for the users what is the implication of setting the limit and it doesn't work well will revocable memory and spilled queries.

This PR makes softMemoryLimit optional and allows to manage query concurrency within query classes (e.g. small, medium, large) which greatly simplifies cluster management.

Description

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## General
* Make soft memory limit optional in resource groups. ({issue}`issuenumber`)

softMemoryLimit was previously required. However, it's often
unclear for the users what is the implication of setting the limit
and it doesn't work well will revocable memory and spilled queries.

This PR makes softMemoryLimit optional and allows to manage
query concurrency within query classes (e.g. small, medium, large)
which greatly simplifies cluster management.
@sopel39 sopel39 requested a review from raunaqmorarka June 3, 2025 14:00
@cla-bot cla-bot bot added the cla-signed label Jun 3, 2025
@github-actions github-actions bot added the docs label Jun 3, 2025
@sopel39 sopel39 merged commit 9067c4a into trinodb:master Jun 4, 2025
39 of 41 checks passed
@sopel39 sopel39 deleted the ks/soft_mem_limit_optional branch June 4, 2025 09:43
@github-actions github-actions bot added this to the 476 milestone Jun 4, 2025
@sopel39 sopel39 mentioned this pull request Jun 10, 2025
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants