ile a bug?
Thanks,
Osborn
-Original Message-
From: Osborn Chan [mailto:oc...@shutterfly.com]
Sent: Friday, January 15, 2010 12:35 PM
To: solr-user@lucene.apache.org
Subject: RE: Index Courruption after replication by new Solr 1.4 Replication
Hi Otis,
Thanks. There is no NFS anymore, a
lock , you will see what I mean.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
> From: Osborn Chan
> To: "solr-user@lucene.apache.org"
> Sent: Fri, January 15, 2010 3:23:21 PM
> Subject: Index Courruption after repli
Hi all,
I have migrated new Solr 1.4 Replication feature with multicore support from
Solr 1.2 with NFS mounting recently. The following exceptions are in
catalina.log from time to time, and there are some EOF exceptions which I
believe the slave index files are corrupted after replication from
Hi all,
I got following exception for SOLR, but the index is still searchable. (At
least it is searchable for query "*:*".)
I am just wondering what is the root cause.
Thanks,
Osborn
INFO: [publicGalleryPostMaster] webapp=/multicore path=/select
params={wt=javabin&rows=12&start=0&sort=/gallery
last snapshot
if it is a single core you will have to restart the master
On Sat, Nov 7, 2009 at 1:55 AM, Osborn Chan wrote:
> Thanks. But I have following use cases:
>
> 1) Master index is corrupted, but it didn't replicate to slave servers.
> - In this case, I only need t
