Hi Deborah.
Just a thought and a common problem that I have seen that causes
index-discovery to take a long time, is that for the command line, one
does not assign enough resource to the JVM. By increasing the amount of
memory assigned to the JVM, you could speed up the indexing. Looking at
your repository, it appears to have about 12000 items. It should not
take too long to index.
BTW, Sorry about the cricket :-)
On 2019/07/04 07:17, Fitchett, Deborah wrote:
Kia ora,
We’ve got a situation where:
·we need to rebuild our keyword index;
·/dspace index-discovery -b takes some unknown multiple of days; and
·we have a backup outage each midnight, interrupting the reindex
part-way through.
The obvious option is to turn off the backup outage until the job is
complete; if we have to, we have to.
But… is there another way?
Is there a way of knowing when the job is complete (or, while it’s
running, of knowing how far along it is)?
Is there a way of resuming a half-completed indexing job?
Is there a way of… like, splitting the indexing job up into sections?
Somehow. IDK.
(If you can’t already tell, I don’t really **understand** the system,
I just run the commands we’ve always run in the past...)
Deborah
––––––––––––––––––––––––––––––––––
*Deborah Fitchett*
Head of Department: Digital Services
––––––––––––––––––––––––––––––––––
*Library, Teaching and Learning – Te Wharepūrākau*
PO Box 85064, Lincoln University
Lincoln 7647, Christchurch, New Zealand
+64 3 423 0358
deborah.fitch...@lincoln.ac.nz <mailto:deborah.fitch...@lincoln.ac.nz>
ltl.lincoln.ac.nz
––––––––––––––––––––––––––––––––––
*Lincoln University*
Te Whare Wānaka o Aoraki
––––––––––––––––––––––––––––––––––
------------------------------------------------------------------------
"The contents of this e-mail (including any attachments) may be
confidential and/or subject to copyright. Any unauthorised use,
distribution, or copying of the contents is expressly prohibited. If
you have received this e-mail in error, please advise the sender by
return e-mail or telephone and then delete this e-mail together with
all attachments from your system." --
All messages to this mailing list should adhere to the DuraSpace Code
of Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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 dspace-tech+unsubscr...@googlegroups.com
<mailto:dspace-tech+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/SY3PR01MB1307EEA5CA6FB64901A052B2C5FA0%40SY3PR01MB1307.ausprd01.prod.outlook.com
<https://groups.google.com/d/msgid/dspace-tech/SY3PR01MB1307EEA5CA6FB64901A052B2C5FA0%40SY3PR01MB1307.ausprd01.prod.outlook.com?utm_medium=email&utm_source=footer>.
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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 dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/786dc219-d25d-67b8-2367-81c93dc586e9%40teqcle.co.za.
