Thanks, Terry. I remember looking at the pull request for DS-3458[0] in
early 2017 but eventually gave up after trying to cherry-pick all the
required commits into my 5.5 branch. I will think about taking a look in
the short term, but in the long term I need to start evaluating moving to
5.7 (we us
Alan,
The issue that you are reporting does not sound like the same issue that
was addressed in DSpace 5.7 and 6.1.
In DSpace 6.0, running the sharding process prevented tomcat from starting
up properly. While addressing that serious bug, a number of smaller issues
related to statistics import a
Hi, Christian. I just tried again with 4096m heap size and the error is the
same. I think the problem is indeed related to the Solr optimistic
concurrency version conflicts that are addressed in DSpace 5.7 and DSpace
6.1.
- 5.7: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.7+Status
-
Hi Alan,
have you tried increasing the Java Heap Space?
On my local development machine (DSpace 6.2) the command did not run
when Heap Space was only 1 GB but did work with 4GB.
Like this:
sudo -u tomcat7 JAVA_OPTS="-Xmx4024M -Xms1024M -Dfile.encoding=UTF-8"
/opt/dspace-kops/bin/dspace stats-
@Mark, I looked in DSpace's solr.log and see that the new Solr core is
created, then it does some stuff and eventually closes it without an error.
Neither Tomcat's catalina.out nor localhost.log have any errors around the
time I attempted to shard on my local development machine. There might be a
h
Alan,
There were some bug fixes to the Solr Sharding process in DSpace 5.7. See
https://wiki.duraspace.org/display/~terrywbrady/Statistics+Import+Export+Issues
for details.
I am running DSpace 5.8 and I was able to shard successfully.
https://wiki.duraspace.org/display/DSDOC5x/SOLR+Statistics+Ma
Does the server log anything interesting? It seems to be dropping the
connection. I suspect a timeout of some sort, on the server side.
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiv
Hello,
Another year has passed and we have yet another failure of the yearly Solr
statistics sharding cron job. The error is same each year, and has never
completed successfully ONCE since we started using Solr. I'm hoping someone
could shed light on this issue. We are using DSpace 5.5 with Tomcat
