Hi, I have a few observations concerning DS-615, if anyone has a moment. I'm sending this note to the devel list, despite the thread having a tech list heritage, because it's a question for the committers.
A quick recap, in case you missed this thread last week. Our production Tomcat server was having trouble last week, and it turns out that Andrea's suggestion, to optimise our SOLR indexes, solved the issue for us. (see below for the entire thread) It looks like DS-615 patches made it in to the DSpace 1.7 release, but the ticket for DS-615 indicates a status of reopened, a resolution of unresolved, and the fix version is 1.8.0. From the comments on the ticket, it does look like the patches for 615 were included for DSpace 1.7, but the ticket remains open, I believe because an additional need, for an option to also optimize the Discover SOLR indexes, was identified. With that longwinded preface out of the way, :-) what I think might have happened, is that, with the ticket still open, the need to document the new features added by the patches associated with the ticket sort of slipped through the cracks. I think the documentation should reflect the new command line options for DSpace, and the upgrade instructions from 1.6 to 1.7 should include a specific recommendation to utilize the stats-util --optimize as a cron job. I am happy to make these documentation changes, and will make them in both the 1.7 docs, as well as the 1.8 dev docs section of the wiki. After discussing this with a few of you, I think it's best if a new ticket is created to reflect the changed nature of DS-615, if my read on the situation is correct. -- HARDY POTTINGER <pottinge...@umsystem.edu> University of Missouri Library Systems http://lso.umsystem.edu/~pottingerhj/ "No matter how far down the wrong road you've gone, turn back." --Turkish proverb On 7/13/11 11:27 AM, "Pottinger, Hardy J." <pottinge...@umsystem.edu> wrote: >Hi, Andrea, thank you very much for this suggestion! We were not >optimizing our SOLR index via cron, but are now. We are running DSpace >1.7.2 in production, and it appears that DS-615 made it into 1.7 somewhere >along the way ([dspace]/bin/dspace stats-util -o exists and appears to >work), though the ticket for DS-615 indicates it is scheduled for 1.8. >{scratching my head} This has me a bit worried, and confused, as DS-615 >mentions not only the optimization tweak, but the auto-commit tweak. I >believe this part of DS-615 was also included in one of the recent >upgrades (likely at the same time), and a glance at my >[dspace]/solr/statistics/conf/solrconfig.xml file does show that >autocommit is configured there. > >I'm thinking that we need include the suggested crontab entry for >optimizing the SOLR index in the documentation, and also include it in the >upgrade instructions for 1.7. I've skimmed both and can't find any mention >of the stats-util command, nor anything about SOLR autocommit. > >My main question is, should I be checking anything else, in relation to >this, to ensure things are working as well as they should be? >-- >HARDY POTTINGER <pottinge...@umsystem.edu> >University of Missouri Library Systems >http://lso.umsystem.edu/~pottingerhj/ >"No matter how far down the wrong road you've gone, >turn back." --Turkish proverb > > > > > > >On 7/12/11 5:05 PM, "Andrea Schweer" <schw...@waikato.ac.nz> wrote: > >>Hi Hardy, >> >>On 13/07/11 07:19, Pottinger, Hardy J. wrote: >>> Hi, George, now that you mention it, the only thing showing up in the >>> logs at the time of the memory error were lines about SOLR stats. I >>> figured that was just an indication of normal usage. >> >>Just a stab in the dark -- are you optimising your Solr indexes at all? >>See https://jira.duraspace.org/browse/DS-615. We applied that patch and >>run the optimise command via cron once a day. I assume that you are >>using autocommit for the stats; if not then it'd definitely be a good >>idea to enable that. >> >>cheers, >>Andrea >> >>-- >>Andrea Schweer >>IRR Technical Specialist, ITS Information Systems >>The University of Waikato, Hamilton, New Zealand >> >>------------------------------------------------------------------------- >>- >>---- >>AppSumo Presents a FREE Video for the SourceForge Community by Eric >>Ries, the creator of the Lean Startup Methodology on "Lean Startup >>Secrets Revealed." This video shows you how to validate your ideas, >>optimize your ideas and identify your business strategy. >>http://p.sf.net/sfu/appsumosfdev2dev >>_______________________________________________ >>DSpace-tech mailing list >>dspace-t...@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/dspace-tech > > >-------------------------------------------------------------------------- >---- >AppSumo Presents a FREE Video for the SourceForge Community by Eric >Ries, the creator of the Lean Startup Methodology on "Lean Startup >Secrets Revealed." This video shows you how to validate your ideas, >optimize your ideas and identify your business strategy. >http://p.sf.net/sfu/appsumosfdev2dev >_______________________________________________ >DSpace-tech mailing list >dspace-t...@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
