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

Global processor reload #40312

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from
Draft

Conversation

pchila
Copy link
Member

@pchila pchila commented Jul 23, 2024

Proposed commit message

Alternative approach derived from PR #40091 .

To reload the global processor we delay instantiating the Pipeline object similarly to what's done with output: we allow to load using settings from the control protocol exactly once; if more changes come in a restart of the beat is required.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

pchila added 8 commits July 3, 2024 18:50
Delay instantiation of Pipeline object till the first client (input)
tries to connect to it.
The idea is to use a builder object for the Pipeline on which we can set
parameters (in this case the global processor config) until the Pipeline
is instantiated.
Once the Pipeline is instantiated, the global processor reloader will
return a specific error, signaling that to reload configuration we need
a new Pipeline (i.e. a beat restart).
At this point in the code the reload and restart seem to work, however
it seems that the output unit is not set correctly (we probably need
some additional hook to correctly wire the Pipeline and the Output
object
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 23, 2024
@mergify mergify bot assigned pchila Jul 23, 2024
Copy link
Contributor

mergify bot commented Jul 23, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @pchila? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@pchila pchila added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Jul 23, 2024
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant