In that case, I'm kind of stuck. You've already rebuilt your index
from scratch and removed it from your slaves. That should have
cleared out most everything that could be an issue. I'd suggest
you set up a pair of machines from scratch and try to set up an
index/replication with your current schem
Hi Erick,
It's not possible because both master and slaves using same binaries.
Thanks...
On Fri, Mar 23, 2012 at 5:30 PM, Erick Erickson wrote:
> Hmmm, looking at your stack trace in a bit more detail, this is really
> suspicious:
>
> Caused by: org.apache.lucene.index.IndexFormatTooNewExcept
Hmmm, looking at your stack trace in a bit more detail, this is really
suspicious:
Caused by: org.apache.lucene.index.IndexFormatTooNewException: Format
version is not supported in file 'segments_1': -12 (needs to be between -9
and -11)
This *looks* like your Solr version on your slave is older t
Hi Erick,
I've already tried step 2 and 3 but it didn't help. It's almost impossible
to do step 1 for us because of project dead-line.
Do you have any other suggestion?
Thank your reply.
On Fri, Mar 23, 2012 at 4:56 PM, Erick Erickson wrote:
> Hmmm, that is odd. But a trunk build from that lon
Hmmm, that is odd. But a trunk build from that long ago is going
to be almost impossible to debug/fix. The problem with working
from trunk is that this kind of problem won't get much attention.
I have three suggestions:
1> update to current trunk. NOTE: you'll have to completely
reindex your
Hi everyone,
We are using very early version of Solr 4.0 and we've some replication
problems. Actually we used this build more than one year without any
problem but when I made some changes on schema.xml, the following problem
started.
I've just changed schema.xml with adding multiValued="true" a
