From: Michael L. <mi...@la...> - 2011-10-27 16:06:33
|
Hello, I am comming back to my question I had the other day about how to optimize after an import. As far as I can tell there should be three ways within vufind that can do it but two of them didn't work for me, among them my favorite (the first). 1) setting in import.properties: solr.optimize_at_end="true" I would like to use this but there is no indication that it worked (no log message and the index is quite big). I also tried without quotation marks but with the same result. 2) C:\vufind\import\bin\optimizesolr.bat gives this error message: 27.10.2011 17:55:09 org.apache.solr.handler.component.SpellCheckComponent$SpellCheckerListener buildSpellIndex SCHWERWIEGEND: Exception in building spell check index for spellchecker: basicSpell java.lang.RuntimeException: java.io.IOException: Cannot overwrite: C:\vufind\solr\biblio\spellchecker\_s.fdt ... [and many more similar messages] But it looks as if at least the optimize for the main biblio index did work (quite a lot more free disk space after the call). 3) From the Wiki I got "php optimize.php" and "php optimize.php authority" This one looks good. Of course I can use the third alternative or use curl or whatever but I think it would be nice to have it working without an extra call (1) and I just wanted to report the problems with 2) -Michael |
From: Demian K. <dem...@vi...> - 2011-10-27 16:26:40
|
I'm copying this message to the solrmarc-tech list, since there may be some additional comments from that front. First of all, what versions of VuFind/Solr/SolrMarc are you using? I just tried testing this under Windows using the very latest VuFind trunk (recently upgraded to the newest Solr and SolrMarc releases). Once I updated import/import.properties to point to the correct paths, I was able to get both the "solr.optimize_at_end" setting and the "optimizesolr.bat" script to work. In both cases, I see the log message: INFO: Calling commit (with optimize set to true) There does seem to be one strange problem, though -- I have to trigger the optimize action TWICE before files are cleaned up from disk -- that is, the first time I run optimize, Solr creates an optimized version of the index but leaves the old dirty version behind. After the second optimize operation, the old files are removed. I'm only seeing this under Windows; everything works as expected under Linux. Has anyone else encountered this issue? - Demian > -----Original Message----- > From: Michael Lackhoff [mailto:mi...@la...] > Sent: Thursday, October 27, 2011 12:06 PM > To: vuf...@li... > Subject: [VuFind-General] Optimize after import > > Hello, > > I am comming back to my question I had the other day about how to > optimize after an import. > > As far as I can tell there should be three ways within vufind that can > do it but two of them didn't work for me, among them my favorite (the > first). > > 1) setting in import.properties: solr.optimize_at_end="true" I would > like to use this but there is no indication that it worked (no log > message and the index is quite big). I also tried without quotation > marks but with the same result. > > 2) C:\vufind\import\bin\optimizesolr.bat gives this error message: > 27.10.2011 17:55:09 > org.apache.solr.handler.component.SpellCheckComponent$SpellCheckerListe > ner > buildSpellIndex > SCHWERWIEGEND: Exception in building spell check index for > spellchecker: > basicSpell > java.lang.RuntimeException: java.io.IOException: Cannot overwrite: > C:\vufind\solr\biblio\spellchecker\_s.fdt > ... [and many more similar messages] > > But it looks as if at least the optimize for the main biblio index did > work (quite a lot more free disk space after the call). > > 3) From the Wiki I got "php optimize.php" and "php optimize.php > authority" > This one looks good. > > Of course I can use the third alternative or use curl or whatever but I > think it would be nice to have it working without an extra call (1) and > I just wanted to report the problems with 2) > > -Michael > > ----------------------------------------------------------------------- > ------- > The demand for IT networking professionals continues to grow, and the > demand for specialized networking skills is growing even more rapidly. > Take a complimentary Learning@Cisco Self-Assessment and learn > about Cisco certifications, training, and career opportunities. > http://p.sf.net/sfu/cisco-dev2dev > _______________________________________________ > VuFind-General mailing list > VuF...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-general |
From: Erik H. <eri...@gm...> - 2011-10-27 17:25:31
|
On Oct 27, 2011, at 12:26 , Demian Katz wrote: > There does seem to be one strange problem, though -- I have to trigger the optimize action TWICE before files are cleaned up from disk -- that is, the first time I run optimize, Solr creates an optimized version of the index but leaves the old dirty version behind. After the second optimize operation, the old files are removed. I'm only seeing this under Windows; everything works as expected under Linux. Has anyone else encountered this issue? Lucene cannot remove the files that are in use on Windows, whereas it can on 'nix platforms. It's working as designed. The files will eventually get removed automatically, if you added more documents and a merge occurred or as you've seen through another optimize. Erik |