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

[DATA-FRAME-ANALYTICS] Add task recovery on node change #39416

Conversation

benwtrent
Copy link
Member

This change is fairly simple (for now) as we don't have any state to really recover. We simply need to check what the previous state was and take some simple actions ahead of time.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core

@@ -100,6 +101,7 @@ task internalClusterTest(type: RandomizedTestingTask,
dependsOn: unitTest.dependsOn) {
include '**/*IT.class'
systemProperty 'es.set.netty.runtime.available.processors', 'false'
systemProperties 'java.security.policy': file("src/main/plugin-metadata/plugin-security-test.policy").absolutePath
Copy link
Member Author

Choose a reason for hiding this comment

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

I needed to add these two lines for the integration tests to run. Apparently, with how the internal cluster is built, the painless plugin is not included, so I included it, and add the requisite java security policy so that it can run.

If there is a better way (or if the tests are deemed unnecessary), then I will happily change this.

*
* @return Set of Strings representing the result fields for the constructed analysis
*/
Set<String> getResultFields();
Copy link
Member Author

Choose a reason for hiding this comment

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

I do think a better solution here is to have some known prefix for our result fields and which analyzer they satisfy.

Something like _ml_analysis_result.<analyzer>.<result-name>. But, that change is more substantial, opted for better planning and refactoring down the line when/if we make that change.

Copy link
Contributor

@dimitris-athanasiou dimitris-athanasiou left a comment

Choose a reason for hiding this comment

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

Looks good! Left a few minor comments.

Copy link
Contributor

@dimitris-athanasiou dimitris-athanasiou left a comment

Choose a reason for hiding this comment

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

LGTM

@benwtrent benwtrent merged commit 9faeb94 into elastic:feature-ml-data-frame-analytics Feb 27, 2019
@benwtrent benwtrent deleted the feature/ml-data-frame-analytics-task-recovery branch February 27, 2019 21:50
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.

5 participants