Skip to content

Elastic stack: use elasticsearch.yml config #554

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 3 commits into from
Oct 27, 2021

Conversation

mtojek
Copy link
Contributor

@mtojek mtojek commented Oct 26, 2021

Issue: #552

This PR introduces a dedicated YML config for Elasticsearch. With this change we'll be able to introduce breaking config changes and not harm end-users.

@mtojek mtojek self-assigned this Oct 26, 2021
@elasticmachine
Copy link
Collaborator

elasticmachine commented Oct 26, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-10-27T07:03:51.390+0000

  • Duration: 35 min 53 sec

  • Commit: c0d4cfd

Test stats 🧪

Test Results
Failed 0
Passed 438
Skipped 4
Total 442

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

Comment on lines 11 to 15
script.max_compilations_rate: "use-context"
script.context.template.max_compilations_rate: "unlimited"
script.context.ingest.cache_max_size: 2000
script.context.processor_conditional.cache_max_size: 2000
script.context.template.cache_max_size: 2000
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@P1llus I'm working on forking the Elasticsearch config for 8.x. Do you know how these script.* settings should look like?

Copy link
Member

Choose a reason for hiding this comment

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

@mtojek they can all be removed actually, they should not be needed anymore. We should monitor for any flakiness, but except that it is actually better to run on the newer better default settings

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, removed!

@mtojek mtojek requested a review from P1llus October 26, 2021 17:20
@mtojek
Copy link
Contributor Author

mtojek commented Oct 27, 2021

/test

@mtojek mtojek requested a review from jsoriano October 27, 2021 06:55
@mtojek mtojek marked this pull request as ready for review October 27, 2021 06:55
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.

4 participants