Hi Jay, There is a setting to increase that limit, but I want to understand what's happening as it is unexpected. Can you open up the developer tools in Chrome and check the headers of the failed request? I wonder what it is that is so long.
Cheers, Boaz On Tuesday, February 24, 2015 at 11:16:33 PM UTC+1, Jay Hilden wrote: > > I am on a Windows 8 PC and I downloaded ES 1.4.4, installed Marvel's > latest version, and started ES. ES starts up just fine but when I tried to > view marvel I get an exception within ES: > > [2015-02-24 16:10:14,462][WARN ][http.netty ] [Kid Nova] > Caught exception while handling client http traffic, closing connection > [id: 0xc3000144, /0:0:0:0:0:0:0:1:51607 => /0:0:0:0:0:0:0:1:9200] > org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: > HTTP header is larger than 8192 bytes. > > The only thing that I changed was the cluster name in the .yml file, > nothing else was touched. > > This exception happens in Chrome, in FF Developer Edition it runs just > fine. > > What's up with that? > -- 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/726ddbf8-4337-4f72-bb23-12c040c38941%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
