HGDB集群(安全版)repmgr手动切换主备库

文章目录

文档用途

介绍HGDB集群(安全版)repmgr手动主备切换的方法,以及使用过程中的注意事项。

详细信息

repmgr集群主备切换使用的是repmgr standby switchover工具,它的作用是将备库提升为主库,所以该命令只能在备库上执行。

操作步骤;

①检查集群状态

sql 复制代码
 ID | Name          | Role    | Status    | Upstream      | Location | Priority | Replication lag | Last replayed LSN
----+---------------+---------+-----------+---------------+----------+----------+-----------------+-------------------
 1  | x.x.197.7 | standby |   running | x.x.197.8 | default  | 100      | 0 bytes         | 0/5007BD8
 2  | x.x.197.8 | primary | * running |               | default  | 100      | n/a             | none

②在备库上执行repmgr standby switchover

sql 复制代码
[root@ha1 .ssh]# repmgr standby  switchover

注意:

xml 复制代码
-------------------------------------------
Login User: sysdba
Login time: 2020-08-18 17:01:08.779533+08
Login Address: ha1
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------
NOTICE: executing switchover on node "x.x.197.7" (ID: 1)

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:08.768112+08
Login Address: ha1
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:09.329686+08
Login Address: ha2
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:09.36233+08
Login Address: ha2
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:09.379521+08
Login Address: ha1
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:09.367691+08
Login Address: ha1
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08


-------------------------------------------

NOTICE: local node "x.x.197.7" (ID: 1) will be promoted to primary; current primary "x.x.197.8" (ID: 2) will be demoted to standby
NOTICE: stopping current primary node "x.x.197.8" (ID: 2)

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:09.525191+08
Login Address: ha2
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08


-------------------------------------------

NOTICE: issuing CHECKPOINT
DETAIL: executing server command "/opt/HighGo4.3.4.9-see/bin/pg_ctl  -D '/opt/HighGo4.3.4.9-see/data' -W -m fast stop"
INFO: checking for primary shutdown; 1 of 60 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 2 of 60 attempts ("shutdown_check_timeout")
NOTICE: current primary has been cleanly shut down at location 0/5007D60
Warning: Executing wildcard deletion to stay compatible with old scripts.
         Explicitly specify the prefix length (x.x.197.110/32) to avoid this warning.
         This special behaviour is likely to disappear in further releases,
         fix your scripts!
NOTICE: promoting standby to primary
DETAIL: promoting server "x.x.197.7" (ID: 1) using "/opt/HighGo4.3.4.9-see/bin/pg_ctl  -w -D '/opt/HighGo4.3.4.9-see/data' promote"
waiting for server to promote.... 完成
server promoted
NOTICE: waiting up to 60 seconds (parameter "promote_check_timeout") for promotion to complete
NOTICE: STANDBY PROMOTE successful
DETAIL: server "x.x.197.7" (ID: 1) was successfully promoted to primary

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:11.342397+08
Login Address: ha2
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08


-------------------------------------------

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:11.369129+08
Login Address: ha2
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08

-------------------------------------------

注意:

xml 复制代码
-------------------------------------------
Login User: sysdba
Login time: 2020-08-18 17:01:11.383934+08
Login Address: ha2
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------
INFO: local node 2 can attach to rejoin target node 1
DETAIL: local node's recovery point: 0/5007D60; rejoin target node's fork point: 0/5007DD0
NOTICE: setting node 2's upstream to node 1
WARNING: unable to ping "host=x.x.197.8 user=sysdba dbname=highgo password=4t65da7s port=5866 connect_timeout=2"
DETAIL: PQping() returned "PQPING_NO_RESPONSE"
NOTICE: starting server using "/opt/HighGo4.3.4.9-see/bin/pg_ctl  -w -D '/opt/HighGo4.3.4.9-see/data' start"

注意:

xml 复制代码
-------------------------------------------


Login User: sysdba
Login time: 2020-08-18 17:01:11.662335+08
Login Address: ha2
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------
NOTICE: NODE REJOIN successful
DETAIL: node 2 is now attached to node 1

注意:

xml 复制代码
-------------------------------------------

Login User: sysdba
Login time: 2020-08-18 17:01:11.691733+08
Login Address: ha1
Last Login Status: SUCCESS
Login Failures: 0
Valied Until: 2020-08-25 14:03:03+08
-------------------------------------------
NOTICE: switchover was successful
DETAIL: node "x.x.197.7" is now primary and node "x.x.197.8" is attached as standby
NOTICE: STANDBY SWITCHOVER has completed successfully

③检查集群状态

sql 复制代码
 ID | Name          | Role    | Status    | Upstream      | Location | Priority | Replication lag | Last replayed LSN
----+---------------+---------+-----------+---------------+----------+----------+-----------------+-------------------
 1  | x.x.197.7 | primary | * running |               | default  | 100      | n/a             | none
 2  | x.x.197.8 | standby |   running | x.x.197.7 | default  | 100      | 0 bytes         | 0/5009640

可以发现数据库的主备已经切换完毕。

注意事项:

1.实现主备切换需要进行互信操作,不然会报错。

WARNING: unable to connect to remote host "x.x.197.8" via SSH

ERROR: unable to connect via SSH to host "x.x.197.8", user ""

2.在切换时 repmgrd 不应该在 repmgr.conf中启用 failover=automatic或启动repmgrd,否则repmgrd守护进程可能尝试并自行提升备用数据库。

3.数据库的环境变量应该设置在.bashrc中否则会报错找不到repmgr。

ERROR: unable to execute "repmgr" on "x.x.197.8"

HINT: check "pg_bindir" is set to the correct path in "repmgr.conf"; current value: "/opt/HighGo4.3.4.9-see/bin"

4.建议在切换之前加上--dry-run,可以测试是否切换成功而不进行切换,测试成功后再进行正式切换。

相关推荐
陌上丨1 小时前
Redis的Key和Value的设计原则有哪些?
数据库·redis·缓存
曹牧1 小时前
Spring Boot:如何测试Java Controller中的POST请求?
java·开发语言
Hello.Reader1 小时前
Flink ZooKeeper HA 实战原理、必配项、Kerberos、安全与稳定性调优
安全·zookeeper·flink
AI_56781 小时前
AWS EC2新手入门:6步带你从零启动实例
大数据·数据库·人工智能·机器学习·aws
ccecw1 小时前
Mysql ONLY_FULL_GROUP_BY模式详解、group by非查询字段报错
数据库·mysql
JH30731 小时前
达梦数据库与MySQL的核心差异解析:从特性到实践
数据库·mysql
数据知道2 小时前
PostgreSQL 核心原理:如何利用多核 CPU 加速大数据量扫描(并行查询)
数据库·postgresql
爬山算法2 小时前
Hibernate(90)如何在故障注入测试中使用Hibernate?
java·后端·hibernate
智驱力人工智能2 小时前
小区高空抛物AI实时预警方案 筑牢社区头顶安全的实践 高空抛物检测 高空抛物监控安装教程 高空抛物误报率优化方案 高空抛物监控案例分享
人工智能·深度学习·opencv·算法·安全·yolo·边缘计算
kfyty7252 小时前
集成 spring-ai 2.x 实践中遇到的一些问题及解决方案
java·人工智能·spring-ai