Update notes for 2018-09-26

content/posts/2018-09.md

@@ -528,5 +528,24 @@ Indexing item downloads (page 260 of 260)
 - Linode emailed to say that CGSpace (linode18) was using 30Mb/sec of outward bandwidth for two hours around midnight
 - I don't see anything unusual in the nginx logs, so perhaps it was the cron job that syncs the Solr database to Amazon S3?
 - It could be that the bot purge yesterday changed the core significantly so there was a lot to change?
+- I don't see any drop in JVM heap size in CGSpace's munin stats since I did the Solr cleanup, but this looks pretty good:
+
+![Tomcat max processing time week](/cgspace-notes/2018/09/tomcat_maxtime-week.png)
+
+- I will have to keep an eye on that over the next few weeks to see if things stay as they are
+- I did a batch replacement of the access rights with my [fix-metadata-values.py](https://gist.github.com/alanorth/df92cbfb54d762ba21b28f7cd83b6897) script on DSpace Test:
+
+```
+$ ./fix-metadata-values.py -i /tmp/fix-access-status.csv -db dspace-u dspace-p 'fuuu' -f cg.identifier.status -t correct -m 206
+```
+
+- This changes "Open Access" to "Unrestricted Access" and "Limited Access" to "Restricted Access"
+- After that I did a full Discovery reindex:
+
+```
+$ time schedtool -D -e ionice -c2 -n7 nice -n19 dspace index-discovery -b
+```
+
+- I told Peter it's better to do the access rights before the usage rights because the git branches are conflicting with each other and it's actually a pain in the ass to keep changing the values as we discuss, rebase, merge, fix conflicts...
 
 <!-- vim: set sw=2 ts=2: -->