bugfix(exporter): ensure response is closed

[codeboten]

Description

I was experiencing connection aborted when using the OTLP exporters to emit metrics. After reading the documentation for the requests library, it appears that if the body is not read, it is not necessarily returned to the connection pool.

Fix #4476

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manually tested to validate that the connection aborted errors no longer happen.

Does This PR Require a Contrib Repo Change?

• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[xrmx]

The metrics failure looks like a double close or something in case the response is a 200?

[codeboten]

Turns out the Response() constructor doesn't set a raw property on the response object which was causing the failures. I added a check for the property to exist, but in my manual testing that was not an issue.

[xrmx]

Do you know if moving this right after getting resp will make resp.ok and self._retryable(resp) change behavior? If not would be nice to do this just once.

[xrmx]

From a quick test it looks like it should be fine

[codeboten]

thanks for the suggestion, updated the code and tested it locally, seems ok

[codeboten]

After further testing, the problem is caused by the Session object sending a keep-alive to the server and the server eventually deciding to close the connection. It would be possible to avoid this problem by closing the session's connection (via self._session.close()) but that would cause a new connection to be established every time, which seems wasteful.

Instead, I added a try/except around the post, to catch the ConnectionError and try to post another time (which causes the connection to be re-established successfully in this case). PTAL