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

[7.15] Execute EnrichPolicyRunner on a non dedicated master node. #77165

Merged
merged 2 commits into from
Sep 2, 2021

Commits on Sep 2, 2021

  1. Execute EnrichPolicyRunner on a non dedicated master node.

    Backporting elastic#76881 to 7.15 branch.
    
    Introduce an internal action that the execute policy action delegates to.
    This to ensure that the actual policy execution is never executed on the elected master node
    or dedicated master nodes. In case the cluster consists out of a single node then
    the internal action will attempt to execute on the current/local node.
    
    The actual enrich policy execution is encapsulated in the `EnrichPolicyRunner` class.
    This class manages the execution of several API calls, so this itself isn't doing anything heavy.
    However the coordination of these api calls (in particular the reindex api call) may involve
    some non-neglectable work/overhead and this shouldn't be performed on the elected master
    or any other dedicated master node.
    
    Closes elastic#70436
    martijnvg committed Sep 2, 2021
    Configuration menu
    Copy the full SHA
    a76f615 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    ee4c48d View commit details
    Browse the repository at this point in the history