Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June."413" Status: Request Entity Too Large is showing up in the logs.
When I reduced it back to 20, it works fine. What is the reason for increasing this to 50? I don't see benefit really.
Best,
Jacob
Comments
Comment #1
robertdouglass commentedInteresting. Seems like one huge node would make a large request entity as well. Whence cometh this error message? What are the limits?
Comment #2
JacobSingh commentedI'm not sure what the limits are. This is actually not a solr issue per se, but I think this is the jetty setting:
http://www.nabble.com/Large-file-upload-to-Jetty-failing-with-HTTP-413-t...
I think that by default we should reduce the # per batch back to 20 because I'm using a default jetty implementation and getting it, means that others would as well. After that... I guess it's just an entry in the FAQ page unless we can cull info about the servlet container somehow...
Best,
Jacob
Comment #3
robertdouglass commentedComment #4
JacobSingh commentedI think this was resolved in another ticket temporarily by setting the # to 20, although it was never really taken care of... I don't suppose there is anyway to auto magically discern the max POST size in Jetty... Maybe the solution here is actually to just fail gracefully, log the error, and give instructions to the user on how to change their setting in jetty to allow bigger payloads AND also provide a variable they can set in settings.php to change the # of nodes per batch.
It's not perfect, but this shouldn't delay 1.0 either IMO
Comment #5
robertdouglass commentedDowngrading on basis of temporary fix in other patch. I like Jacob's suggestions in #4 but needs more research.
Comment #6
JacobSingh commentedClosing this unless it comes back to haunt us, should be okay...