Thanks, Andrea:
I do backup everything with every upgrade and that has been a help since I have
had to go back and forth from 4.x to 5.x multiple times. I might just drop
teh stats since I am not using them for my test instance. I am planning on
converting our production instance soon, and I may take the the indexes from
that and try them and see if I get the same error.
Thanks for your help.
George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CULIT)
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
________________________________
From: Andrea Schweer <schw...@waikato.ac.nz>
Sent: Wednesday, April 1, 2015 11:09 PM
To: George Stanley Kozak; dspace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Error after install of DSpace 5.1
Hi,
On 02/04/15 12:50, George Stanley Kozak wrote:
?Andrea:
I'm not sure if you saw my follow up post. Yes, I did see errors in the Solr
log. It is:
ERROR org.apache.solr.core.CoreContainer @ Unable to create core: statistics
Format version is not supported (resource: segment _32 in resource
ChecksumIndexInput(MMapIndexInput(path="/cul/app/dspace/solr/statistics/data/index/segments_1p0"))):
2.x. This version of Lucene only supports indexes created with release 3.0 and
later.
If I later try to upgrade to 5.1, I see during the ant update:
/cul/app/dspace/src/dspace-5.1-src-release/dspace/target/dspace-installer/build.xml:1061:
ERROR occurred while checking Solr index version:
Exception in thread "main" java.io.IOException: Could not read Lucene segments
files in /cul/app/dspace/solr/statistics/data/index
No sorry, I didn't see that. I did however run into a very similar problem with
one of my own DSpace 5.1 development instances the other day. I'm not quite
sure what state the solr indexes were in at that stage, so I'm not sure how to
reproduce it. It does look like we should add a big warning to the upgrade
instructions for people to back up their solr index first -- my problem went
away when I re-set the usage stats data dir in my dev instance to a fresh copy
from (4.2) production.
I did try to manually update the Solr statistics using the instructions in the
DSpace 5.1 Manual, but that didn't seem to help..
My suspicion is that once the upgrade fails halfway through for some reason,
there is no way to recover from the situation. Hence the importance of the
back-up!
Is there a way to tell the DSpace that we don't want to use the Solr Stats? We
have our own statistics gathering so I'm really not using them.
It looks like you can disable adding new hits to the Solr statistics by
commenting out the SolrLoggerUsageEventListener bean in
dspace-xmlui/src/main/webapp/WEB-INF/spring/applicationContext.xml (XMLUI) /
dspace-jspui/src/main/webapp/WEB-INF/spring//applicationContext.xml (JSPUI).
Then you could delete the contents of [dspace]/solr/statistics/data (for anyone
following along on this -- this _will_ wipe all your usage stats data! Do this
only when you're sure that's what you want!) and that should be it. But I've
never tried this, so it may break lots of things in lots of interesting ways.
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
