Add notes for 2020-06-04

This commit is contained in:
2020-06-06 13:33:23 +03:00
parent d8ae82cf85
commit 4bde626ed4
25 changed files with 61 additions and 32 deletions

View File

@ -90,7 +90,7 @@ java.lang.NullPointerException
```
$ time chrt -i 0 ionice -c2 -n7 nice -n19 dspace index-discovery -b
...
real 125m37.423s
user 11m20.312s
sys 3m19.965s
@ -102,6 +102,7 @@ sys 3m19.965s
- I ran all system updates on the server (linode18) and rebooted it
- After it came back up I had to restart Tomcat five times before all Solr statistics cores came up properly
- Unfortunately this means that the Tomcat JDBC pooling via JNDI doesn't work, so we're using only the 30 connections reserved for the DSpace CLI from DSpace's own internal pool
- Perhaps our previous issues with the database pool from a few years ago will be less now that we have much more aggressive blocking and rate limiting of bots in nginx
- I will also import a fresh database snapshot from CGSpace and check if I can map the item in my local environment
- After importing and forcing a full reindex locally I can see the item in search and in the item mapper
- Abenet sent another message about two users who are having issues with submission, and I see the number of locks in PostgreSQL has sky rocketed again as of a few days ago:
@ -114,5 +115,18 @@ sys 3m19.965s
![PostgreSQL locks year](/cgspace-notes/2020/06/postgres_locks_ALL-year.png)
- I think I need to just leave this as is with the DSpace default JDBC driver for now, but perhaps I could also downgrade the Tomcat version (I deployed Tomcat 7.0.103 in March, so perhaps that's relevant)
- Also, I'll start *another* full reindexing to see if the issue with mapping is somehow also resolved now that the database connections are working better
- Perhaps related, but this one finished much faster:
```
$ time chrt -i 0 ionice -c2 -n7 nice -n19 dspace index-discovery -b
real 101m41.195s
user 10m9.569s
sys 3m13.929s
```
- Unfortunately the item is still not showing up in the item mapper...
- Something happened to AReS Explorer (linode20) so I ran all system updates and rebooted it
<!-- vim: set sw=2 ts=2: -->