HGDB HAC集群导致时间线变化的操作演示

最新推荐文章于 2023-07-17 14:46:55 发布
最新推荐文章于 2023-07-17 14:46:55 发布
阅读量453 收藏
点赞数
分类专栏： Highgo DB 文章标签： 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lk_db/article/details/123570046
版权

（1）停止所有节点的HAC
[root@db data]# systemctl stop hghac-vip
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Replica | stopped |    |   unknown |
| hghacb | 192.168.80.112:5866 | Replica | stopped |    |   unknown |
| hghacc | 192.168.80.113:5866 | Replica | stopped |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
（2）启动节点1的HAC，此时时间线为26
[root@db data]# systemctl start hghac-vip
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Leader  | running | 26 |           |
| hghacb | 192.168.80.112:5866 | Replica | stopped |    |   unknown |
| hghacc | 192.168.80.113:5866 | Replica | stopped |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
（3）启动节点2的HAC，此时节点1时间线发生变化为27，备节点时间线同步主节点的
[root@db data]# --此时启动节点2的HAC
bash: --此时启动节点2的HAC: command not found...
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Leader  | running | 27 |           |
| hghacb | 192.168.80.112:5866 | Replica | running | 26 |        16 |
+--------+---------------------+---------+---------+----+-----------+
节点1数据库日志如下：
2022-03-18 10:42:31.837 CST,,,25636,"127.0.0.1:16450",6233f197.6424,1,"",2022-03-18 10:42:31 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=16450",,,,,,,,,""
2022-03-18 10:42:31.837 CST,,,25635,,6233f197.6423,2,,2022-03-18 10:42:31 CST,,0,WARNING,01000,"specified neither primary_conninfo nor restore_command",,"The database server will regularly poll the pg_wal subdirectory to check for files placed there.",,,,,,,""
2022-03-18 10:42:31.838 CST,,,25635,,6233f197.6423,3,,2022-03-18 10:42:31 CST,,0,LOG,00000,"entering standby mode",,,,,,,,,""
2022-03-18 10:42:31.847 CST,,,25635,,6233f197.6423,4,,2022-03-18 10:42:31 CST,1/0,0,LOG,00000,"consistent recovery state reached at 0/2F0000A0",,,,,,,,,""
2022-03-18 10:42:31.847 CST,,,25635,,6233f197.6423,5,,2022-03-18 10:42:31 CST,1/0,0,LOG,00000,"invalid record length at 0/2F0000A0: wanted 24, got 0",,,,,,,,,""
2022-03-18 10:42:31.851 CST,,,25631,,6233f197.641f,2,,2022-03-18 10:42:31 CST,,0,LOG,00000,"database system is ready to accept read only connections",,,,,,,,,""
2022-03-18 10:42:31.869 CST,"sysdba","highgo",25636,"127.0.0.1:16450",6233f197.6424,2,"",2022-03-18 10:42:31 CST,,0,FATAL,57P03,"the database system is starting up",,,,,,,,,""
2022-03-18 10:42:31.876 CST,,,25641,"127.0.0.1:16452",6233f197.6429,1,"",2022-03-18 10:42:31 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=16452",,,,,,,,,""
2022-03-18 10:42:31.892 CST,,,25643,"127.0.0.1:16456",6233f197.642b,1,"",2022-03-18 10:42:31 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=16456",,,,,,,,,""
2022-03-18 10:42:31.952 CST,,,25651,"127.0.0.1:16460",6233f197.6433,1,"",2022-03-18 10:42:31 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=16460",,,,,,,,,""
2022-03-18 10:42:31.969 CST,"sysdba","highgo",25651,"127.0.0.1:16460",6233f197.6433,2,"authentication",2022-03-18 10:42:31 CST,2/3,0,LOG,00000,"connection authorized: user=sysdba database=highgo application_name=Patroni SSL enabled (protocol=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256, compression=off)",,,,,,,,,""
2022-03-18 10:42:32.061 CST,,,25666,"127.0.0.1:16468",6233f198.6442,1,"",2022-03-18 10:42:32 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=16468",,,,,,,,,""
2022-03-18 10:42:32.075 CST,"sysdba","",25666,"127.0.0.1:16468",6233f198.6442,2,"authentication",2022-03-18 10:42:32 CST,3/1,0,LOG,00000,"replication connection authorized: user=sysdba SSL enabled (protocol=TLSv1.2, cipher=ECDHE-RSA-AES256-GCM-SHA384, bits=256, compression=off)",,,,,,,,,""
2022-03-18 10:42:32.087 CST,"sysdba","",25666,"127.0.0.1:16468",6233f198.6442,3,"idle",2022-03-18 10:42:32 CST,,0,LOG,00000,"disconnection: session time: 0:00:00.027 user=sysdba database= host=127.0.0.1 port=16468",,,,,,,,,""
2022-03-18 10:42:32.112 CST,,,25635,,6233f197.6423,6,,2022-03-18 10:42:31 CST,1/0,0,LOG,00000,"received promote request",,,,,,,,,""
2022-03-18 10:42:32.112 CST,,,25635,,6233f197.6423,7,,2022-03-18 10:42:31 CST,1/0,0,LOG,00000,"redo is not required",,,,,,,,,""
2022-03-18 10:42:32.116 CST,,,25635,,6233f197.6423,8,,2022-03-18 10:42:31 CST,1/0,0,LOG,00000,"selected new timeline ID: 27",,,,,,,,,""
2022-03-18 10:42:32.352 CST,,,25635,,6233f197.6423,9,,2022-03-18 10:42:31 CST,1/0,0,LOG,00000,"archive recovery complete",,,,,,,,,""
2022-03-18 10:42:32.363 CST,,,25635,,6233f197.6423,10,,2022-03-18 10:42:31 CST,1/0,0,LOG,00000,"Switchover the SSHA Role. Current is NONE",,,,,,,,,""
2022-03-18 10:42:32.365 CST,,,25637,,6233f197.6425,1,,2022-03-18 10:42:31 CST,,0,LOG,00000,"checkpoint starting: force",,,,,,,,,""
2022-03-18 10:42:32.369 CST,,,25631,,6233f197.641f,3,,2022-03-18 10:42:31 CST,,0,LOG,00000,"database system is ready to accept connections",,,,,,,,,""
2022-03-18 10:42:32.402 CST,,,25637,,6233f197.6425,2,,2022-03-18 10:42:31 CST,,0,LOG,00000,"checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.015 s, sync=0.001 s, total=0.038 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB",,,,,,,,,"

