summaryrefslogtreecommitdiff
path: root/issues/database-not-responding.gmi
diff options
context:
space:
mode:
authorPjotr Prins2021-07-25 11:19:18 +0200
committerPjotr Prins2021-07-25 11:19:18 +0200
commit5fd0df92b333b4d4bab75ac719badd451d9efc8e (patch)
tree165d58bae17eca1e62429f6749251827c6c5165d /issues/database-not-responding.gmi
parentad44988918a2271cae03becc4e0f2729017eb0d5 (diff)
downloadgn-gemtext-5fd0df92b333b4d4bab75ac719badd451d9efc8e.tar.gz
Issue added
Diffstat (limited to 'issues/database-not-responding.gmi')
-rw-r--r--issues/database-not-responding.gmi13
1 files changed, 13 insertions, 0 deletions
diff --git a/issues/database-not-responding.gmi b/issues/database-not-responding.gmi
new file mode 100644
index 0000000..c8e752b
--- /dev/null
+++ b/issues/database-not-responding.gmi
@@ -0,0 +1,13 @@
+# Mariadb table locked
+
+Arthur reports: MariaDB is not responding Saturday, July 24 2021 at 10:48 pm. I tried to enter data to the table ProbeSetXRef.pValue and when normally takes few seconds, now is more than 10 minutes without completion/responding.
+
+Zach: before restarting the table can you check the status first?
+
+=> https://mariadb.com/kb/en/show-table-status/
+
+some ideas here
+
+=> https://dba.stackexchange.com/questions/98725/mariadb-innodb-what-to-do-on-locks-in-status-log-but-no-locked-table-found
+
+we are still using MyISAM for these tables: a switch to InnoDB may help.