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

Allow telemetry devices use jvm.options instead of ES_JAVA_OPTS #28

Merged
merged 2 commits into from
Jun 18, 2019

Conversation

ebadyano
Copy link
Contributor

No description provided.

@ebadyano
Copy link
Contributor Author

Unblocks elastic/rally#711

Copy link
Member

@danielmitterdorfer danielmitterdorfer left a comment

Choose a reason for hiding this comment

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

I left a nit but otherwise LGTM. Thank you! :)

@@ -112,3 +112,10 @@
# due to internationalization enhancements in JDK 9 Elasticsearch need to set the provider to COMPAT otherwise
# time/date parsing will break in an incompatible way for some date patterns and locals
9-:-Djava.locale.providers=COMPAT

{# cluster settings provided by the user via the command line #}
Copy link
Member

Choose a reason for hiding this comment

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

Nit: The comment is not applicable here. I'd probably just get rid of it.

@danielmitterdorfer
Copy link
Member

We should backport this as far as jvm.options are supported (Elasticsearch 5.0.0).

@ebadyano
Copy link
Contributor Author

@danielmitterdorfer Thank you for the review!

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