[root@db data]# --此时启动节点3的HAC
bash: --此时启动节点3的HAC: command not found...
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Leader  | running | 27 |           |
| hghacb | 192.168.80.112:5866 | Replica | running | 27 |         0 |
| hghacc | 192.168.80.113:5866 | Replica | running | 26 |        16 |
+--------+---------------------+---------+---------+----+-----------+
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Leader  | running | 27 |           |
| hghacb | 192.168.80.112:5866 | Replica | running | 27 |         0 |
| hghacc | 192.168.80.113:5866 | Replica | running | 27 |         0 |
+--------+---------------------+---------+---------+----+-----------+


（4）如果仅重启被节点2和备节点3的HAC服务，此时数据库时间线不变
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Leader  | running | 27 |           |
| hghacb | 192.168.80.112:5866 | Replica | stopped |    |   unknown |
| hghacc | 192.168.80.113:5866 | Replica | stopped |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
[root@db data]# --启动节点2 HAC
bash: --启动节点2: command not found...
[root@db data]# --启动节点3 HAC
bash: --启动节点3: command not found...
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+---（）-+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Leader  | running | 27 |           |
| hghacb | 192.168.80.112:5866 | Replica | running | 27 |         0 |
| hghacc | 192.168.80.113:5866 | Replica | running | 27 |         0 |
+--------+---------------------+---------+---------+----+-----------+

（5）HAC集群发生切换的时候，也会导致时间线的变化
[root@db data]# systemctl stop hghac-vip
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Replica | stopped |    |   unknown |
| hghacb | 192.168.80.112:5866 | Leader  | running | 28 |           |
| hghacc | 192.168.80.113:5866 | Replica | running |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Replica | stopped |    |   unknown |
| hghacb | 192.168.80.112:5866 | Leader  | running | 28 |           |
| hghacc | 192.168.80.113:5866 | Replica | running | 28 |         0 |
+--------+---------------------+---------+---------+----+-----------+
[root@db data]# systemctl start hghac-vip
[root@db data]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list
+ Cluster: ha (7072987311974756506) -----+---------+----+-----------+
| Member | Host                | Role    | State   | TL | Lag in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Replica | running | 28 |         0 |
| hghacb | 192.168.80.112:5866 | Leader  | running | 28 |           |
| hghacc | 192.168.80.113:5866 | Replica | running | 28 |         0 |
+--------+---------------------+---------+---------+----+-----------+

lk_db
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
hgdb HAC集群中，计划重新初始化数据库使用原集群配置的操作方法（二）
lk的窝
04-02 1102
续“hgdb HAC集群中，计划重新初始化数据库使用原集群配置的操作方法（一）” 1、停止所有节点的hghac服务并删除所有节点的data目录 [root@db ~]# systemctl stop hghac-vip [root@db hgdbdata]# rm -rf data/ [root@db2 ~]# systemctl stop hghac-vip [root@db2 hgdbdata]# rm -rf data/ [root@db3 ~]# systemctl stop hghac-vip
数据库PostrageSQL-热备
逍遥云恋
12-24 583
26.5. 热备 术语热备用来描述处于归档恢复或后备模式中的服务器连接到服务器并运行只读查询的能力。这有助于复制目的以及以高精度恢复一个备份到一个期望的状态。术语热备也指服务器从恢复转移到正常操作而用户能继续运行查询并且保持其连接打开的能力。在热备模式中运行查询与正常查询操作相似，尽管如下所述存在一些用法和管理上的区别。 26.5.1. 用户概览 当hot_standby参数在一台后备服务器上被设置为真时，一旦恢复将系统带到一个一致的状态它将开始接受连接。所有这些连接都被限制为只读，甚至临时表都不能被写入。
Centos7部署PostgreSQL 12集群（主备）
sunny05296的博客
10-27 7879
Centos7部署PostgreSQL 12集群（主备） 关于备份模式 常规的备份模式有三种：热备、冷备和双活。 热备：仅主节点承担用户的业务、提供数据库服务，在不关闭数据库服务（不停服）的情况下对主节点进行备份。 为了保证数据库服务的正常不间断运行，一般用两台机器作为数据库服务机器。其中一台用于实际数据库操作应用、提供数据库服务，而另外一台则实时从前者中获取数据以保持数据的一致性。 如果当前的主节点故障宕机，当前的备节点机器立马（人为手动触发或由配置自动触发）取代当前的主节点机器继续提...
hgdb hac集群重启后所有节点显示Replica，无Leader节点的原因之一
lk的窝
03-18 3815
1、瀚高HAC集群重启后，所有节点显示Replica；无法启动主节点 [root@db ~]# /opt/HighGo/tools/hghac/hghactl -c /opt/HighGo/tools/hghac/hghac.yaml list + Cluster: ha (7072987311974756506) -----+---------+----+-----------+ | Member | Host | Role | State | TL | Lag i...
postgres 基于时间线恢复测试
m15217321304的博客
04-03 861
--//当前时间线为5 --//插入一些数据 [postgres@postgres pg_wal]$ p psql (11.1) Type "help" for help. postgres=# select * from tbl; id | ival | description | created_time ----+------+------------...
GBase 8s HAC集群简介
12-25
GBase 8s HAC（High Availability Cluster，高可用集群）是南大通用数据库系统公司推出的一种基于数据库逻辑日志复制技术的集群解决方案，旨在提供高可靠性和数据安全性。该集群设计主要目标是确保在主数据库出现...
GBase8s HAC集群配置方法.docx
07-31
一个GBase8s 同城灾备高可用集群中最多只能有一个同城灾备节点。节点间基于逻辑日志的复制技术，所以数据库需要开启日志模式。 集群搭建需要满足以下前提条件： 各节点服务器的数据库版本完全相同 各节点务器...
Linux运维-6.集群-集群视频-3、高可用集群（HAC）-课件
11-02
本课程聚焦于Linux集群中的一个关键领域——高可用性集群（High Availability Cluster，简称HAC）。通过学习这一主题，你将能够理解如何构建和维护一个能够抵御单点故障的系统，确保业务不受中断。 高可用集群是...
数据库集群技术有哪些？.doc
最新发布
09-18
2. 负载均衡集群（LBC）：负载均衡集群用于处理大量并发请求，通过将工作负载分散到集群中的多个节点，避免单个服务器过载，提高服务响应时间和系统稳定性。常见于互联网服务和高流量网站，确保用户请求能够被快速且...
HAC的射频电场辐射和磁场辐射研究
10-22
根据这种情况,在ANSIC63.19标准里规定了HAC(hearingaidcompatibility)部分的测试要求,其中HAC的射频电场辐射和射频磁场辐射是其最重要的组成部分之一。下面我们就简单介绍一下HAC的射频电场辐射和射频磁场辐射的大致...
瀚高数据库安全版V4.5_Repmgr集群安装手册（Linux）
Auspicious航的博客
07-17 636
安全审计功能关闭及用户有效期的更改请参考《瀚高数据库安全版V4.5单机版-安装手册(Linux平台)》。在所有集群节点的root用户家目录下创建“.pgpass”文件，写入如下内容，并赋权600。③所有节点都需配置.pgpass文件，.pgpass不能省略点。至此，瀚高数据库安全版V4.5集群（REPMGR）安装完毕。【备节点配置数据库参数前请按照主节点修改步骤进行配置】配置备节点的集群配置文件hg_repmgr.conf。注意：集群每个节点都需配置。册(Linux平台)》】。注意：其他备节点配置相同。
csv-parse 解析csv文件报错 Invalid Record Length: expect 4, got 7 on line 8
landiyaaa的博客
03-09 777
在找虫的过程中发现如果把有问题的文件重新保存一次，报错消失。并且对比前后两次的文件大小，有1字节的差异。 这1字节应该就是关键。要看下两个文件这1字节差在哪里，需要查看文件的字节码 在终端输入vi -b 文件名，使用二进制模式 进入后输入 :%!xxd 文件的字节码（对应ASCII码表）就展开了。 窗口的右边的字符是一一对应的 左边的文件是有问题的，右边的可以成功解析。 差别就在于右边文件，所有的换行符都是 0d 0a ，对应 ASCII 码表是“回车”+“换行”。 ...
HAC集群部署vip及相关操作
HighGO
04-13 1632
瀚高数据库 目录 文档用途 详细信息 文档用途 本文档用于指导HAC集群vip部署及相关操作 详细信息 HAC集群支持用户配置在特定事件发生时触发的回调脚本，因此可以通过callback脚本实现vip的添加、漂移、删除 1、vip的部署 vip相关文件会在HAC集群安装包的同一目录下，其中loadvip.sh为vip脚本（见附件），vip.env为脚本的变量文件 [root@host hghac]# ls etcd hghac hghac.service hghactl hghac-vip.ser
postgresql链接提示the database system is starting up
热门推荐
业精于勤荒于嬉;行成于思，毁于随。
03-30 1万+
电脑重启后，postgresql链接提示the database system is starting up不论是通过程序还是通过pgadmin工具，都提示这个错误。网上搜了下，有遇到类似的问题。解决方法就是修改postgresql.conf文件中的hot_standby为on，默认是注释掉的。改完之后，重启postgresql数据库即可，如果无法重启，看下是不是有postgres的进程在运行，如...
postgres主备切换之文件触发方式
m15217321304的博客
03-27 4970
本文测试参考PostgresSQL实战一书。 本文档测试环境： 主库IP：192.168.40.130 主机名：postgres 端口：5442 备库IP: 192.168.40.131 主机名：postgreshot 端口：5442 PostgreSQL9.0版本流复制主备切换只能通过创建触发文件方式进行，这一小节将介绍这种主备切换方式，测试环境为一主一备异步流复制...
PostgreSQL异步主从流复制搭建
baidang9740的博客
11-15 166
1 总体规划 Master库 Slave库 操作系统 CentOS Linux release 7.5.1804 CentOS Linux release 7.5.1804 处理器 1 1 内存 4G 4G 硬盘 ...
FATAL: the database system is starting up
dqchouyang的专栏
03-05 7328
详细的报错信息如下：LOG: database system is ready to accept connections LOG: database system was interrupted; LOG: database system was not properly shut down; automatic recovery in progress LOG: invalid reco
pg 备份恢复（二）—— 利用pg_rman进行完整恢复及基于时间点的恢复
Hehuyi_In的博客
10-20 2975
利用上一篇提到的pg_rman来做备份恢复测试，相对而言它的命令更简单，在紧急恢复时更方便。 一、 完整恢复测试 1. 在users库创建一个测试表 create table test1017(a int); insert into test1017 values(1); insert into test1017 values(2); insert into test1017 valu...
数据库集群技术详解：分类、架构与应用
不同的集群技术和架构，如共享磁盘型和非共享磁盘型，以及基于IO、操作系统、数据库实例或单个数据库的不同粒度，都是为了适应各种复杂的应用场景和性能优化需求。数据库集群技术是现代IT基础设施的核心组成部分，它...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值