Update notes for 2018-09-26

This commit is contained in:
2018-09-26 17:19:13 +03:00
parent f6f25e1284
commit 3890af5e02
8 changed files with 50 additions and 1196 deletions

View File

@ -18,7 +18,7 @@ I’m testing the new DSpace 5.8 branch in my Ubuntu 18.04 environment and I
" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2018-09/" /><meta property="article:published_time" content="2018-09-02T09:55:54&#43;03:00"/>
<meta property="article:modified_time" content="2018-09-26T03:29:56&#43;03:00"/>
<meta property="article:modified_time" content="2018-09-26T09:54:45&#43;03:00"/>
<meta name="twitter:card" content="summary"/>
<meta name="twitter:title" content="September, 2018"/>
<meta name="twitter:description" content="2018-09-02
@ -41,9 +41,9 @@ I&rsquo;m testing the new DSpace 5.8 branch in my Ubuntu 18.04 environment and I
"@type": "BlogPosting",
"headline": "September, 2018",
"url": "https://alanorth.github.io/cgspace-notes/2018-09/",
"wordCount": "4135",
"wordCount": "4288",
"datePublished": "2018-09-02T09:55:54&#43;03:00",
"dateModified": "2018-09-26T03:29:56&#43;03:00",
"dateModified": "2018-09-26T09:54:45&#43;03:00",
"author": {
"@type": "Person",
"name": "Alan Orth"
@ -716,6 +716,29 @@ Indexing item downloads (page 260 of 260)
<li>Linode emailed to say that CGSpace (linode18) was using 30Mb/sec of outward bandwidth for two hours around midnight</li>
<li>I don&rsquo;t see anything unusual in the nginx logs, so perhaps it was the cron job that syncs the Solr database to Amazon S3?</li>
<li>It could be that the bot purge yesterday changed the core significantly so there was a lot to change?</li>
<li>I don&rsquo;t see any drop in JVM heap size in CGSpace&rsquo;s munin stats since I did the Solr cleanup, but this looks pretty good:</li>
</ul>
<p><img src="/cgspace-notes/2018/09/tomcat_maxtime-week.png" alt="Tomcat max processing time week" /></p>
<ul>
<li>I will have to keep an eye on that over the next few weeks to see if things stay as they are</li>
<li>I did a batch replacement of the access rights with my <a href="https://gist.github.com/alanorth/df92cbfb54d762ba21b28f7cd83b6897">fix-metadata-values.py</a> script on DSpace Test:</li>
</ul>
<pre><code>$ ./fix-metadata-values.py -i /tmp/fix-access-status.csv -db dspace-u dspace-p 'fuuu' -f cg.identifier.status -t correct -m 206
</code></pre>
<ul>
<li>This changes &ldquo;Open Access&rdquo; to &ldquo;Unrestricted Access&rdquo; and &ldquo;Limited Access&rdquo; to &ldquo;Restricted Access&rdquo;</li>
<li>After that I did a full Discovery reindex:</li>
</ul>
<pre><code>$ time schedtool -D -e ionice -c2 -n7 nice -n19 dspace index-discovery -b
</code></pre>
<ul>
<li>I told Peter it&rsquo;s better to do the access rights before the usage rights because the git branches are conflicting with each other and it&rsquo;s actually a pain in the ass to keep changing the values as we discuss, rebase, merge, fix conflicts&hellip;</li>
</ul>
<!-- vim: set sw=2 ts=2: -->