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.

Sign up for GitHub

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

Jump to bottom

[ML] Introduce a "starting" datafeed state for lazy jobs #53918

Merged
merged 5 commits into from
Mar 24, 2020
Merged

[ML] Introduce a "starting" datafeed state for lazy jobs #53918

merged 5 commits into from
Mar 24, 2020

Commits on Mar 21, 2020

  1. [ML] Introduce a "starting" datafeed state for lazy jobs 

    It is possible for ML jobs to open lazily if the "allow_lazy_open"
option in the job config is set to true.  Such jobs wait in the
"opening" state until a node has sufficient capacity to run them.

This commit fixes the bug that prevented datafeeds for jobs lazily
waiting assignment from being started.  The state of such datafeeds
is "starting", and they can be stopped by the stop datafeed API
while in this state with or without force.

Relates elastic#53763
    @droberts195
    droberts195 committed Mar 21, 2020
    Configuration menu
    Copy the full SHA
    c386dc2 View commit details
    Browse the repository at this point in the history

  2. Lazy open/start needs to return true for UI

    @droberts195
    droberts195 committed Mar 21, 2020
    Configuration menu
    Copy the full SHA
    a08fda3 View commit details
    Browse the repository at this point in the history

Commits on Mar 23, 2020

  1. Adjust test result

    @droberts195
    droberts195 committed Mar 23, 2020
    Configuration menu
    Copy the full SHA
    23e48cf View commit details
    Browse the repository at this point in the history

  2. Revert test response format change

    @droberts195
    droberts195 committed Mar 23, 2020
    Configuration menu
    Copy the full SHA
    e31bea9 View commit details
    Browse the repository at this point in the history

  3. opened is now pointless as it's just the inverse of shouldCancel

    @droberts195
    droberts195 committed Mar 23, 2020
    Configuration menu
    Copy the full SHA
    85e5fbc View commit details
    Browse the repository at this point in the history