Skip to content
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

[Native] Fix error java.lang.OutOfMemoryError: Compressed class space #21825

Merged
merged 1 commit into from
Jan 31, 2024

Conversation

pramodsatya
Copy link
Contributor

Description

The following error was seen when adding presto native e2e tests for window aggregate functions in #20625 :

[ERROR] java.lang.OutOfMemoryError: Compressed class space
[ERROR] Terminating due to java.lang.OutOfMemoryError: Compressed class space

This error is fixed by increasing the compressed class space size to 3gb in the CircleCI config for linux-presto-e2e-tests.

Test Plan

The CircleCI job linux-presto-e2e-tests was verified to be passing with this fix: https://app.circleci.com/pipelines/github/prestodb/presto/11583/workflows/b23f1755-3811-49fd-844e-748dc2212080/jobs/43847 .

== NO RELEASE NOTE ==

@majetideepak
Copy link
Collaborator

@amitkdutta can you take a look at this change? Looks reasonable to me, but I want to double-check.

@@ -57,8 +57,8 @@ executors:
- image: prestocpp/prestocpp-avx-centos:root-20230613
resource_class: 2xlarge
environment:
MAVEN_OPTS: "-Xmx4G -XX:+ExitOnOutOfMemoryError"
MAVEN_INSTALL_OPTS: "-Xmx2G -XX:+ExitOnOutOfMemoryError"
MAVEN_OPTS: "-Xmx4G -XX:+ExitOnOutOfMemoryError -XX:CompressedClassSpaceSize=3g"
Copy link
Member

Choose a reason for hiding this comment

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

Small recommendation: I see that we are using machine size as 2xlarge (which is 32 GB memory) we can either increase Xmx for both MAVEN_OPTS and MAVEN_FINAL_OPTS or if we don't need such large machines we can plan to shift to smaller resource class probably to save costs.

If there are certain suites that require larger machine size, we can also segregate different suites to use different executors to optimize costs.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for the suggestion @imjalpreet. @majetideepak could you please confirm if I can increase Xmx to 8G in MAVEN_OPTS and MAVEN_FINAL_OPTS in this PR?

Copy link
Collaborator

Choose a reason for hiding this comment

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

We have to remember that Prestissimo workers also run on the same node and they require memory. I would prefer to limit the JVM memory to only the required since we know the memory is held up by the JVM until GC runs which is not in our control.

@pramodsatya pramodsatya merged commit f37e83a into prestodb:master Jan 31, 2024
56 checks passed
@pramodsatya pramodsatya deleted the fix_oom_err branch January 31, 2024 20:15
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.

5 participants