It sounds like you need to increase the HTTP header size. In tomcat the default is 4096 bytes, and to change it you need to add maxHttpHeaderSize="<value>" to the connector definition 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 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 about let you bump this limit up via configuration settings. -- Ken On Jun 3, 2011, at 9:27am, JohnRodey wrote: > So here's what I'm seeing: I'm running Solr 3.1 > I'm running a java client that executes a Httpget (I tried HttpPost) with a > large shard list. If I remove a few shards from my current list it returns > fine, when I use my full shard list I get a "HTTP/1.1 400 Bad Request". If > I execute it in firefox with a few shards removed it returns fine, with the > full shard list I get a blank screen returned immediately. > > My URI works at around 7800 characters but adding one more shard to it blows > up. > > Any ideas? > > I've tried using SolrJ rather than httpget before but ran into similar > issues but with even less shards. > See > http://lucene.472066.n3.nabble.com/Long-list-of-shards-breaks-solrj-query-td 2748556.html > http://lucene.472066.n3.nabble.com/Long-list-of-shards-breaks-solrj-query-td 2748556.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: http://lucene.472066.n3.nabble.com/Hitting-the-URI-limit-how-to-get-around-t his-tp3017837p3020185.html > Sent from the Solr - User mailing list archive at Nabble.com. -------------------------- Ken Krugler +1 530-210-6378 http://bixolabs.com custom data mining solutions
