[
http://jira.dspace.org/jira/browse/DS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue updated DS-615:
---------------------------
Status: Open (was: Received)
This issue was discussed in the Developer Meeting on 08 Sept 2010:
[20:26] <tdonohue> DS-615 : Ability to perform maintenance on SOLR with
solr.optimize http://jira.dspace.org/jira/browse/DS-615
[20:27] <tdonohue> Peter has already claimed this -- so, I'm assuming he's
working on it for 1.7...any quick comments to pass along to Peter?
[20:27] <tdonohue> I'd be +1 this -- we need to be maintaining Solr indexes
better
[20:27] <mhwood> +1
[20:28] <mdiggory> +!
[20:28] <mdiggory> light enough
> Ability to perform maintenance on SOLR with solr.optimize
> ---------------------------------------------------------
>
> Key: DS-615
> URL: http://jira.dspace.org/jira/browse/DS-615
> Project: DSpace 1.x
> Issue Type: Improvement
> Components: Solr
> Environment: solr
> Reporter: Peter Dietz
> Assignee: Peter Dietz
> Priority: Minor
> Fix For: 1.7.0
>
> Attachments: solr-optimize.patch
>
>
> By adding all historical log data to a SOLR index, as well as the constant
> addition of new records, it might be good for the efficient performance of a
> SOLR index to periodically run solr.optimize.
> Therefore I've created a patch which allows you to run solr.optimize on your
> solr instance from the command line. This could allow you to add a cron task
> that runs this periodic maintenance. It also spits out the amount of time
> taken to run the optimize task.
> Once you patch your instance. You can execute this with
> /dspace/bin/dspace stats-util --optimize
> or
> /dspace/bin/dspace stats-util -o
> Output looks like:
> SOLR Optimize -- Process Started:1277486321673
> SOLR Optimize -- Process Finished:1277486321738
> SOLR Optimize -- Total time taken:65 (ms).
> It would be useful to profile the amount of time taken for solr operations
> add/update/query before running this optimize task, and then afterwards.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
