bugfix: allow for larger request payload to avoid 413 when unwarranted #188
Conversation
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
|
What's the batch size you are running? |
|
I was looking into making this configurable. What would be the preferred method of doing so? cmd line arg or env var? |
Env var preferably |
I don't recall exactly, but large enough to get this error I guess 😅 |
|
Closed in favour of #210 |
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.
What does this PR do?
This PR enlarges the allowed request payload to be 0.5GB expressed in bytes -
67110000.I am submitting this PR to fix a production bug that we were facing with the service where large re-rank requests would fail due to a 413 from axum.
@OlivierDehaene OR @Narsil