> > Hi Hardy,
I had the same problem when testing the upgrade to DSpace 5.3 from our DSpace 1.8 server. Although the update scripts are supposed to regenerate the indexes that does not happen. I had to run /dspace/bin/dspace index-discovery to create the indexes. One way to check it is whether there are entries in /dspace/solr/search/data directory. Because we have not used SOLR before that directory was empty and remained empty after the upgrade. While running index-discovery this directory is being filled with indexes. Please check the manual (page 81 of the PDF version) for the parameters you want to use. I ran the script without the -o option because in first instance the script ran out of memory and threw MMAP errors. I reported that in another message. After assigning more RAM to the server, the index-discovery did work. # NOTE: You should not need to optimize the Discovery Search and Browse indexes, as they will be automatically rebuilt on upgrade (See previous upgrade step) # However, you still may wish to schedule optimizing of Discovery Search & Browse (via cron or similar) # [dspace]/bin/dspace index-discovery -o 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 http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
