Erick Erickson wrote:
>
> SOLR uses Lucene, so I'd expect that putting your index files on a share
> isn't any more robust under SOLR than Lucene
>
> Sounds to me like your network's glitchy.
>
>
Except that with Lucene we had separate processes searching and indexing
directly against th
SOLR uses Lucene, so I'd expect that putting your index files on a share
isn't any more robust under SOLR than Lucene
Sounds to me like your network's glitchy.
FWIW
Erick
On Fri, Sep 10, 2010 at 3:00 PM, brian519 wrote:
>
>
> Yonik Seeley-2-2 wrote:
> >
> >
> > Hmmm, that's interesting. I
Yonik Seeley-2-2 wrote:
>
>
> Hmmm, that's interesting. I wonder if it's a Java bug or something?
> There's nothing in lucene/solr that I know of that would lead to "The
> specified network name is no longer
> available".
>
> What JVM are you using?
>
> -Yonik
> http://lucenerevolution.org
On Fri, Sep 10, 2010 at 2:12 PM, brian519 wrote:
> Once we see the error, it is persistent. Restarting Tomcat makes the error
> stop. This is happening across a variety of deployments and networks, so I
> don't think there is an actual network problem. Many other apps operate
> fine on the same
Hi all,
Using Solr 1.4 hosted with Tomcat 6 on Windows 2003 (sometimes Windows 2008)
Occasionally, we can't search anymore and this error shows up in the log
file:
SEVERE: java.io.IOException: The specified network name is no longer
available
at java.io.RandomAccessFile.read
