Hi all, in the process of upgrading to DSpace 5.4 we encounter many SOLR problems. It seems that solr is looking for index files (/dspace/solr/search/data/index/_sxp.fdt) that do not exist in the current installation, because I replaced the complete solr directory by running ant update again to recreate the directory in an attempt to solve the many problems we have.
Were does solr keeps track of the files in the index? Caused by: java.io.IOException: Map failed: MMapIndexInput(path="/dspace/solr/search/data/index/_sxp.fdt") [this may be caused by lack of enough unfragmented virtual address space or too restrictive virtual memory limits enforced by the operating system, preventing us to map a chunk of 423723626 bytes. Please review 'ulimit -v', 'ulimit -m' (both should return 'unlimited'), and 'sysctl vm.max_map_count'. More information: http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html] at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:888) We upgrade from a DSpace 1.8.3 installation in which we did not use SOLR. We used a new linux server, installed dspace 5.3 and migrated a copy of the dspace 1.8 db to dspace 5.3. We ran into many SOLR problems and did not take the server into production. In the meantime dspace 5.4 was released and we upgraded to dspace 5.4. SOLR was still causing many problems. So I removed the /dspace/solr directory and performed the upgrade again. First mvn followed by update. Imported OAI, ran index-discovery and imported legacy stats files. Still, again, the solr.log reports errors, best wishes, Francis -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
