Hello, Yes, perhaps better guidance in the help text, or even changing that line in the example crontab on the wiki so that it has a better description of when it would be appropriate to run that job. Of course people always see "optimize" and they want to run it, but have no idea what it does. Hell, I don't even know what "if excessive, reduce the number of segments in Solr search core" means in the context of a digital repository like DSpace, and I'm a very technical user with a background in computer science!
Cheers, On Wed, Aug 2, 2017 at 10:40 AM helix84 <[email protected]> wrote: > No reason to make it a no-op in DSpace (if you need it, you have it > available without needing to fire a curl query to Solr), but running > the scheduled task daily is not necessary. That said, it doesn't cost > much, either. The excessive usage Solr devs referred to was running it > after every batch update or even after every added document. > > We might also change the help output of index-discovery -h to > something more descriptive like "if excessive, reduce the number of > segments in Solr search core". > > Current output: > > stats-util -h > -o,--optimize Run maintenance on the SOLR index > > index-discovery -h > -o optimize search core > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing List Etiquette > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > > On Wed, Aug 2, 2017 at 9:24 AM, Alan Orth <[email protected]> wrote: > > Hi, > > > > What is the current best practices recommendation for `index-discovery > -o` > > in DSpace 4, 5, and 6? In this thread helix84 pointed out a quite old > issue > > on the Solr bug tracker that discussed the usefulness of the "optimize" > > (forceMerge) operation in Solr. I've had this disabled on our DSpace > > instances for almost a year now but notice it is still recommended on the > > various scheduled tasks pages on the wiki[0]. > > > > What are people's thoughts on this? Should we remove it from the official > > list of scheduled tasks (and make the `index-discovery -o` subcommand a > > noop)? > > > > [0] https://wiki.duraspace.org/display/DSDOC6x/Scheduled+Tasks+via+Cron > > > > Regards, > > > > On Thu, Mar 17, 2016 at 8:38 PM Terry Brady <[email protected]> > > wrote: > >> > >> See the prior note from helix84 that references the log files of > interest. > >> Take a look at those files to diagnose the problem. > >> > >>> The 503 error you see is from the Solr client side (DSpace). To see the > >>> actual error you need to look into Solr log (catalina.out or solr.log > >>> depending on DSpace version). > >> > >> > >> If the errors are unclear, please post the error messages to this > thread. > >> > >> Terry > >> > >> On Thu, Mar 17, 2016 at 4:44 AM, Lulamile Mangali > >> <[email protected]> wrote: > >>> > >>> Hi Terry, > >>> > >>> Can you assist us here, we have installed a new 5.3 DSpace instance and > >>> now are getting an error that says "503 Service Temporarily > Unavailable" - > >>> could you please give us an indicator as to what might be the > problem...? > >>> > >>> Thanking you in advance.. > >>> > >>> > >>> > >>> On Wednesday, January 13, 2016 at 10:52:09 AM UTC+2, helix84 wrote: > >>>> > >>>> Hi Terry, > >>>> > >>>> 1. The 503 error you see is from the Solr client side (DSpace). To see > >>>> the actual error you need to look into Solr log (catalina.out or > solr.log > >>>> depending on DSpace version). > >>>> > >>>> 2. Running the forceMerge operation (-o) on a regular basis is not > >>>> really necessary. It can help in special circumstances, but it's not > such a > >>>> big deal in normal operation, especially in read-heavy use case such > as > >>>> DSpace. You can more about that here: [1] > >>>> > >>>> [1] https://issues.apache.org/jira/browse/SOLR-3141 > >>>> > >>>> > >>>> Regards, > >>>> ~~helix84 > >>>> > >>>> Compulsory reading: DSpace Mailing List Etiquette > >>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > >>>> > >> > >> > >> > >> -- > >> Terry Brady > >> Applications Programmer Analyst > >> Georgetown University Library Information Technology > >> https://www.library.georgetown.edu/lit/code > >> 425-298-5498 (Seattle, WA) > >> > >> -- > >> 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. > > > > -- > > Alan Orth > > [email protected] > > https://picturingjordan.com > > https://englishbulgaria.net > > https://mjanja.ch > > > > -- > > 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. > -- Alan Orth [email protected] https://picturingjordan.com https://englishbulgaria.net https://mjanja.ch -- 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.
