Page History

...

1. In DSpace 6x, tomcat does not properly restart after a statistics shard has been created.  

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-3457

   2. This behavior has been verified at 3 instances (Georgetown, UCLA and ?). Tom Desair has volunteered to try to reproduce this error.
   3. How to test
      1. Back up your solr directory
      2. If you have statistics from 2016 or earlier in your statistics repository
         1. Run stats-util -s to shard last years records into a shard
      3. If you do not have statistics from 2016 in your repository
         1. See the instructions related to testing PRs 1623/1624 to force old stats records (from a prior year) into your statistics repository
         2. Run stats-util -s
      4. Restart tomcat
      5. Tomcat will not restart properly.  The tomcat process will not resond to a stop request.
      6. To resolve this issue
         1. kill -9 your tomcat process
         2. delete the statistics shard directories
         3. restart tomcat
2. In DSpace 5x and 6x, the owningComm field is corrupted by the sharding process 

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key DS-3436

   2. Tom Desair has created a fix: https://github.com/DSpace/DSpace/pull/1613  While testing this fix, many of the other issues listed here have been discovered.
   3. Ultimately, we need the ability to repair statistics shards that contain a corrupted owningComm (perhaps via the solr-reindex-statistics command) 

While attempting to resolve this issue, a number of long standing challenges with the sharding process have become evident.

...