DSpace version 4.2

When I run

I see

./dspace stats-util --shard-solr-index

Moving: 70249 into core statistics-2012
Exception: version conflict for 4f5e5c83-4369-467e-8332-fb222e6896ce
expected=1482607080797896704 actual=-1
org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
version conflict for 4f5e5c83-4369-467e-8332-fb222e6896ce
expected=1482607080797896704 actual=-1

As for the record in question, I have:

<response>
<lst name="responseHeader">
<int name="status">0</int>
<int name="QTime">1</int>
<lst name="params">
<str name="q">uid:4f5e5c83-4369-467e-8332-fb222e6896ce</str>
<str name="fl">time,uid,_version_</str>
</lst>
</lst>
<result name="response" numFound="1" start="0">
<doc>
<str name="uid">4f5e5c83-4369-467e-8332-fb222e6896ce</str>
<date name="time">2013-12-26T17:02:32.07Z</date>
<long name="_version_">1482607080797896704</long>
</doc>
</result>
</response>

Where is the conflict?

More info: I am running my solr instance on a different server from my
DSpace instance.  Also, for some reason, I do not see a _version_
field in about half of my solr records... (not including this one
obviously...)

Has anyone else had similar problems with sharding?  This seems to be
possibly related to DS-2212?  But I do run optimize on  daily basis,
and I have attempted to manually optimize (as suggested there) as
well.

Thanks in advance!
Bill

------------------------------------------------------------------------------
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

Reply via email to