Hey,
Thanks for the reply, this helped me very much.
Kind Regards,
Aviel Buskila.
בתאריך 17 באוג' 2015 08:49, "Jony Cohen" כתב:
> Hi,
> The clone command just clones the data from node2 to node1, you need to
> also register it with the `force` option to override the old record. (as if
> you're b
Hi,
The clone command just clones the data from node2 to node1, you need to
also register it with the `force` option to override the old record. (as if
you're building a new replica node...)
see:
https://github.com/2ndQuadrant/repmgr#converting-a-failed-master-to-a-standby
Regards,
- Jony
On Su
Hey,
I think I know what the problem is,
after the first failover when I clone the old master to be standby with the
'repmgr standby clone' command it seems that nothing updates the repl_nodes
table with the new standby in my cluster so on the next failover the
repmgrd is failed to find a new upcom
hey,
I have tried to set the configuration all over again, now the status of
'repl_nodes' before the failover is:
id | type | upstream_node_id | cluster | name | conninfo | priority | active
+-+---++--+---
El 14/08/15 a las 04:14, Aviel Buskila escribió:
> Hey,
> yes I did .. and still it wont fail back..
Can you send over the output of "repmgr cluster show" before and after
the failover process?
The output of SELECT * FROM repmgr_schema.repl_nodes; after the failover
(you need to change repmgr_sch
Hey,
yes I did .. and still it wont fail back..
2015-08-13 16:23 GMT+03:00 Jony Vesterman Cohen :
> Hi, did you make the old master follow the new one using repmgr?
>
> It doesn't update itself automatically...
> From the looks of it repmgr thinks you have 2 masters - the old one
> offline and th
Hi Aviel,
you can use the 'show cluster' command to see the repmgr state before you
do the 2nd failover - make sure the node1 is indeed marked as replica.
After a failover the Master doesn't automatically attach to the new master
- you need to point him as a slave (standby follow - if possible...)
