Yep that was my issue.
And like Ken said on Tomcat I set maxHttpHeaderSize="65536".
--
View this message in context:
http://lucene.472066.n3.nabble.com/Hitting-the-URI-limit-how-to-get-around-this-tp3017837p3020774.html
Sent from the Solr - User mailing list archive at Nabble.com.
finition in server.xml
>
> Colin.
>
> -Original Message-
> From: Ken Krugler [mailto:kkrugler_li...@transpac.com]
> Sent: Friday, June 03, 2011 12:39 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Hitting the URI limit, how to get around this?
>
> It sounds li
nt: Friday, June 03, 2011 12:39 PM
To: solr-user@lucene.apache.org
Subject: Re: Hitting the URI limit, how to get around this?
It sounds like you're hitting the max URL length (8K is a common default)
for the HTTP web server that you're using to run Solr.
All of the web servers I know abo
html
>
>
> My shards are added dynamically, every few hours I am adding new shards or
> cores into the cluster. so I cannot have a shard list in the config files
> unless I can somehow update them while the system is running.
>
> --
> View this message in context:
>
ew shards or
cores into the cluster. so I cannot have a shard list in the config files
unless I can somehow update them while the system is running.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Hitting-the-URI-limit-how-to-get-around-this-tp3017837p3020185.html
Sent from the
ts core01, core02, core03, ...)?
>
> Thanks!
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Hitting-the-URI-limit-how-to-get-around-this-tp3017837p3017837.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
t of
servers (nodeA:1234,nodeB:1234,...) and each of those nodes query the cores
that they host (nodeA hosts core01, core02, core03, ...)?
Thanks!
--
View this message in context:
http://lucene.472066.n3.nabble.com/Hitting-the-URI-limit-how-to-get-around-this-tp3017837p3017837.html
Sent from the
