.jvmopts: Remove MaxMetaspaceSize setting #10020
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liufengyun
approved these changes
Oct 16, 2020
The default on Java >= 8 is infinite metaspace, by introducing an arbitrary limit we risk running out of metaspace (this might explain some weird recent CI failures).
smarter
force-pushed
the
remove-maxmetaspacesize
branch
from
64b4965 to
538e194
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default on Java >= 8 is infinite metaspace, by introducing an
arbitrary limit we risk running out of metaspace (this might explain
some weird recent CI failures).