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

Cherry-pick #8845 to 6.x: add_cloud_metadata asynchronous initialization #10495

Merged
merged 1 commit into from
Feb 4, 2019

Conversation

adriansr
Copy link
Contributor

@adriansr adriansr commented Feb 1, 2019

Cherry-pick of PR #8845 to 6.x branch. Original message:

Now that the add_cloud_metadata is enabled by default in all beats, we are losing 3 precious seconds every time a Beat is started outside a supported cloud environment.

This patch makes the cloud detection an asynchronous task so the Beat can start and only block if initialization is not completed at the time of the first enrichment.

Running in debug mode bypasses this parallelism as the processor needs to be initialized when its String() method is called.

Now that the add_cloud_metadata is enabled by default in all beats, we
are losing 3 precious seconds every time a Beat is started outside a
supported cloud environment.

This patch makes the cloud detection an asynchronous task so the Beat
can start and only block if initialization is not completed at the time
of the first enrichment.

Running in debug mode bypasses this parallelism as the processor needs
to be initialized when its String() method is called.

(cherry picked from commit 737a0b9)
@adriansr
Copy link
Contributor Author

adriansr commented Feb 4, 2019

jenkins, test this

@adriansr adriansr merged commit 1640308 into elastic:6.x Feb 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants