Mark, I am testing the upgrade and indexing gives me this error:
914379 [http-apr-8080-exec-4] ERROR org.apache.solr.core.SolrCore ?
org.apache.solr.common.SolrException: Invalid UTF-8 middle byte 0xe0 (at
char #1, byte #-1)
... and a bunch of these
request:
http://xx.xx.xx.xx/col1/update
On Jan 31, 2014, at 11:15 AM, David Santamauro
wrote:
> On 01/31/2014 10:22 AM, Mark Miller wrote:
>
>> I’d also highly recommend you try moving to Solr 4.6.1 when you can though.
>> We have fixed many, many, many bugs around SolrCloud in the 4 releases since
>> 4.4. You can follow the prog
http://about.me/markrmiller
On Jan 31, 2014, at 11:11 AM, David Santamauro
wrote:
>
> There is nothing of note in the zookeeper logs. My solr.xml (sanitized for
> privacy) and identical on all 4 nodes.
>
> zkHost="xx.xx.xx.xx:2181,xx.xx.xx.xx:2181,xx.xx.xx.xx:2181,xx.xx.xx.xx:2181,xx.xx.xx.
On 01/31/2014 10:22 AM, Mark Miller wrote:
I’d also highly recommend you try moving to Solr 4.6.1 when you can though. We
have fixed many, many, many bugs around SolrCloud in the 4 releases since 4.4.
You can follow the progress in the CHANGES file we update for each release.
Can I do a drop
On 01/31/2014 10:35 AM, Mark Miller wrote:
On Jan 31, 2014, at 10:31 AM, Mark Miller wrote:
Seems unlikely by the way. Sounds like what probably happened is that for some
reason it thought when you restarted the shard that you were creating it with
numShards=2 instead of 1.
No, that’s n
On Jan 31, 2014, at 10:31 AM, Mark Miller wrote:
> Seems unlikely by the way. Sounds like what probably happened is that for
> some reason it thought when you restarted the shard that you were creating it
> with numShards=2 instead of 1.
No, that’s not right. Sorry.
It must have got assign
On Jan 31, 2014, at 10:13 AM, David Santamauro
wrote:
> Oh, and I'm assuming shard1 is completely corrupt.
Seems unlikely by the way. Sounds like what probably happened is that for some
reason it thought when you restarted the shard that you were creating it with
numShards=2 instead of 1.
Would probably need to see some logs to have an idea of what happened.
Would also be nice to see the after state of zk in a text dump.
You should be able to fix it, as long as you have the index on a disk, just
make sure it is where it is expected and manually update the clusterstate.json.
Woul
