alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2025-01-27 05:49:12 +01:00
Code Issues Projects Releases Wiki Activity

Add notes for 2016-12-28

Browse Source
This commit is contained in:
Alan Orth
2016-12-28 12:35:40 +02:00
parent 4684bf3290
commit 8d266b4f50
28 changed files with 299 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
public/2016-12/index.html
View File

@ -30,7 +30,7 @@
<meta itemprop="dateModified" content="2016-12-02T10:43:00&#43;03:00" />
<meta itemprop="wordCount" content="3947">
<meta itemprop="wordCount" content="4078">
@ -54,7 +54,7 @@
<meta name="generator" content="Hugo 0.17" />
<meta name="generator" content="Hugo 0.18" />
<base href="https://alanorth.github.io/cgspace-notes/">
@ -83,6 +83,14 @@
<a class="nav-link " href="https://alanorth.github.io/cgspace-notes/">Home</a>
<a class="nav-link" href="https://alanorth.github.io/cgspace-notes/">CGSpace Notes</a>
<a class="nav-link" href="https://alanorth.github.io/cgspace-notes/tags/notes/">Notes</a>
<a class="nav-link" href="https://alanorth.github.io/cgspace-notes/post/">Posts</a>
<a class="nav-link" href="https://alanorth.github.io/cgspace-notes/tags/">Tags</a>
</nav>
</div>
@ -851,6 +859,23 @@ $ exit
<pre><code>$ [dspace]/bin/dspace metadata-export -a -f /tmp/iita.csv -i 10568/68616
</code></pre>
<h2 id="2016-12-28">2016-12-28</h2>
<ul>
<li>We&rsquo;ve been getting two alerts per day about CPU usage on the new server from Linode</li>
<li>These are caused by the batch jobs for Solr etc that run in the early morning hours</li>
<li>The Linode default is to alert at 90% CPU usage for two hours, but I see the old server was at 150%, so maybe we just need to adjust it</li>
<li>Speaking of the old server (linode01), I think we can decommission it now</li>
<li>I checked the S3 logs on the new server (linode18) to make sure the backups have been running and everything looks good</li>
<li>In other news, I was looking at the Munin graphs for PostgreSQL on the new server and it looks slightly worrying:</li>
</ul>
<p><img src="2016/12/postgres_size_ALL-week.png" alt="munin postgres stats" /></p>
<ul>
<li>I will have to check later why the size keeps increasing</li>
</ul>