Skip to content

Make sure we explicitly specify Xms and Mmx to 1g #34

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
Feb 16, 2021

Conversation

Mpdreamz
Copy link
Member

@Mpdreamz Mpdreamz commented Feb 16, 2021

As of:

elastic/elasticsearch#65905

The default is dynamic and defaults to 4g on data nodes.
I finally had one too many IDE open to this becomming a problem on my
32gig laptop :)

As of:

elastic/elasticsearch#65905

The default is dynamic and defaults to 4g on data nodes.
I finally had one too many IDE open to this becomming a problem on my
32gig laptop :)
@Mpdreamz Mpdreamz merged commit fb0d994 into master Feb 16, 2021
@Mpdreamz Mpdreamz deleted the feature/constrain-memory branch February 16, 2021 20:13
@Mpdreamz
Copy link
Member Author

@stevejgordon self reviewed this because I need this to generate a new specification tests update and this is blocking me.

Releasing this under 0.2.5

@stevejgordon
Copy link
Contributor

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants