Skip to content

Fix OOM caused by big max_nodes parameter #2281

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 21, 2023
Merged

Conversation

kolesnikovae
Copy link
Collaborator

Resolves #2280

@kolesnikovae kolesnikovae added type/bug Something isn't working backend Mostly go code labels Aug 19, 2023
@kolesnikovae kolesnikovae marked this pull request as ready for review August 19, 2023 05:56
@kolesnikovae kolesnikovae requested a review from a team as a code owner August 19, 2023 05:56
@kolesnikovae kolesnikovae merged commit 3d25aa2 into next Aug 21, 2023
@kolesnikovae kolesnikovae deleted the fix/max-nodes-oom branch August 21, 2023 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Mostly go code type/bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Specifying huge "max nodes" value, consumes a lot of memory
2 participants