Mark Miller-3 wrote
> On Feb 15, 2013, at 6:04 AM, o.mares <
> ota.mares+nabble@
> > wrote:
>
>> Hey when running a solr cloud setup with 4 servers, managing 3 cores each
>> splitted on 2 shards, what are the proper steps to do a full index
>> import?
>&
It was/is a client issue. The googlebot executed a request where the search
term was CP1252 encoded, maybe the brokenn url got indexed from a third
party site.
We solved the issue by filtering all non valid utf8 chars from the search
input string because there is no proper way to check what encodi
Hey when running a solr cloud setup with 4 servers, managing 3 cores each
splitted on 2 shards, what are the proper steps to do a full index import?
Do you have to import the index on all of the solr instances? Or is it
sufficient enough to perform the import on one instance and it will get
replic
Hey,
yesterday we updated from solr 4.0 to solr 4.1 and since then from time to
time following error pops up:
{msg=URLDecoder: Invalid character encoding detected after position 160 of
query string / form data (while parsing as UTF-8),code=400}:
{msg=URLDecoder: Invalid character encoding detect
Hey does there exist a upgrade guide? Or do you simply copy all files over?
If yes, how to verify if everything is in place.
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-upgrade-from-4-0-to-4-1-tp4039757p4039775.html
Sent from the Solr - User mailing list archiv
