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

Increase max cache size for scripts to try to stabilize Zeek tests #16390

Merged
merged 4 commits into from
Feb 19, 2020

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Feb 18, 2020

What does this PR do?

Increase max size of cache scripts to avoid recompilations in filebeat tests.

Why is it important?

Zeek tests are quite flaky since some time ago, the pipeline fails with:

[script] Too many dynamic script compilations within, max: [2000/1m]; please use indexed, or scripts with parameters instead; this limit can be changed by the [script.max_compilations_rate] setting

@jsoriano jsoriano added review flaky-test Unstable or unreliable test cases. Team:SIEM Team:Integrations Label for the Integrations team labels Feb 18, 2020
@jsoriano jsoriano self-assigned this Feb 18, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem (Team:SIEM)

@jsoriano jsoriano added needs_backport PR is waiting to be backported to other branches. v7.7.0 labels Feb 18, 2020
@andrewkroh
Copy link
Member

You can probably also increase the cache size to help. The cache size is 100 so it might be thrashing. Relates to #14236.

@jsoriano
Copy link
Member Author

You can probably also increase the cache size to help. The cache size is 100 so it might be thrashing. Relates to #14236.

Ok, trying this, thanks!

@jsoriano
Copy link
Member Author

jenkins, test this again please

1 similar comment
@jsoriano
Copy link
Member Author

jenkins, test this again please

@jsoriano jsoriano changed the title Increase max compilations rate to try to stabilize Zeek tests Increase max cache size for scripts to try to stabilize Zeek tests Feb 19, 2020
@jsoriano
Copy link
Member Author

jsoriano commented Feb 19, 2020

jenkins, test this again please (builds were interrupted)

@jsoriano
Copy link
Member Author

@andrewkroh it seems that increasing the cache size actually works, tests with zeek files are not failing now. Thanks for the suggestion!

@jsoriano
Copy link
Member Author

jenkins, test this again, one last time

@jsoriano jsoriano merged commit 742e9e6 into elastic:master Feb 19, 2020
@jsoriano jsoriano deleted the zeek-compilation-rate branch February 19, 2020 16:42
jsoriano added a commit to jsoriano/beats that referenced this pull request Feb 19, 2020
…lastic#16390)

Some filebeat tests were frequently failing due to "Too many
dynamic script compilations". Try to reduce number of
compilations by increasing the max size of scripts cache.

(cherry picked from commit 742e9e6)
@jsoriano jsoriano removed the needs_backport PR is waiting to be backported to other branches. label Feb 19, 2020
jsoriano added a commit that referenced this pull request Feb 20, 2020
…16390) (#16429)

Some filebeat tests were frequently failing due to "Too many
dynamic script compilations". Try to reduce number of
compilations by increasing the max size of scripts cache.

(cherry picked from commit 742e9e6)
kvch pushed a commit to kvch/beats that referenced this pull request Feb 20, 2020
…lastic#16390)

Some filebeat tests were frequently failing due to "Too many
dynamic script compilations". Try to reduce number of
compilations by increasing the max size of scripts cache.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flaky-test Unstable or unreliable test cases. review Team:Integrations Label for the Integrations team v7.7.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants