Deployment script ./t/1-init-cluster.sh assumes that management machine from which it's run is 10.200.1.1
which is added in pg_hba.conf as authorized to be able to deploy cluster. It also assumes that management machine
-has ssh access to nodes of clustetr using ssh keys or you will need to type passwords multiple times.
+has ssh access to nodes of cluster using ssh keys or you will need to type passwords multiple times, so use
+ssh-copy-id root@10.200.1.6[12] to install them.
+
+In it's current form, scripts assume that postgresql-9.6 is allready installed on machines while pgpool isn't.
+It doesn't metter if pgpool is allready there, but postgresql-9.6 must be allready installed.
You can run cluster creation it with:
make init
+
This will destroy all databases on all nodes, archive logs, etc, so don't do this if you need your old data later.
On the other hand this will also create setup whole cluster, and you can examine it's status using:
make
+
+In output you can see both nodes, and their status, if it looks ok, test cluster with:
+
+./t/3-test.sh
+
+
If you edited local files, push changes to all nodes using:
make push
cp /usr/sbin/arping /etc/pgpool-II/sbin/
chmod -v 4755 /etc/pgpool-II/sbin/*
- rpm -q pgpool-II-pg96 || yes | ssh root@$1 yum install http://www.pgpool.net/yum/rpms/3.6/redhat/rhel-7-x86_64/pgpool-II-pg96-3.6.5-1pgdg.rhel7.x86_64.rpm
+ rpm -q pgpool-II-pg96 || yes | yum install http://www.pgpool.net/yum/rpms/3.6/redhat/rhel-7-x86_64/pgpool-II-pg96-3.6.5-1pgdg.rhel7.x86_64.rpm
systemctl enable pgpool