alanorth/cgspace-notes
1
0
Fork 0
mirror of https://github.com/alanorth/cgspace-notes.git synced 2024-11-16 11:57:03 +01:00
Code Issues Projects Releases Wiki Activity

Update notes for 2016-09-07

Browse Source
This commit is contained in:
Alan Orth 2016-09-07 16:31:00 +03:00
parent 49c9cc6b48
commit 598a53f2c0
Signed by: alanorth
GPG Key ID: 0FB860CC9C45B1B9
4 changed files with 39 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/2016-09.md
View File

@ -174,3 +174,12 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
- Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads - Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads
- I suggest we disable our nightly manual vacuum task, as we're a mostly read workload, and I'd rather stick as close to the documentation as possible since we haven't done any testing/observation of PostgreSQL - I suggest we disable our nightly manual vacuum task, as we're a mostly read workload, and I'd rather stick as close to the documentation as possible since we haven't done any testing/observation of PostgreSQL
- See: https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html - See: https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html
- CGSpace went down and the error seems to be the same as always (lately):
```
2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
...
```
- Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat

10
public/2016-09/index.html
View File

@ -278,6 +278,16 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
<li>Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads</li> <li>Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads</li>
<li>I suggest we disable our nightly manual vacuum task, as we&rsquo;re a mostly read workload, and I&rsquo;d rather stick as close to the documentation as possible since we haven&rsquo;t done any testing/observation of PostgreSQL</li> <li>I suggest we disable our nightly manual vacuum task, as we&rsquo;re a mostly read workload, and I&rsquo;d rather stick as close to the documentation as possible since we haven&rsquo;t done any testing/observation of PostgreSQL</li>
<li>See: <a href="https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html">https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html</a></li> <li>See: <a href="https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html">https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html</a></li>
<li>CGSpace went down and the error seems to be the same as always (lately):</li>
</ul>
<pre><code>2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
...
</code></pre>
<ul>
<li>Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat</li>
</ul> </ul>
</section> </section>

10
public/index.xml
View File

@ -216,6 +216,16 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
&lt;li&gt;Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads&lt;/li&gt; &lt;li&gt;Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads&lt;/li&gt;
&lt;li&gt;I suggest we disable our nightly manual vacuum task, as we&amp;rsquo;re a mostly read workload, and I&amp;rsquo;d rather stick as close to the documentation as possible since we haven&amp;rsquo;t done any testing/observation of PostgreSQL&lt;/li&gt; &lt;li&gt;I suggest we disable our nightly manual vacuum task, as we&amp;rsquo;re a mostly read workload, and I&amp;rsquo;d rather stick as close to the documentation as possible since we haven&amp;rsquo;t done any testing/observation of PostgreSQL&lt;/li&gt;
&lt;li&gt;See: &lt;a href=&#34;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&#34;&gt;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&lt;/a&gt;&lt;/li&gt; &lt;li&gt;See: &lt;a href=&#34;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&#34;&gt;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;CGSpace went down and the error seems to be the same as always (lately):&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
...
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat&lt;/li&gt;
&lt;/ul&gt; &lt;/ul&gt;
</description> </description>
</item> </item>

10
public/tags/notes/index.xml
View File

@ -216,6 +216,16 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
&lt;li&gt;Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads&lt;/li&gt; &lt;li&gt;Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads&lt;/li&gt;
&lt;li&gt;I suggest we disable our nightly manual vacuum task, as we&amp;rsquo;re a mostly read workload, and I&amp;rsquo;d rather stick as close to the documentation as possible since we haven&amp;rsquo;t done any testing/observation of PostgreSQL&lt;/li&gt; &lt;li&gt;I suggest we disable our nightly manual vacuum task, as we&amp;rsquo;re a mostly read workload, and I&amp;rsquo;d rather stick as close to the documentation as possible since we haven&amp;rsquo;t done any testing/observation of PostgreSQL&lt;/li&gt;
&lt;li&gt;See: &lt;a href=&#34;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&#34;&gt;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&lt;/a&gt;&lt;/li&gt; &lt;li&gt;See: &lt;a href=&#34;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&#34;&gt;https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;CGSpace went down and the error seems to be the same as always (lately):&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;code&gt;2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
...
&lt;/code&gt;&lt;/pre&gt;
&lt;ul&gt;
&lt;li&gt;Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat&lt;/li&gt;
&lt;/ul&gt; &lt;/ul&gt;
</description> </description>
</item> </item>