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

fix: stop recreating http transports on each info request #260

Merged
merged 1 commit into from
Aug 1, 2022

Conversation

kruskall
Copy link
Member

@kruskall kruskall commented Aug 1, 2022

http transports should be reused as per documentation. Recreating the
reverse proxy and the transport on each request is also preventing
connection resuse.

http transports should be reused as per documentation. Recreating the
reverse proxy and the transport on each request is also preventing
connection resuse.
@github-actions github-actions bot added the aws-λ-extension AWS Lambda Extension label Aug 1, 2022
@apmmachine
Copy link

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-08-01T04:43:25.760+0000

  • Duration: 7 min 42 sec

Test stats 🧪

Test Results
Failed 0
Passed 196
Skipped 64
Total 260

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Copy link
Member

@axw axw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!

@kruskall kruskall merged commit 2235448 into elastic:main Aug 1, 2022
@kruskall kruskall deleted the fix/receiver-transport branch August 1, 2022 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aws-λ-extension AWS Lambda Extension
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants