summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/consistency.txt2
-rw-r--r--docs/databases.txt8
-rw-r--r--docs/kickstart.txt1
-rw-r--r--docs/troubleshooting.txt11
4 files changed, 22 insertions, 0 deletions
diff --git a/docs/consistency.txt b/docs/consistency.txt
index c648a9a..090f0a3 100644
--- a/docs/consistency.txt
+++ b/docs/consistency.txt
@@ -19,6 +19,8 @@ Storage
./gluster.sh info all_heketi
- Check available storage space on system partition and LVM volumes (docker, heketi, ands)
Run 'df -h' and 'lvdisplay' on each node
+ - Check status of hardware raids
+ /opt/MegaRAID/storcli/storcli64 /c0/v0 show all
Networking
==========
diff --git a/docs/databases.txt b/docs/databases.txt
index 7f8468e..aa58a2e 100644
--- a/docs/databases.txt
+++ b/docs/databases.txt
@@ -9,8 +9,16 @@
Galera INNODB 3.5 MB/s fast 3 x 200% - Should be perfect, but I am not sure about automatic recovery...
Galera/Hostnet INNODB 4.6 MB/s fast 3 x 200% -
MySQL Slaves INNODB 5-6 MB/s fast 2 x 250% - Available data is HA, but caching is not. We can easily turn the slave to master.
+ MySQL S.+Zlib INNODB + ZLib 2-4 MB/s normal 2 x 300% - At about 35% compression level.
DRBD MyISAM (no logs) 4-6 exp. ? I expect it as an faster option, but does not fit the OpenShift concept that well.
+
+Optimized (Large buffers, transactions in ADEI, etc.)
+ Method Database Perf (Mst/Slv) Clnt/Cache MySQL Gluster HA
+ MySQL Slaves INNODB 12 / 14 MB/s fast 600-800% -
+
+
+
Gluster is a way too slow for anything. If node crashes, MyISAM tables may be left in corrupted state. The recovery will take ages to complete.
The Gluster/Block is faster, but HA suffers. The volume is attached to the pod running on crashed node. It seems not detached automatically until
diff --git a/docs/kickstart.txt b/docs/kickstart.txt
index fb2b5da..1331542 100644
--- a/docs/kickstart.txt
+++ b/docs/kickstart.txt
@@ -8,6 +8,7 @@ Troubleshooting
vgdestroy <vgname>
* Destroy rogue device mapper devices
dmsetup info -C
+ dmsetup remove_all
dmsetup remove <name>
\ No newline at end of file
diff --git a/docs/troubleshooting.txt b/docs/troubleshooting.txt
index ef3c206..ae43c52 100644
--- a/docs/troubleshooting.txt
+++ b/docs/troubleshooting.txt
@@ -244,6 +244,17 @@ Storage
or again we can compare lvm volumes which are used by Gluster bricks and which are not. The later
ones should be cleaned up. Again there is the script.
+MySQL
+=====
+ - MySQL may stop replicating from the master. There is some kind of deadlock in multi-threaded SLAVE SQL.
+ This can be seen by exexuting (which should show a lot of slave threads waiting on coordinator to provide
+ load).
+ SHOW PROCESSLIST;
+ The remedy is to restart slave MySQL with 'slave_parallel_workers=0', give it a time to go, and then
+ restart back in the standard multithreading mode.
+
+
+
Performance
===========
- To find if OpenShift restricts the usage of system resources, we can 'rsh' to container and check