[ML] Correct restart from failure when fine tuning classification and regression models #2251
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Fixes elastic/elasticsearch#85536. |
…toring hyperparameters
benwtrent
added a commit
to elastic/elasticsearch
that referenced
this pull request
Apr 1, 2022
ml-cpp build containing fix elastic/ml-cpp#2251 has been uploaded. enabling tests again. closes #85536
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, we would enter fine tuning loop even if we exited early in the event of restart from failover. This adds state to record early exit so we pick up correctly. Also, to monitor progress correctly we need to always start progress monitoring for final train, independent of whether we're training using a hold set or cross-validation.