elasticapm/transport: specific shutdown handling for http transport#2085
Merged
xrmx merged 2 commits intoelastic:mainfrom Jul 26, 2024
Merged
elasticapm/transport: specific shutdown handling for http transport#2085xrmx merged 2 commits intoelastic:mainfrom
xrmx merged 2 commits intoelastic:mainfrom
Conversation
basepi
previously approved these changes
Jul 18, 2024
568c0ba to
20d51c0
Compare
basepi
previously approved these changes
Jul 19, 2024
Member
Author
|
It looks like the tests that replicates the submission timeout is flaky on windows: |
Contributor
Honestly, I've been extremely tempted to remove our windows support entirely. I don't think anyone uses it, and the majority of our flakey tests have been on windows. (You can easily search for some of our other tests we skip on windows due to flakiness.) |
20d51c0 to
08136b4
Compare
xrmx
commented
Jul 24, 2024
We have a race condition at http transport shutdown where our atexit handler is racing against urllib3 ConnectionPool weakref finalizer. Having the urllib3 finalizer called before atexit would lead to have our thread hang waiting for send any eventual queued data via urllib3 pools that are closed. Force the creation of a new PoolManager so that we are always able to flush.
08136b4 to
25c4f9e
Compare
Member
Author
This time the problem was the test itself :) |
basepi
approved these changes
Jul 25, 2024
xrmx
added a commit
to xrmx/apm-agent-python
that referenced
this pull request
Aug 19, 2024
…lastic#2085) We have a race condition at http transport shutdown where our atexit handler is racing against urllib3 ConnectionPool weakref finalizer. Having the urllib3 finalizer called before atexit would lead to have our thread hang waiting for send any eventual queued data via urllib3 pools that are closed. Force the creation of a new PoolManager so that we are always able to flush.
xrmx
added a commit
that referenced
this pull request
Aug 19, 2024
…2085) We have a race condition at http transport shutdown where our atexit handler is racing against urllib3 ConnectionPool weakref finalizer. Having the urllib3 finalizer called before atexit would lead to have our thread hang waiting for send any eventual queued data via urllib3 pools that are closed. Force the creation of a new PoolManager so that we are always able to flush.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this pull request do?
We have a race condition at http transport shutdown where our atexit handler is racing against urllib3 ConnectionPool weakref finalizer. Having the urllib3 finalizer called before atexit would lead to have our thread hang waiting for send any eventual queued data via urllib3 pools that are closed.
Force the creation of a new PoolManager so that we are always able to flush.
Related issues
Closes #1975