Hi,
Is this already registered as bug.Is their any fix to this issue(i want use
EmbeddedSolrServer server only).
Regards,
Ram.
--
View this message in context:
http://lucene.472066.n3.nabble.com/1-3-help-with-update-timeout-issue-tp505766p3310048.html
Sent from the Solr - User mailing list arch
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
: Subject: Index Courruption after replication by new Solr 1.4 Replication
: References: <3ca90cc651ae3f4baedf8a5b78639c8c038a1...@mail02.tveyes.com>
: <667725.5147...@web52905.mail.re2.yahoo.com>
: <3ca90cc651ae3f4baedf8a5b78639c8c038a1...@ma
, 2010 12:31 PM
To: solr-user@lucene.apache.org
Subject: Re: Index Courruption after replication by new Solr 1.4 Replication
This is not a direct answer to your question, but can you avoid NFS? My first
guess would be that NFS somehow causes this problem. If you check the ML
archives for: NFS
> From: Osborn Chan
> To: "solr-user@lucene.apache.org"
> Sent: Fri, January 15, 2010 3:23:21 PM
> Subject: Index Courruption after replication by new Solr 1.4 Replication
>
> Hi all,
>
> I have migrated new Solr 1.4 Replication feature with multicore
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
