hgdb hac集群重启后所有节点显示Replica，无Leader节点的原因之一

最新推荐文章于 2022-03-24 16:05:32 发布
最新推荐文章于 2022-03-24 16:05:32 发布
阅读量3.8k 收藏
点赞数
分类专栏： Highgo DB 文章标签： 运维 dba 数据库架构
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lk_db/article/details/123569900
版权

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 in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Replica | running |    |   unknown |
| hghacb | 192.168.80.112:5866 | Replica | running |    |   unknown |
| hghacc | 192.168.80.113:5866 | Replica | running |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
2、停止所有节点HAC服务后，仅重启节点1（原主节点）Role也显示为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 in MB |
+--------+---------------------+---------+---------+----+-----------+
| hghaca | 192.168.80.111:5866 | Replica | running |    |   unknown |
| hghacb | 192.168.80.112:5866 | Replica | stopped |    |   unknown |
| hghacc | 192.168.80.113:5866 | Replica | stopped |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
3、停止所有节点的HAC服务，在节点1手动删除standby.signal文件，启动节点1的HAC服务后仍然不正常
[root@db ~]# systemctl stop hghac-vip
[root@db ~]# /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 |
+--------+---------------------+---------+---------+----+-----------+
[root@db ~]# cd /db/hgdbdata/data/
[root@db data]# ls
audit_param.conf  global                pg_commit_ts        pg_ident.conf         pg_notify     pg_stat      pg_twophase  postgresql.auto.conf         postgresql.conf.backup
backup_label.old  hgaudit               pg_dynshmem         pg_ident.conf.backup  pg_replslot   pg_stat_tmp  PG_VERSION   postgresql.base.conf         postmaster.opts
base              hgdb.lic              pg_hba.conf         pg_logical            pg_serial     pg_subtrans  pg_wal       postgresql.base.conf.backup  secure_param.conf
current_logfiles  patroni.dynamic.json  pg_hba.conf.backup  pg_multixact          pg_snapshots  pg_tblspc    pg_xact      postgresql.conf              standby.signal
[root@db data]# rm -rf standby.signal 
[root@db data]# systemctl start hghac-vip
[root@db data]# systemctl status hghac-vip
● hghac-vip.service - hghac
   Loaded: loaded (/etc/systemd/system/hghac-vip.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2022-03-18 10:22:55 CST; 4s ago
 Main PID: 21221 (hghac)
    Tasks: 14
   CGroup: /system.slice/hghac-vip.service
           ├─21221 /opt/HighGo/tools/hghac/hghac /opt/HighGo/tools/hghac/hghac.yaml
           ├─21227 /opt/HighGo/tools/hghac/hghac /opt/HighGo/tools/hghac/hghac.yaml
           ├─21241 /opt/HighGo4.5.7-see/bin/postgres -D /db/hgdbdata/data --config-file=/db/hgdbdata/data/postgresql.conf --listen_addresses=0.0.0.0 --port=5866 --cluster_name=ha --wal_l...
           ├─21243 postgres: ha: logger   
           ├─21244 postgres: ha: auditwriter   
           ├─21245 postgres: ha: startup   recovering 00000019000000000000002D
           ├─21247 postgres: ha: checkpointer   
           ├─21248 postgres: ha: background writer   
           ├─21249 postgres: ha: stats collector   
           └─21250 postgres: ha: audit archiver or cleanup   

Mar 18 10:22:55 db systemd[1]: Started hghac.
Mar 18 10:22:57 db hghac[21221]: 2022-03-18 10:22:57 CST [21241]: [1-1] 6233ed01.52f9 0     LOG:  Password detection module is disabled
Mar 18 10:22:57 db hghac[21221]: 2022-03-18 10:22:57 CST [21241]: [2-1] 6233ed01.52f9 0     LOG:  starting HighGo Security Enterprise Edition Database System 4.5.7 on CentOS...d on 20210804
Mar 18 10:22:57 db hghac[21221]: 2022-03-18 10:22:57 CST [21241]: [3-1] 6233ed01.52f9 0     LOG:  listening on IPv4 address "0.0.0.0", port 5866
Mar 18 10:22:57 db hghac[21221]: 2022-03-18 10:22:57 CST [21241]: [4-1] 6233ed01.52f9 0     LOG:  listening on Unix socket "/tmp/.s.PGSQL.5866"
Mar 18 10:22:57 db hghac[21221]: 2022-03-18 10:22:57 CST [21241]: [5-1] 6233ed01.52f9 0     LOG:  redirecting log output to logging collector process
Mar 18 10:22:57 db hghac[21221]: 2022-03-18 10:22:57 CST [21241]: [6-1] 6233ed01.52f9 0     HINT:  Future log output will appear in directory "../hgdb_log".
Mar 18 10:22:57 db hghac[21221]: localhost:5866 - accepting connections
Mar 18 10:22:57 db hghac[21221]: localhost:5866 - accepting connections
Mar 18 10:22:58 db hghac[21221]: localhost:5866 - accepting connections
Hint: Some lines were ellipsized, use -l to show in full.
[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 |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
4、停止所有节点的HAC服务，在节点1手动删除standby.signal文件，启动节点1的数据库服务，数据库能正常启动，未生成standby.signal文件，表明数据库为正常读写模式
[root@db data]# systemctl stop hghac-vip
[root@db data]# pwd
/db/hgdbdata/data
[root@db data]# ls
audit_param.conf  global                pg_commit_ts        pg_ident.conf         pg_notify     pg_stat      pg_twophase  postgresql.auto.conf         postgresql.conf.backup
backup_label.old  hgaudit               pg_dynshmem         pg_ident.conf.backup  pg_replslot   pg_stat_tmp  PG_VERSION   postgresql.base.conf         postmaster.opts
base              hgdb.lic              pg_hba.conf         pg_logical            pg_serial     pg_subtrans  pg_wal       postgresql.base.conf.backup  secure_param.conf
current_logfiles  patroni.dynamic.json  pg_hba.conf.backup  pg_multixact          pg_snapshots  pg_tblspc    pg_xact      postgresql.conf              standby.signal
[root@db data]# rm -rf standby.signal 
[root@db data]# pg_ctl start -D /db/hgdbdata/data/
waiting for server to start....2022-03-18 10:24:22 CST [21576]: [1-1] 6233ed56.5448 0     LOG:  Password detection module is disabled
2022-03-18 10:24:22 CST [21576]: [2-1] 6233ed56.5448 0     LOG:  starting HighGo Security Enterprise Edition Database System 4.5.7 on CentOS7 x86_64,build on 20210804
2022-03-18 10:24:22 CST [21576]: [3-1] 6233ed56.5448 0     LOG:  listening on IPv4 address "0.0.0.0", port 5866
2022-03-18 10:24:22 CST [21576]: [4-1] 6233ed56.5448 0     LOG:  listening on Unix socket "/tmp/.s.PGSQL.5866"
2022-03-18 10:24:22 CST [21576]: [5-1] 6233ed56.5448 0     LOG:  redirecting log output to logging collector process
2022-03-18 10:24:22 CST [21576]: [6-1] 6233ed56.5448 0     HINT:  Future log output will appear in directory "../hgdb_log".
 done
server started
[root@db data]# ls
audit_param.conf  global                pg_commit_ts        pg_ident.conf         pg_notify     pg_stat      pg_twophase  postgresql.auto.conf         postgresql.conf.backup
backup_label.old  hgaudit               pg_dynshmem         pg_ident.conf.backup  pg_replslot   pg_stat_tmp  PG_VERSION   postgresql.base.conf         postmaster.opts
base              hgdb.lic              pg_hba.conf         pg_logical            pg_serial     pg_subtrans  pg_wal       postgresql.base.conf.backup  postmaster.pid
current_logfiles  patroni.dynamic.json  pg_hba.conf.backup  pg_multixact          pg_snapshots  pg_tblspc    pg_xact      postgresql.conf              secure_param.conf
[root@db data]# pg_ctl stop -D /db/hgdbdata/data/
waiting for server to shut down.... done
server stopped
[root@db data]# 

5、启动节点1 HAC服务，检查数据库日志文件，报错如下
[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 |    |   unknown |
+--------+---------------------+---------+---------+----+-----------+
[root@db data]# 
[root@db hgdb_log]# pwd
/db/hgdbdata/hgdb_log
[root@db hgdb_log]# tail -f hgdb-5.csv
2022-03-18 10:28:10.388 CST,"sysdba","highgo",22463,"127.0.0.1:14914",6233ee3a.57bf,2,"authentication",2022-03-18 10:28:10 CST,2/12,0,FATAL,28P01,"password authentication failed for user ""sysdba""","Password does not match for user ""sysdba"".
Connection matched pg_hba.conf line 4: ""host    all             all             0.0.0.0/0            sm3""",,,,,,,,""
2022-03-18 10:28:10.393 CST,,,22464,"127.0.0.1:14916",6233ee3a.57c0,1,"",2022-03-18 10:28:10 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=14916",,,,,,,,,""
2022-03-18 10:28:10.398 CST,"sysdba","highgo",22464,"127.0.0.1:14916",6233ee3a.57c0,2,"authentication",2022-03-18 10:28:10 CST,2/13,0,FATAL,28P01,"password authentication failed for user ""sysdba""","Password does not match for user ""sysdba"".
Connection matched pg_hba.conf line 4: ""host    all             all             0.0.0.0/0            sm3""",,,,,,,,""
2022-03-18 10:28:10.419 CST,,,22467,"127.0.0.1:14920",6233ee3a.57c3,1,"",2022-03-18 10:28:10 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=14920",,,,,,,,,""
2022-03-18 10:28:10.459 CST,,,22468,"127.0.0.1:14924",6233ee3a.57c4,1,"",2022-03-18 10:28:10 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=14924",,,,,,,,,""
2022-03-18 10:28:10.483 CST,"sysdba","highgo",22468,"127.0.0.1:14924",6233ee3a.57c4,2,"authentication",2022-03-18 10:28:10 CST,2/15,0,FATAL,28P01,"password authentication failed for user ""sysdba""","Password does not match for user ""sysdba"".
Connection matched pg_hba.conf line 4: ""host    all             all             0.0.0.0/0            sm3""",,,,,,,,""
2022-03-18 10:28:10.490 CST,,,22469,"127.0.0.1:14926",6233ee3a.57c5,1,"",2022-03-18 10:28:10 CST,,0,LOG,00000,"connection received: host=127.0.0.1 port=14926",,,,,,,,,""
2022-03-18 10:28:10.495 CST,"sysdba","highgo",22469,"127.0.0.1:14926",6233ee3a.57c5,2,"authentication",2022-03-18 10:28:10 CST,2/16,0,FATAL,28P01,"password authentication failed for user ""sysdba""","Password does not match for user ""sysdba"".
Connection matched pg_hba.conf line 4: ""host    all             all             0.0.0.0/0            sm3""",,,,,,,,""

经检查为hghac.yaml中密码与实际不符（因特殊需求前期更改过相关用户密码）
[root@db hghac]# pwd
/opt/HighGo/tools/hghac
[root@db hghac]# vi hghac.yaml
  authentication:
    replication:
      password: High@123
      username: sysdba
    rewind:
      password: High@123
      username: sysdba
    sysdba:
      password: High@123
    syssso:
      password: High@123
    syssao:
      password: High@123
      
将hghac.yaml中的密码修改为正确的密码：
  authentication:
    replication:
      password: High@789
      username: sysdba
    rewind:
      password: High@789
      username: sysdba
    sysdba:
      password: High@789
    syssso:
      password: High@789
    syssao:
      password: High@789
      
重启HAC服务，数据库Role显示为Leader：
[root@db data]# systemctl restart 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 | 25 |           |
+--------+---------------------+--------+---------+----+-----------+
[root@db data]# 

其他两个备节点也修改hghac.yaml文件为正确的密码，分别启动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 | 26 |           |
| hghacb | 192.168.80.112:5866 | Replica | running | 26 |         0 |
| hghacc | 192.168.80.113:5866 | Replica | running | 26 |         0 |
+--------+---------------------+---------+---------+----+-----------+

6、至此，集群恢复正常。
 

lk_db
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
Replica sets架构复制集(3)详解--增减节点
weixin_33810302的博客
07-25 126
添加新节点到现有的replica sets中状态1，执行初始化，代码如下"stateStr" : "RECOVERING","uptime" : 21,"optime" : {"t" : 0,"i" : 0},"optimeDate" : ISODate("1970-01-01T00:00:00Z"),"lastHeartbea...
解决连接kudu时，delaying RPC due to Service unavailable: Master config (**.**.**.**:7051) has no leader
t18092838767的博客
01-11 1360
文章目录1 报错日志2 原因分析3 问题解决4 扩展问题排查4.1 端口是否开放 1 报错日志 delaying RPC due to Service unavailable: Master config (...:7051) has no leader 2 原因分析 kudu客户端连接kudu时，配置的时ip，结果kudu给返回了主机的域名，集群通过域名找到其他节点。问题就出在这了，返回域名后客户端就要识别啊，所以少一个配置，hosts配置.如下 127.**..1 master1 3 问题解决 在使
ssh另一台机器时，报Password authentication is disabled to avoid man-in-the-middle attacks.
xqhrs232的专栏
05-02 8208
原文地址::http://www.blogjava.net/anchor110/articles/418195.html 相关文章 1、好记心不如烂笔头，ssh登录　The authenticity of host 192.168.0.xxx can't be established.的问题----http://blog.csdn.net/kimsoft/article/detai
impala 报错value too large for column 'xxx' (70787 bytes, maximum is 65536 bytes)
vkingnew 的技术博客
05-21 2265
报错信息： Pipeline Status: RUNNING_ERROR: com.streamsets.pipeline.api.StageException: KUDU_03 - Errors while interacting with Kudu: Row error for primary key="c42f76aec336497e8a2691d8a6f96f76", tablet=n...
kudu坑1
老猿说说专栏
11-25 766
坑1: Caused by: org.apache.kudu.client.NoLeaderFoundException Caused by: org.apache.kudu.client.NoLeaderFoundException: Master config (192.168.1.117:7051) has no leader. Exceptions received: org.apache.kudu.client.RecoverableException: [peer master-192.1..
GBase 8s HAC集群简介
12-25
GBase 8s HAC（High Availability Cluster，高可用集群）是南大通用数据库系统公司推出的一种基于数据库逻辑日志复制技术的集群解决方案，旨在提供高可靠性和数据安全性。该集群设计主要目标是确保在主数据库出现...
Linux运维-6.集群-集群视频-3、高可用集群（HAC）-课件
11-02
本课程聚焦于Linux集群中的一个关键领域——高可用性集群（High Availability Cluster，简称HAC）。通过学习这一主题，你将能够理解如何构建和维护一个能够抵御单点故障的系统，确保业务不受中断。 高可用集群是...
GBase8s HAC集群配置方法.docx
07-31
一个GBase8s 同城灾备高可用集群中最多只能有一个同城灾备节点。节点间基于逻辑日志的复制技术，所以数据库需要开启日志模式。 集群搭建需要满足以下前提条件： 各节点服务器的数据库版本完全相同 各节点务器...
行业文档-设计装置-一种降低手机HAC值的装置及其手机.zip
09-02
标题“行业文档-设计装置-一种降低手机HAC值的装置及其手机.zip”和描述所提及的“一种降低手机HAC值的装置及其手机”明显指向了针对手机辐射水平（HAC，Headphone Acoustic Coupling，耳机声耦合值）优化的技术方案...
数据库集群技术有哪些？.doc
09-18
数据库集群技术是现代大型企业级应用中不可或缺的一部分，它通过将多台服务器组织成一个集群，以实现更高的性能、负载均衡以及系统可用性。数据库集群技术主要包括以下几类： 1. 高性能集群（HPC）：这类集群主要...
kudu重启报错：Error creating minidump directory: /var/log/kudu/minidumps/kudu-tserver
小海的专栏
09-26 602
问题描述：CDH6.3.2的Kudu，之前安装的时候启动都是正常的，后来因为一些原因停了一段时间，再次启动的时候发现启动失败报错： Error creating minidump directory:/data/var/log/kudu/minidumps/kudu-tserver 和 Failed to load FS layout: /data/kudu/kudu_server_data/instance 经查发现kudu的日志文件和数据文件的所有者出现错误： 原...
HGDB HAC集群导致时间线变化的操作演示
lk的窝
03-18 449
（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 ...
Kafka的Replica分配策略之二 Replica变为0了怎么办
Rapper金馆长的博客
11-21 3501
这一篇文章准备讨论当kafka集群的broker发生变化,诸如broker崩溃,退出时,kafka集群会如何分配该broker上的Replica和Partition. 在讨论这个问题之前,需要先搞清kafka集群中,leader与follower的分工.可以看我写的这篇文章 Kafka的leader选举过程 在之前介绍kafka的选举过程时,提到成功选举出的leader会向zookeepe
Kafka 错误代码解释
热门推荐
Rao的博客
02-24 2万+
Kafka 原生API交互的Code代表 使用client 与 kafka 交互时，会返回错误代码，官方给出了，代码表示的具体含义 官网地址 https://kafka.apache.org/protocol 示例 KeyError 36 表示 topic 已存在 下表是Error code 以及相对应的关系 Error code retriable description ...
数据库(基础)-Password认证失败解决
Kellbook的博客
11-20 1万+
日志文件
连接docker中postgresql数据库出现Connection matched pg_hba.conf line 99: “host all all all md5“
长舒的博客
11-13 2476
最近跑在docker里的go服务总是莫名其妙的突然连不上postgres数据库，postgres数据库也是跑在docker里，看了下日志 Connection matched pg_hba.conf line 99: “host all all all md5” 使用 docker cp ContainerID:Containerpath 宿主机路径 将文件复制到宿主机目录下，然后进行修改，将第99行的md5改为trust,搞定 ...
Patroni 时间差导致启动状态为stop
Database operation and maintenance
04-09 1081
环境信息 服务名称 系统版本 PostgreSQL PostgreSQL 9.6.8 Patronictl patronictl version 1.5.5 Etcd etcdctl version 2.2.5 查看Patroni状态 root@localhost:~# patronictl -c /data/scripts/patroni_postgresql.yml...
PostgreSQL连接报错的一些常规办法
suverhwh的博客
03-24 7248
2.1 远程连接失败 无法通过远程TCP/IP方式连接PostgreSQL，而本地可连接。 远程连接失败： $ psql -h 10.0.4.13 -U postgres -d postgres -p5432 psql: error: could not connect to server: Connection refused Is the server running on host "10.0.4.13" and accepting TCP/IP connections on...
PostgreSQL 高可用集群 repmgr 与 头疼的问题
sql server的专栏
08-08 1800
PostgreSQL 的高可用的方案，基本上不是原生的，大多是依靠第三方的公司来进行开发的，挂名的有那么几种 Patroni, PGPOOL-II, Repmgr , 等等几种。PGP...
HAC检验 python
最新发布
11-16
根据提供的引用内容，没有直接与HAC检验相关的代码或方法。但是，可以使用Python中statsmodels包中的HAC函数来进行HAC检验。下面是一个简单的例子： ```python import statsmodels.api as sm from statsmodels.stats.diagnostic import het_white, het_breuschpagan from statsmodels.stats.diagnostic import het_white as white_test # 加载数据 data = sm.datasets.macrodata.load_pandas().data data.index = data['year'] data = data[['realgdp','realcons','realinv']] # 添加常数项 data = sm.add_constant(data) # 拟合线性回归模型 model = sm.OLS(data['realgdp'], data[['const', 'realcons', 'realinv']]).fit() # 进行HAC检验 hac_test = model.get_robustcov_results(cov_type='HAC', maxlags=1) # 输出结果 print(hac_test.summary()) ``` 上述代码中，我们首先加载了一个数据集，然后添加了常数项并拟合了一个线性回归模型。接下来，我们使用get_robustcov_results函数来进行HAC检验，并将cov_type参数设置为'HAC'，将maxlags参数设置为1。最后，我们输出了检验结果的摘要。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值