From: Dobrica Pavlinusic <dpavlin@rot13.org>
Date: Wed, 23 Aug 2017 07:05:08 +0000 (+0200)
Subject: test killing slave, recovery, killing master
X-Git-Url: http://git.rot13.org/?p=pgpool-online-recovery;a=commitdiff_plain;h=7faf06f9eb74f1444acefd6845b091ad055c2485

test killing slave, recovery, killing master
---

diff --git a/README.md b/README.md
index 603e386..1ddcfcc 100644
--- a/README.md
+++ b/README.md
@@ -28,11 +28,11 @@ If you edited local files, push changes to all nodes using:
 
 make push
 
-To restart all services (pgoool and postgresql) do:
+To restart pgpool (and cleanup it's state) do:
 
 make restart
 
-If you want to see systemd status of pgpool and replication just type:
+If you want to see systemd status of services just type:
 
 make status
 
@@ -40,11 +40,21 @@ make status
 Now you can start './t/80-insert-test.sh' in one terminal to create insert and select load on cluster and
 kill one of nodes with 'echo b > /proc/sysrq-trigger'
 
-To issue online recovery, you can use
+For example, kill slave:
+
+ssh root@10.200.1.62 'echo b > /proc/sysrq-trigger'
+
+pgpool should detect broken back-end and remove it.
+You can verify that using just 'make' and see that one node is down.
+To issue online recovery, you can use:
 
 make fix
 
+now, try to kill master:
+
+ssh root@10.200.1.61 'echo b > /proc/sysrq-trigger'
 
+FIXME: pgpool is stuck and needs to be restarted
 
 
 If installing on existing streaming replication you will need to tell pgpool where current master is with: