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

Elasticsearch reports too_long_http_line_exception if scrolling through results #320

Closed
Radiergummi opened this issue Aug 24, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@Radiergummi
Copy link
Member

Sometimes when scrolling through a result set, Elasticsearch will throw an Exception such as this:

Elasticsearch\Common\Exceptions\BadRequest400Exception: {"error":{"root_cause":[{"type":"too_long_http_line_exception","reason":"An HTTP line is larger than 4096 bytes."}],"type":"too_long_http_line_exception","reason":"An HTTP line is larger than 4096 bytes."},"status":400}

This can be fixed by passing the scroll ID in the body instead of the URL.

@Radiergummi Radiergummi added the bug Something isn't working label Aug 24, 2023
@Radiergummi Radiergummi self-assigned this Aug 24, 2023
Radiergummi added a commit that referenced this issue Aug 24, 2023
There has been a change in how query parameters are constructed for the Elasticsearch scroll API. We now directly pass the scrollId under the PARAM_BODY key, fixing a bug where Elasticsearch would abort the query due to an URL too long. Fixes #320.
@Radiergummi Radiergummi reopened this Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant