Skip to content

Introduce memory usage estimation mode in data_frame_analyzer #584

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 6 commits into from
Aug 7, 2019

Conversation

przemekwitek
Copy link
Contributor

@przemekwitek przemekwitek commented Aug 2, 2019

Introduce a mode in which data_frame_analyzer binary only outputs memory usage estimations but does not perform any analysis. This mode will be used by the new endpoint in Java server.

Relates elastic/elasticsearch#44699

@przemekwitek przemekwitek force-pushed the model_memory_limit branch 4 times, most recently from 1a97d9c to 978a6b4 Compare August 6, 2019 10:23
Copy link
Contributor

@tveasey tveasey left a comment

Choose a reason for hiding this comment

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

I did a quick pass through. Looking pretty good. I know you're working on tests. I've made a couple of suggestions which might have some knock on effects for testing, so thought I'd just go ahead and submit these.

…ory estimations but does not perform any analysis
@przemekwitek
Copy link
Contributor Author

I did a quick pass through. Looking pretty good. I know you're working on tests. I've made a couple of suggestions which might have some knock on effects for testing, so thought I'd just go ahead and submit these.

Thanks. I've just sent this PR to regular review and will address your comments shortly.

@przemekwitek przemekwitek marked this pull request as ready for review August 6, 2019 11:08
Copy link
Contributor

@tveasey tveasey left a comment

Choose a reason for hiding this comment

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

Good stuff! This looks good to go. Just a couple of comment typos and a suggestion. Also, I propose we use the usual error handling mechanism for dealing with the case that the runner is null. I'm going to go ahead and approve because I don't think this needs any further reviews.

Copy link
Contributor

@droberts195 droberts195 left a comment

Choose a reason for hiding this comment

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

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.

3 participants