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
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
Thank you Bill and David. I'll take a look at `pg_buffercache ` and explain
with buffers.
---
What problem are you seeing?
---
I don't have a problem at the moment.
---
What is your performance requirement, and what is the observed
performance?
On 13 August 2015 at 23:52, Wayne E. Seguin wayneeseg...@gmail.com wrote:
The context of this is using BDR to implement a HA solution where we have
one node getting all connections at a time, if the node fails we move all
connections to another node. (eg. only one node gets all connections at
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
