Hi Guys,
I'm experiencing the same issue with a single war. I'm using a brand new
Solr war built from yestertay's version of the trunk.
I've got one master with 2 cores and one slave with a single core. I'm using
one core from master as the master of the second core (which is configured
as a re
On Sat, Jan 16, 2010 at 7:38 AM, Joe Kessel wrote:
> There is no issue here, we had patched our solr to include SOLR-1595 and our
> webapps directory contained two wars. With only a single war file there is
> no issue with this replication handler.
Thanks Joe, for now I've added a note to the
There is no issue here, we had patched our solr to include SOLR-1595 and our
webapps directory contained two wars. With only a single war file there is no
issue with this replication handler.
thanks for the quick response.
Joe
> From: isjust...@hotmail.com
> To: solr-user@lucene.apach
I am using the example solrconfig.xml with only a few changes. Mainly the
replication section for the master has been changed. I am not using any
plugins that I am aware of. Here is my replication section:
startup
optimize
If this is valid, then I will open
Interesting... this should be impossible.
Unless there is a bug in Lucene's NativeFSLock (and it doesn't look
like it), the only way I see that this could happen is if there were
multiple instances of that class loaded in different classloaders.
Are you using any kind of plugins?
Could you open a
I have an instance of Solr that won't start since I have added the replication
startup. I am using Solr 1.4 and only see
this with my index that contains 200k documents with a total size of 400MB.
Removing the replicate after startup and the instance starts without error. We
found that we n
