Hi, I've got a search query which fails with "CircuitBreakingException: Data too large" when POSTed, but succeeds when the identical query is sent as a GET (with the json in the query string).
The search query itself may be buggy, as far as I can tell (the "size" parameter is in the wrong place). But the different behaviour between the two test cases is the bug I'm interested in. This is on version 1.0.3, with two nodes. Presumably something is causing too many fieldvalues to be loaded into memory in the POST version (note "nested: QueryPhaseExecutionException" in the error output). I can't reproduce locally with a small dataset, only in production with a 10G index. I guess I would have to create a very large test dataset first (and maybe set the circuit breaker settings low?), but I've run out of time for debugging it this morning and thought I'd see if this was a known issue first. I thought the "nested" message might be a meaningful clue to someone who knows more about it. Gist here: https://gist.github.com/sebbacon/7b5e67aaae7f0e0a31aa Thanks Seb -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/adb7d64d-49f2-4bb6-9cf1-cdc4280b24c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
