Skip to content

Conversation

@benwtrent
Copy link
Member

We already search for the previously stored progress document.

For optimization purposes, and to prevent restoring the same
progress after a failed analytics job is stopped,
this commit does an equality check between the previously stored progress and current progress
If the progress has changed, persistence continues as normal.

closes #61913

@benwtrent benwtrent added >non-issue >test Issues or PRs that are addressing/adding tests :ml Machine learning v8.0.0 v7.10.0 labels Sep 8, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

We already search for the previously stored progress document.

For optimization purposes, and to prevent restoring the same
progress after a failed analytics job is stopped,
this commit does an equality check between the previously stored progress and current progress
If the progress has changed, persistence continues as normal.
@benwtrent benwtrent force-pushed the feature/ml-analytics-progress-persistence-optimization branch from 6d8d136 to 6dc2c7b Compare September 8, 2020 17:18
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 c8707ea into elastic:master Sep 9, 2020
@benwtrent benwtrent deleted the feature/ml-analytics-progress-persistence-optimization branch September 9, 2020 15:50
benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Sep 9, 2020
* [ML] only persist progress if it has changed

We already search for the previously stored progress document.

For optimization purposes, and to prevent restoring the same
progress after a failed analytics job is stopped,
this commit does an equality check between the previously stored progress and current progress
If the progress has changed, persistence continues as normal.
benwtrent added a commit that referenced this pull request Sep 9, 2020
* [ML] only persist progress if it has changed

We already search for the previously stored progress document.

For optimization purposes, and to prevent restoring the same
progress after a failed analytics job is stopped,
this commit does an equality check between the previously stored progress and current progress
If the progress has changed, persistence continues as normal.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:ml Machine learning >non-issue >test Issues or PRs that are addressing/adding tests v7.10.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ClassificationIT.testTooLowConfiguredMemoryStillStarts fails on CI

4 participants