Error Caused by too Many Headers from Elasticsearch/OpenSearch #589
Conversation
This file contains 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
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.
Since the last update I get the following error quite often:
ERROR:cli.py:134:Elasticsearch Error: Elasticsearch's search for existing report error: ConnectionError(('Connection aborted.', HTTPException('got more than 100 headers'))) caused by: ProtocolError(('Connection aborted.', HTTPException('got more than 100 headers')))Googling around reveals that this some kind of issue in the Python http where you cannot set the maximum allowed headers. Elasticsearch (OpenSearch in my case) seems to send more than the default 100 headers. Since this change the error does no longer occur in my Docker Compose deployment.