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 <bpear...@desire2learn.com> wrote: > > > 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 Lucene/Solr Conference, Boston Oct 7-8 > > > > > > java -version gives me this: > > java version "1.6.0_18" > Java(TM) SE Runtime Environment (build 1.6.0_18-b07) > Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode) > > Is that what you're looking for? > > Can you confirm that putting the Index files on a network share is OK? We > used to use Lucene and I know that this was bad news .. but since getting > these errors we're wondering whether Solr might have a similar issue. > > I found this Java bug, but it's really old and I'm not sure if it's > relevant: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6176034 > > Thanks Yonik > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SEVERE-java-io-IOException-The-specified-network-name-is-no-longer-available-tp1454016p1454271.html > Sent from the Solr - User mailing list archive at Nabble.com. >
