Grainne, I would recommend that you do not do this. In fact, I would recommend you not use NFS as well, although that’s more likely to work, just not ideally. Solr’s going to do best when it’s working with fast, local storage that the OS can cache natively.
Michael Della Bitta Senior Software Engineer o: +1 646 532 3062 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions | g+: plus.google.com/appinions w: appinions.com On Oct 2, 2014, at 14:44, Grainne <grainne_rei...@harvard.edu> wrote: > I am currently running Solr 4.4.0 on RHEL 6. The index used to be mounted > via nfs and it all worked perfectly fine. For security reasons we switched > the index to be sshfs mounted - and this seems to cause solr to fail after a > while. If we switch back to nfs it works again. > > The behavior is strange - Solr starts up and issues an error: > ... > Oct 02, 2014 11:43:00 AM org.apache.solr.common.SolrException log > SEVERE: org.apache.solr.common.SolrException: Error opening new searcher > ... > Caused by: java.io.FileNotFoundException: > /path/to/collection/data/index/_10_Lucene41_0.tim (Operation not permitted) > ... > > While Solr is running, if, as the same user, I look at the mounted path I > get the same behavior: > -bash-4.1$ ls /mounted/filesystem/path > ls: reading directory /mounted/filesystem/path: Operation not permitted > > When I shut down Solr it behaves as expected and I get the file listing. > The file is there and > > Several of us, including unix systems people, are looking at why this might > be happening and have yet to figure it out. > > Does anyone know if it possible to run Solr where the index is mounted via > sshfs? > > Thanks for any advice, > Grainne > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Does-Solr-handle-an-sshfs-mounted-index-tp4162375.html > Sent from the Solr - User mailing list archive at Nabble.com.
