On Sat, Jun 1, 2019 at 7:34 PM Adrian Klaver <adrian.kla...@aklaver.com>
wrote:
> On 6/1/19 4:22 PM, Tom K wrote:
> >
> >
>
> >
> > Looks like this crash was far more catastrophic then I thought. By the
> > looks of things, thinking on psql02 would be my best bet.
> >
>
> The more I look at it the more I think the replication was not doing
> what you thought it was doing. That psql02 was the primary and that
> psql01 and psql03 where out of sync and/or defunct standbys.
>
Now that I look at the files myself, that's the conclusion I was coming to
myself. Sample config:
[root@psql02 base]# cat /etc/patroni.yml
scope: postgres
namespace: /db/
name: postgresql1
restapi:
listen: 192.168.0.124:8008
connect_address: 192.168.0.124:8008
etcd:
host: 192.168.0.124:2379
bootstrap:
dcs:
ttl: 30
loop_wait: 10
retry_timeout: 10
maximum_lag_on_failover: 1048576
postgresql:
use_pg_rewind: true
initdb:
- encoding: UTF8
- data-checksums
pg_hba:
- host replication replicator 127.0.0.1/32 md5
- host replication replicator 192.168.0.108/0 md5
- host replication replicator 192.168.0.124/0 md5
- host replication replicator 192.168.0.118/0 md5
- host all all 0.0.0.0/0 md5
users:
admin:
password: admin
options:
- createrole
- createdb
postgresql:
listen: 192.168.0.124:5432
bin_dir: /usr/pgsql-10/bin
connect_address: 192.168.0.124:5432
data_dir: /data/patroni
pgpass: /tmp/pgpass
unix_socket_directories: /data/patroni
authentication:
replication:
username: replicator
password: rep-pass
superuser:
username: postgres
password: <SECRET>
parameters:
unix_socket_directories: '.'
tags:
nofailover: false
noloadbalance: false
clonefrom: false
nosync: false
[root@psql02 base]#
Or perhaps when the system crashed, the filesystem check simply moved the
folders out due to corruption.
>
>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>
