SOLR: Core with name 'statistics-xxxx' already exists

[Javier Távara]

Hello.
Today I saw my search results aren't being updated, so I decided to see the logs and I found:

INFO org.apache.solr.handler.admin.CoreAdminHandler @ core create command instanceDir=statistics&name=statistics-2011&action=CREATE&dataDir=/home/dspace/installation/solr/statistics-2011/data&wt=javabin&version=2

WARN org.apache.solr.handler.admin.CoreAdminHandler @ Creating a core with existing name is not allowed

ERROR org.apache.solr.core.SolrCore @ org.apache.solr.common.SolrException: Core with name 'statistics-2011' already exists.

INFO org.apache.solr.servlet.SolrDispatchFilter @ [admin] webapp=null path=/admin/cores params={instanceDir=statistics&name=statistics-2011&action=CREATE&dataDir=/home/dspace/installation/solr/statistics-2011/data&wt=javabin&version=2} status=500 QTime=1

ERROR org.apache.solr.servlet.SolrDispatchFilter @ null:org.apache.solr.common.SolrException: Core with name 'statistics-2011' already exists.

The message I'm getting:

Creating a core with existing name is not allowed.
Core with name 'statistics-2011' already exists.

According to the dates recorded, this is happening when 2 cron jobs are running:

 # Cleanup Web Spiders from DSpace Statistics Solr Index at 01:00 every day
# NOTE: ONLY NECESSARY IF YOU ARE RUNNING SOLR STATISTICS
# (This removes any known web spiders from your usage statistics)
0 1 * * * $DSPACE/bin/dspace stats-util -i
 
# Re-Optimize DSpace Statistics Solr Index at 01:30 every day
# NOTE: ONLY NECESSARY IF YOU ARE RUNNING SOLR STATISTICS
# (This ensures that the Statistics Solr Index is re-optimized for better performance)
30 1 * * * $DSPACE/bin/dspace stats-util -o

And it started the first day of this year (because of dspace stats-util -s maybe).

And don't know if this will resolve my original problem (search results aren't being updated), but maybe it's a start.

I hope someone can help me.

Thanks!

Javier.

[Fitchett, Deborah]

We’ve had the same error message for a while – it happens whenever our cron runs dspace stats-util -o (we don’t run dspace stats-util -i). In our case it’s always for ‘statistics-2013’ though we’ve got several other cores so don’t know why it hates that one in particular.

 

I don’t think it’s affecting our search results. We are having serious problems with usage statistics but suspect that’s to do with something else we did – just haven’t been able to figure it out because we don’t really understand how usage stats are built in DSpace (especially as we’re on XMLUI but found the JSPUI stats much more useful: c’est la vie).

 

Not much help I’m afraid but maybe useful as another datapoint.

 

Deborah

--
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...@googlegroups.com.
To post to this group, send email to dspac...@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

---

P Please consider the environment before you print this email.
"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."