2023-01-11 LightDB高可用常用操作-管理.md

最新推荐文章于 2024-06-07 22:24:10 发布
最新推荐文章于 2024-06-07 22:24:10 发布
阅读量252 收藏
点赞数
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/richar1/article/details/131331553
版权
本文详细介绍了LightDB集群的高可用操作，包括主库和备库的重启、主备切换以及主库和备库故障后的恢复步骤。通过ltcluster工具，管理员可以执行standbyswitchover、standbyfollow、noderejoin等操作，确保数据库服务的连续性和数据一致性。
摘要由CSDN通过智能技术生成

LightDB-高可用常用操作-管理篇

  • 安装环境
操作系统：
    centos7
服务器IP:
    1.192.168.121.112 (主)
    2.192.168.121.113 (从)
    3.192.168.121.114 (哨兵-可选)
  • 主库重启操作

1.先停止备库的keepalived,在root用户下执行

# 1.获得备库keepalived进 程pid
[root@localhost ~]# cat /var/run/keepalived.pid
7680
# 2.杀死keepalived进程
[root@localhost ~]# kill 7680
# 3.确认keepalived进程确实已不存在
[root@localhost ~]# ps aux | grep keepalived
root      24464  0.0  0.0 112824   976 pts/1    S+   20:27   0:00 grep --color=auto keepalived
  1. 主库重启，在lightdb用户下执行，重启期间主库不提供服务
# 1.暂停ltclusterd,防止自动failover
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service pause
NOTICE: node 1 (lightdbCluster1921681211125432) paused
NOTICE: node 2 (lightdbCluster1921681211135432) paused
NOTICE: node 4 (lightdbCluster1921681211145432) paused

# 2.查看集群状态，确认primary的paused?状态为yes
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928 | yes     | n/a                
 2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 3727 | yes     | 0 second(s) ago    
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525 | yes     | 0 second(s) ago   
 
# 3.先断开所有连接到数据库的客户端和应用程序(否则数据库将stop failed)，然后停止主库
# 3.1默认回滚所有未断开的连接
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop
waiting for server to shut down................... done
server stopped
# 3.2如果存在客户端连接，尝试执行
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop -m smart
waiting for server to shut down............................................................... failed
lt_ctl: server does not shut down
HINT: The "-m fast" option immediately disconnects sessions rather than
waiting for session-initiated disconnection.
# 3.3如果依旧失败，尝试执行
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop -m immediate
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop -m fast

# 4.等待数据库停止成功

# 5.修改数据库参数，或其他操作

# 6.启动主库
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA start
2023-01-10 20:46:30.865738T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,LOG:  LightDB autoprewarm: prewarm dbnum=0
2023-01-10 20:46:30.869043T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,LOG:  ltaudit extension initialized
waiting for server to start........2023-01-10 20:46:35.267239T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,LOG:  redirecting log output to logging collector process
2023-01-10 20:46:35.267239T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,HINT:  Future log output will appear in directory "log".
done
server started

# 7.等待启动成功，验证集群状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928 | yes     | n/a                
 2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 3727 | yes     | 1 second(s) ago    
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525 | yes     | 1 second(s) ago

# 8.恢复集群状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service unpause
NOTICE: node 1 (lightdbCluster1921681211125432) unpaused
NOTICE: node 2 (lightdbCluster1921681211135432) unpaused
NOTICE: node 4 (lightdbCluster1921681211145432) unpaused

# 9.再次查验集群状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928 | no      | n/a                
 2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 3727 | no      | 0 second(s) ago    
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525 | no      | 0 second(s) ago
  1. 重启备机keepalived服务
新开一个会话，使用root用户，按照上面输出的提示执行
[root@localhost bin]# cd /usr/local/lightdb/lightdb-x/13.8-22.3/tools/bin

#启动keepalive服务(standby server执行)
[root@localhost bin]# ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf

#查看进程
[root@localhost bin]# ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
[root@localhost bin]# ps aux|grep keepalived
root      26657  0.0  0.0  48100  1008 ?        Ss   20:55   0:00 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26658  0.1  0.0  48100  1844 ?        S    20:55   0:00 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26659  0.0  0.0  48100  1364 ?        S    20:55   0:00 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
  • 备库重启操作

备库因修改参数或者其他原因需要重启，在备库上执行

# 1.暂停ltclusterd,防止自动failover
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service pause
NOTICE: node 1 (lightdbCluster1921681211125432) paused
NOTICE: node 2 (lightdbCluster1921681211135432) paused
NOTICE: node 4 (lightdbCluster1921681211145432) paused

# 2.查看集群状态，确认standby的paused?状态为yes
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928 | yes     | n/a                
 2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 3727 | yes     | 0 second(s) ago    
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525 | yes     | 0 second(s) ago   
 
# 3.先断开所有连接到数据库的客户端和应用程序(否则数据库将stop failed)，然后停止主库
# 3.1默认回滚所有未断开的连接
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop
waiting for server to shut down................... done
server stopped
# 3.2如果存在客户端连接，尝试执行
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop -m smart
waiting for server to shut down............................................................... failed
lt_ctl: server does not shut down
HINT: The "-m fast" option immediately disconnects sessions rather than
waiting for session-initiated disconnection.
# 3.3如果依旧失败，尝试执行
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop -m immediate
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop -m fast

# 4.等待数据库停止成功，备库停止后，可以在主库机上执行查看集群状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                         | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+----------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                  | running    | 4928 | yes     | n/a                
 2  | lightdbCluster1921681211135432 | standby | - failed  | ? lightdbCluster1921681211125432 | n/a        | n/a  | n/a     | n/a                
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432   | running    | 3525 | yes     | 0 second(s) ago    

# 5.修改数据库参数，或其他操作

# 6.启动备库
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA start
2023-01-10 20:46:30.865738T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,LOG:  LightDB autoprewarm: prewarm dbnum=0
2023-01-10 20:46:30.869043T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,LOG:  ltaudit extension initialized
waiting for server to start........2023-01-10 20:46:35.267239T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,LOG:  redirecting log output to logging collector process
2023-01-10 20:46:35.267239T,,,,,postmaster,,00000,2023-01-10 20:46:30 CST,0,72843,HINT:  Future log output will appear in directory "log".
done
server started

# 7.等待启动成功，验证集群状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928 | yes     | n/a                
 2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 3727 | yes     | 1 second(s) ago    
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525 | yes     | 1 second(s) ago

# 8.恢复集群状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service unpause
NOTICE: node 1 (lightdbCluster1921681211125432) unpaused
NOTICE: node 2 (lightdbCluster1921681211135432) unpaused
NOTICE: node 4 (lightdbCluster1921681211145432) unpaused

# 9.再次查验集群状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928 | no      | n/a                
 2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 3727 | no      | 0 second(s) ago    
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525 | no      | 0 second(s) ago
  • 主备切换

集群正常运行状态下进行主备切换，可以通过在备机上使用switchover来自动完成

# 1.在备机上试运行
[lightdb@localhost ~]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf standby switchover --siblings-follow --dry-run
NOTICE: checking switchover on node "lightdbCluster1921681211135432" (ID: 2) in --dry-run mode
INFO: SSH connection to host "192.168.121.112" succeeded
INFO: able to execute "ltcluster" on remote host "192.168.121.112"
INFO: all sibling nodes are reachable via SSH
INFO: 2 walsenders required, 10 available
INFO: demotion candidate is able to make replication connection to promotion candidate
INFO: 0 pending archive files
INFO: replication lag on this standby is 0 seconds
INFO: 1 replication slots required, 10 available
INFO: would pause ltclusterd on node "lightdbCluster1921681211125432" (ID 1)
INFO: would pause ltclusterd on node "lightdbCluster1921681211135432" (ID 2)
INFO: would pause ltclusterd on node "lightdbCluster1921681211145432" (ID 4)
NOTICE: local node "lightdbCluster1921681211135432" (ID: 2) would be promoted to primary; current primary "lightdbCluster1921681211125432" (ID: 1) would be demoted to standby
INFO: following shutdown command would be run on node "lightdbCluster1921681211125432":
  "/usr/local/lightdb/lightdb-x/13.8-22.3/bin/lt_ctl  -D '/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster' -W -m fast stop"
INFO: parameter "shutdown_check_timeout" is set to 1800 seconds
INFO: prerequisites for executing STANDBY SWITCHOVER are met

# 2.如果显示prerequisites for executing STANDBY SWITCHOVER are met，表示成功，可进行下一步

# 3.在备库机上正式执行
[lightdb@localhost ~]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf standby switchover --siblings-follow
NOTICE: executing switchover on node "lightdbCluster1921681211135432" (ID: 2)
ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf standby switchover --siblings-follow
NOTICE: local node "lightdbCluster1921681211135432" (ID: 2) will be promoted to primary; current primary "lightdbCluster1921681211125432" (ID: 1) will be demoted to standby
NOTICE: stopping current primary node "lightdbCluster1921681211125432" (ID: 1)
NOTICE: issuing CHECKPOINT on node "lightdbCluster1921681211125432" (ID: 1) 
DETAIL: executing server command "/usr/local/lightdb/lightdb-x/13.8-22.3/bin/lt_ctl  -D '/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster' -W -m fast stop"
INFO: checking for primary shutdown; 1 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 2 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 3 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 4 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 5 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 6 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 7 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 8 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 9 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 10 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 11 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 12 of 1800 attempts ("shutdown_check_timeout")
INFO: checking for primary shutdown; 13 of 1800 attempts ("shutdown_check_timeout")
NOTICE: current primary has been cleanly shut down at location 0/A0000028
NOTICE: promoting standby to primary
DETAIL: promoting server "lightdbCluster1921681211135432" (ID: 2) using pg_promote()
NOTICE: waiting up to 60 seconds (parameter "promote_check_timeout") for promotion to complete
NOTICE: STANDBY PROMOTE successful
DETAIL: server "lightdbCluster1921681211135432" (ID: 2) was successfully promoted to primary
INFO: local node 1 can attach to rejoin target node 2
DETAIL: local node's recovery point: 0/A0000028; rejoin target node's fork point: 0/A00000A0
INFO: creating replication slot as user "ltcluster"
NOTICE: setting node 1's upstream to node 2
WARNING: unable to ping "host=192.168.121.112 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2"
DETAIL: PQping() returned "PQPING_NO_RESPONSE"
NOTICE: starting server using "/usr/local/lightdb/lightdb-x/13.8-22.3/bin/lt_ctl  -w -D '/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster' start"
WARNING: node "lightdbCluster1921681211125432" not found in "pg_stat_replication"
ERROR: connection to database failed
DETAIL: 
could not connect to server: Connection refused
	Is the server running on host "192.168.121.112" and accepting
	TCP/IP connections on port 5432?

DETAIL: attempted to connect using:
  user=ltcluster connect_timeout=2 dbname=ltcluster host=192.168.121.112 port=5432 fallback_application_name=ltcluster options=-csearch_path=
WARNING: unable to connect to local node to check replication slot status
HINT: execute "ltcluster node check" to check inactive slots and drop manually if necessary
NOTICE: NODE REJOIN successful
DETAIL: node 1 is now attached to node 2
WARNING: node "lightdbCluster1921681211125432" not found in "pg_stat_replication"
INFO: waiting for node "lightdbCluster1921681211125432" (ID: 1) to connect to new primary; 1 of max 60 attempts (parameter "node_rejoin_timeout")
DETAIL: checking for record in node "lightdbCluster1921681211135432"'s "pg_stat_replication" table where "application_name" is "lightdbCluster1921681211125432"
WARNING: node "lightdbCluster1921681211125432" not found in "pg_stat_replication"
WARNING: node "lightdbCluster1921681211125432" not found in "pg_stat_replication"
WARNING: node "lightdbCluster1921681211125432" not found in "pg_stat_replication"
WARNING: node "lightdbCluster1921681211125432" not found in "pg_stat_replication"
WARNING: node "lightdbCluster1921681211125432" attached in state "catchup"
INFO: waiting for node "lightdbCluster1921681211125432" (ID: 1) to connect to new primary; 6 of max 60 attempts (parameter "node_rejoin_timeout")
DETAIL: node "lightdbCluster1921681211135432" (ID: 1) is currrently attached to its upstream node in state "catchup"
WARNING: node "lightdbCluster1921681211125432" attached in state "catchup"
WARNING: node "lightdbCluster1921681211125432" attached in state "catchup"
WARNING: node "lightdbCluster1921681211125432" attached in state "catchup"
WARNING: node "lightdbCluster1921681211125432" attached in state "catchup"
WARNING: node "lightdbCluster1921681211125432" attached in state "catchup"
INFO: waiting for node "lightdbCluster1921681211125432" (ID: 1) to connect to new primary; 11 of max 60 attempts (parameter "node_rejoin_timeout")
DETAIL: node "lightdbCluster1921681211135432" (ID: 1) is currrently attached to its upstream node in state "catchup"
NOTICE: node  "lightdbCluster1921681211135432" (ID: 2) promoted to primary, node "lightdbCluster1921681211125432" (ID: 1) demoted to standby
NOTICE: executing STANDBY FOLLOW on 1 of 1 siblings
INFO:  node 4 received notification to follow node 2
INFO: STANDBY FOLLOW successfully executed on all reachable sibling nodes
NOTICE: replication slot "ltcluster_slot_2" deleted on node 1
NOTICE: switchover was successful
DETAIL: node "lightdbCluster1921681211135432" is now primary and node "lightdbCluster1921681211125432" is attached as standby
NOTICE: STANDBY SWITCHOVER has completed successfully

# 4.查看集群状态(2切换成了primary)
[lightdb@localhost ~]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | standby |   running | lightdbCluster1921681211135432 | running    | 4928 | no      | 1 second(s) ago    
 2  | lightdbCluster1921681211135432 | primary | * running |                                | running    | 3727 | no      | n/a                
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211135432 | running    | 3525 | no      | 0 second(s) ago
  • 主库故障恢复

当主库发生故障(如宕机)failover后，备库会自动提升为新主库，以确保集群可用 因上面做了一次主备切换，目前新的主库地址为：192.168.121.113，备库地址为：192.168.121.112

  1. 模拟主库故障，将主库所在机器(192.168.121.113)上的lightdb进程停掉
# 1.查看lightdb进程，确认lightdb是停止运行状态，如果不是，执行步骤2停掉，来模拟主库故障
[lightdb@localhost ~]$ ps aux|grep lightdb

# 2.停止lightdb
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop
waiting for server to shut down......... done
server stopped

# 3.查看状态
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
ERROR: connection to database failed
DETAIL: 
could not connect to server: Connection refused
	Is the server running on host "192.168.121.113" and accepting
	TCP/IP connections on port 5432?

DETAIL: attempted to connect using:
  user=ltcluster connect_timeout=2 dbname=ltcluster host=192.168.121.113 port=5432 fallback_application_name=ltcluster options=-csearch_path=

# 4.在备库机器上查询状态(可以看到1机器切换到了primary)
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID  | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928 | no      | n/a                
 2  | lightdbCluster1921681211135432 | primary | - failed  | ?                              | n/a        | n/a  | n/a     | n/a                
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525 | no      | 0 second(s) ago    

WARNING: following issues were detected
  - unable to  connect to node "lightdbCluster1921681211135432" (ID: 2)

HINT: execute with --verbose option to see connection error messages
  1. 确认当前主库所在机器(192.168.121.113)上的ltcluster处于运行状态
# 1.查看ltcluster进程
[lightdb@localhost ltcluster]$ ps aux|grep ltcluster
lightdb   60183  0.0  0.0 116884  1624 ?        Sl   22:47   0:00 /usr/local/lightdb/lightdb-x/13.8-22.3/bin/ltclusterd -d -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf -p /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltclusterd.pid

# 2.确认ltcluster是运行状态，如果没有，则执行下面命令启动
[lightdb@localhost ltcluster]$ /usr/local/lightdb/lightdb-x/13.8-22.3/bin/ltclusterd -d -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf -p /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltclusterd.pid
[2023-01-10 22:47:18] [NOTICE] redirecting logging output to "/usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster2023-01-10_224718.log"

3.重启故障机器上的lightdb数据库进程

# 1.重新启动lightdb数据库进程
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA start
2023-01-10 23:02:16.502933T,,,,,postmaster,,00000,2023-01-10 23:02:16 CST,0,62485,LOG:  LightDB autoprewarm: prewarm dbnum=0
waiting for server to start....2023-01-10 23:02:16.508863T,,,,,postmaster,,00000,2023-01-10 23:02:16 CST,0,62485,LOG:  ltaudit extension initialized
...2023-01-10 23:02:20.135427T,,,,,postmaster,,00000,2023-01-10 23:02:16 CST,0,62485,LOG:  redirecting log output to logging collector process
2023-01-10 23:02:20.135427T,,,,,postmaster,,00000,2023-01-10 23:02:16 CST,0,62485,HINT:  Future log output will appear in directory "log".
 done
server started

4.故障恢复后重新加入集群
故障恢复后的数据库不会自动加入集群，如果想要重新加入，可以使用region将当前数据库恢复成备库。如果还想将当前数据库成为主库，可以参考主从切换操作。

# 1.region试运行(ps:host地址为集群中primary的ip地址)
[lightdb@localhost ltcluster]$ ltcluster -f $LTHOME/etc/ltcluster/ltcluster.conf node rejoin -d 'host=192.168.121.112 port=5432 dbname=ltcluster user=ltcluster' --verbose --force-rewind --dry-run
NOTICE: using provided configuration file "/usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf"
INFO: replication slots in use, 1 free slots on node 10
INFO: replication connection to the rejoin target node was successful
INFO: local and rejoin target system identifiers match
DETAIL: system identifier is 7186927613994770615
NOTICE: lt_rewind execution required for this node to attach to rejoin target node 1
DETAIL: rejoin target server's timeline 3 forked off current database system timeline 2 before current recovery point 1/28
INFO: prerequisites for using lt_rewind are met
INFO: temporary archive directory "/tmp/ltcluster-config-archive-lightdbCluster1921681211135432" created
INFO: 0 files would have been copied to "/tmp/ltcluster-config-archive-lightdbCluster1921681211135432"
INFO: temporary archive directory "/tmp/ltcluster-config-archive-lightdbCluster1921681211135432" deleted
INFO: lt_rewind would now be executed
DETAIL: lt_rewind command is:
  /usr/local/lightdb/lightdb-x/13.8-22.3/bin/lt_rewind -D '/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster' --source-server='host=192.168.121.112 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2'
INFO: prerequisites for executing NODE REJOIN are met 

# 2.等待确认执行成功

# 3.region正式执行
[lightdb@localhost ltcluster]$ ltcluster -f $LTHOME/etc/ltcluster/ltcluster.conf node rejoin -d 'host=192.168.121.112 port=5432 dbname=ltcluster user=ltcluster' --verbose --force-rewind 
NOTICE: using provided configuration file "/usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf"
NOTICE: lt_rewind execution required for this node to attach to rejoin target node 1
DETAIL: rejoin target server's timeline 3 forked off current database system timeline 2 before current recovery point 1/28
INFO: prerequisites for using lt_rewind are met
INFO: 0 files copied to "/tmp/ltcluster-config-archive-lightdbCluster1921681211135432"
NOTICE: executing lt_rewind
DETAIL: lt_rewind command is "/usr/local/lightdb/lightdb-x/13.8-22.3/bin/lt_rewind -D '/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster' --source-server='host=192.168.121.112 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2'"
NOTICE: 0 files copied to /usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster
INFO: directory "/tmp/ltcluster-config-archive-lightdbCluster1921681211135432" deleted
INFO: creating replication slot as user "ltcluster"
NOTICE: setting node 2's upstream to node 1
WARNING: unable to ping "host=192.168.121.113 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2"
DETAIL: PQping() returned "PQPING_NO_RESPONSE"
NOTICE: starting server using "/usr/local/lightdb/lightdb-x/13.8-22.3/bin/lt_ctl  -w -D '/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster' start"
WARNING: unable to ping "host=192.168.121.113 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2"
DETAIL: PQping() returned "PQPING_NO_RESPONSE"
INFO: waiting for node "lightdbCluster1921681211135432" (ID: 2) to respond to pings; 1 of max 60 attempts (parameter "node_rejoin_timeout")
WARNING: unable to ping "host=192.168.121.113 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2"
DETAIL: PQping() returned "PQPING_NO_RESPONSE"
WARNING: unable to ping "host=192.168.121.113 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2"
DETAIL: PQping() returned "PQPING_NO_RESPONSE"
WARNING: unable to ping "host=192.168.121.113 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2"
DETAIL: PQping() returned "PQPING_NO_RESPONSE"
INFO: node "lightdbCluster1921681211135432" (ID: 2) is pingable
INFO: node "lightdbCluster1921681211135432" (ID: 2) has attached to its upstream node
NOTICE: NODE REJOIN successful
DETAIL: node 2 is now attached to node 1

# 4.查看集群状态(可以看到2重新加入了集群)
[lightdb@localhost ltcluster]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
 ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID   | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+-------+---------+--------------------
 1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928  | no      | n/a                
 2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 60183 | no      | 1 second(s) ago    
 4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525  | no      | 1 second(s) ago 

# 5.确认keepalived正常运行，如果没有运行，则需要启动它
[lightdb@localhost ltcluster]$ ps aux | grep keepalived
root      26657  0.0  0.0  48100  1008 ?        Ss   20:56   0:01 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26658  0.0  0.0  48100  1844 ?        S    20:56   0:01 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26659  0.0  0.0  48100  1408 ?        S    20:56   0:03 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
lightdb   63836  0.0  0.0 112832   984 pts/1    S+   23:32   0:00 grep --color=auto keepalived

5.以上执行region如果失败，可以按照下面步骤重新克隆

# 1.确认lightdb数据库已经停止运行，如果没有，执行以下命令进行停止
[lightdb@localhost ltcluster]$ lt_ctl -D $LTDATA stop
waiting for server to shut down.... done
server stopped

# 2.查看一下集群状态
[lightdb@localhost data]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
ERROR: connection to database failed
DETAIL:
could not connect to server: Connection refused
Is the server running on host "192.168.121.113" and accepting
TCP/IP connections on port 5432?

DETAIL: attempted to connect using:
user=ltcluster connect_timeout=2 dbname=ltcluster host=192.168.121.113 port=5432 fallback_application_name=ltcluster options=-csearch_path=

# 3.清空实例目录下的内容($LTDATA/),如果需要，可以先进行备份

# 4.clone试运行
[lightdb@localhost data]$ ltcluster -h 192.168.121.112 -p 5432 -U ltcluster -d ltcluster -f $LTHOME/etc/ltcluster/ltcluster.conf standby clone --dry-run
NOTICE: destination directory "/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster" provided
INFO: connecting to source node
DETAIL: connection string is: host=192.168.121.112 port=5432 user=ltcluster dbname=ltcluster
DETAIL: current installation size is 83 MB
INFO: "ltcluster" extension is installed in database "ltcluster"
INFO: parameter "max_replication_slots" set to 10
INFO: parameter "max_wal_senders" set to 10
NOTICE: checking for available walsenders on the source node (2 required)
INFO: sufficient walsenders available on the source node
DETAIL: 2 required, 10 available
NOTICE: checking replication connections can be made to the source server (2 required)
INFO: required number of replication connections could be made to the source server
DETAIL: 2 replication connections required
INFO: replication slots will be created by user "ltcluster"
NOTICE: standby will attach to upstream node 1
HINT: consider using the -c/--fast-checkpoint option
INFO: all prerequisites for "standby clone" are met


# 5.确认all prerequisites for "standby clone" are met

# 6.克隆实例目录(ps:-h为primary服务器地址)
[lightdb@localhost data]$ ltcluster -h 192.168.121.112 -p 5432 -U ltcluster -d ltcluster -f $LTHOME/etc/ltcluster/ltcluster.conf standby clone -F
NOTICE: destination directory "/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster" provided
INFO: connecting to source node
DETAIL: connection string is: host=192.168.121.112 port=5432 user=ltcluster dbname=ltcluster
DETAIL: current installation size is 83 MB
NOTICE: checking for available walsenders on the source node (2 required)
NOTICE: checking replication connections can be made to the source server (2 required)
INFO: creating directory "/usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster"...
INFO: creating replication slot as user "ltcluster"
NOTICE: starting backup (using lt_basebackup)...
HINT: this may take some time; consider using the -c/--fast-checkpoint option
INFO: executing:
  /usr/local/lightdb/lightdb-x/13.8-22.3/bin/lt_basebackup -l "ltcluster base backup"  -D /usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster -h 192.168.121.112 -p 5432 -U ltcluster -X stream -S ltcluster_slot_2 
NOTICE: standby clone (using lt_basebackup) complete
NOTICE: you can now start your LightDB server
HINT: for example: lt_ctl -D /usr/local/lightdb/lightdb-x/13.8-22.3/data/defaultCluster start
HINT: after starting the server, you need to re-register this standby with "ltcluster standby register --force" to update the existing node record

# 7.启动数据库
[lightdb@localhost data]$ lt_ctl -D $LTDATA start
2023-01-11 00:02:19.037650T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,LOG:  LightDB autoprewarm: prewarm dbnum=0
2023-01-11 00:02:19.040082T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,LOG:  ltaudit extension initialized
waiting for server to start......2023-01-11 00:02:22.125889T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,LOG:  redirecting log output to logging collector process
2023-01-11 00:02:22.125889T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,HINT:  Future log output will appear in directory "log".
done
server started

# 8.重新注册为standby
[lightdb@localhost data]$ ltcluster -f $LTHOME/etc/ltcluster/ltcluster.conf standby register -F
INFO: connecting to local node "lightdbCluster1921681211135432" (ID: 2)
INFO: connecting to primary database
INFO: standby registration complete
NOTICE: standby node "lightdbCluster1921681211135432" (ID: 2) successfully registered

# 9.查看集群状态(可以看到2正常加入到集群中)
[lightdb@localhost data]$ ltcluster -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf service status
ID | Name                           | Role    | Status    | Upstream                       | ltclusterd | PID   | Paused? | Upstream last seen
----+--------------------------------+---------+-----------+--------------------------------+------------+-------+---------+--------------------
1  | lightdbCluster1921681211125432 | primary | * running |                                | running    | 4928  | no      | n/a
2  | lightdbCluster1921681211135432 | standby |   running | lightdbCluster1921681211125432 | running    | 60183 | no      | 0 second(s) ago
4  | lightdbCluster1921681211145432 | witness | * running | lightdbCluster1921681211125432 | running    | 3525  | no      | 0 second(s) ago


# 10.确认keepalived正常运行，如果没有运行，则需要启动它
[lightdb@localhost ltcluster]$ ps aux | grep keepalived
root      26657  0.0  0.0  48100  1008 ?        Ss   20:56   0:01 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26658  0.0  0.0  48100  1844 ?        S    20:56   0:01 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26659  0.0  0.0  48100  1408 ?        S    20:56   0:03 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
  • 备库故障

备库发生故障后的恢复步骤如下

# 1.确认ltcluster是运行状态，如果没有，则执行下面命令启动
[lightdb@localhost ltcluster]$ /usr/local/lightdb/lightdb-x/13.8-22.3/bin/ltclusterd -d -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster.conf -p /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltclusterd.pid
[2023-01-10 22:47:18] [NOTICE] redirecting logging output to "/usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster2023-01-10_224718.log"

# 2.启动lightdb数据库
[lightdb@localhost data]$ lt_ctl -D $LTDATA start
2023-01-11 00:02:19.037650T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,LOG:  LightDB autoprewarm: prewarm dbnum=0
2023-01-11 00:02:19.040082T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,LOG:  ltaudit extension initialized
waiting for server to start......2023-01-11 00:02:22.125889T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,LOG:  redirecting log output to logging collector process
2023-01-11 00:02:22.125889T,,,,,postmaster,,00000,2023-01-11 00:02:19 CST,0,65044,HINT:  Future log output will appear in directory "log".
done
server started

# 3.确认keepalived正常运行，如果没有运行，则需要启动它
[lightdb@localhost ltcluster]$ ps aux | grep keepalived
root      26657  0.0  0.0  48100  1008 ?        Ss   20:56   0:01 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26658  0.0  0.0  48100  1844 ?        S    20:56   0:01 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
root      26659  0.0  0.0  48100  1408 ?        S    20:56   0:03 ./keepalived -f /usr/local/lightdb/lightdb-x/13.8-22.3/etc/keepalived/keepalived.conf
  • 集群数据复制 (replication) 级别

不通业务场景对数据库主备一致性有不同的要求，一致性越高对性能影响越大。可以通过调整synchronous_commit来达到不通级别的一致性

修改$LTDATA/lightdb.conf文件中的配置参数

# 同步模式下，修改主节点上的配置
synchronous_commit = 'on'
synchronous_standby_names = '*'

# 异步模式下，修改主节点上的配置
synchronous_commit = 'local'
synchronous_standby_names = ''

# 使修改生效
[lightdb@localhost defaultCluster]$ lt_ctl -D $LTDATA reload
server signaled

synchronous_commit

  • 其他
ltcluster和lightdb的运行是独立的。如果三台机器全部宕机重启，这时候lightdb和ltcluster进程都不存在。
如果想要恢复集群环境，需要先启动lightdb,再启动ltcluster

[lightdb@localhost ~]$ cat /usr/local/lightdb/lightdb-x/13.8-22.3/etc/ltcluster/ltcluster2023-01-12_103553.log
[2023-01-12 10:35:53] [NOTICE] ltclusterd (ltclusterd 5.2.1) starting up
[2023-01-12 10:35:53] [INFO] connecting to database "host=192.168.121.112 port=5432 user=ltcluster dbname=ltcluster connect_timeout=2"
[2023-01-12 10:35:53] [ERROR] connection to database failed
[2023-01-12 10:35:53] [DETAIL] 
could not connect to server: Connection refused
	Is the server running on host "192.168.121.112" and accepting
	TCP/IP connections on port 5432?

[2023-01-12 10:35:53] [DETAIL] attempted to connect using:
  user=ltcluster connect_timeout=2 dbname=ltcluster host=192.168.121.112 port=5432 fallback_application_name=ltcluster options=-csearch_path=
炮姐的呱太
关注
ffmpeg2023-12-14版本 windows版
12-20
它包含了非常先进的音频/视频编解码库libavcodec，为了保证高可移植性和编解码质量，libavcodec里很多code都是从头开发的。 FFmpeg在Linux平台下开发，但它同样也可以在其它操作系统环境中编译运行，包括Windows、...
nacos-server-2.1.1.tar.gz
08-16
Nacos 是一个由阿里巴巴开源的分布式服务治理平台，它的全称是Naming And Configuration Service，主要功能包括服务发现、配置管理和服务管理。Nacos 2.1.1 是该平台的一个稳定版本，提供了一系列的增强和优化，使得...
LightDB高可用版集群管理操作
no1polo的博客
12-28 174
LightDB高可用版 switchover, rejoin, standby clone操作展示
lightdb_service.py - lightdb一键启停脚本
紫无之紫的博客
12-29 452
lightdb_service.py 用于对lightdb 服务进行简易的一键启停操作，包括高可用模式，分布式模式和单机模式。lightdb_service.py 基于python3开发。
2023-01-10 LightDB高可用版本安装.md
Richar1的专栏
06-21 94
LightDB-高可用版本安装 一主一从高可用版本安装 安装环境 操作系统： centos7 服务器IP: 1.192.168.121.112 (主) 2.192.168.121.113 (从) 3.192.168.121.114 (哨兵-可选) 安装前准备 参考单机版安装 设置服务器之间的免密认证 #如果使用lightdb用户安装高可用，则在lig...
【最佳实践】基于 Arm 虚拟硬件平台完成在Cortex-M85上移植RT-Thread操作系统
热门推荐
一个专注于嵌入式IoT领域的架构师，深耕IoT领域多年，深度掌握IoT领域的相关技术栈，包括但不限于RTOS内核的实现及其移植、硬件驱动移植开发、网络通讯协议开发、编译构建原理及其实现、底层汇编及编译原理、编译优化及代码重构、嵌入式IoT系统的架构设计等。
06-07 4万+
Arm AVH 跑RT-Thread 体验如何？
consul-template + nginx部署高可用负载均衡
yb223731的博客
05-10 4418
https://www.cnblogs.com/duanxz/p/9734597.html https://juejin.im/post/5b2a6bc351882574cf66a211 consul-template + nginx部署高可用负载均衡 一、Consul-Template简介 Consul-Template是基于Consul的自动替换配置文件的应用。在Consul-Temp...
kubeadm+kube-vip搭建高可用k8s集群
cbmljs的博客
04-08 1962
通用 安装基本软件包 yum install bash‐comp* vim net‐tools wget ‐y 设置主机名，管理节点设置主机名为node1（node2的设置为node2） hostnamectl set-hostname node102 设置Host解析，编辑/etc/hosts文件，添加域名解析 [root@node1 ~]# vim /etc/hosts 10.168.1.101 node101 10.168.1.102 node102 10.168.1.103
XXL-JOB调度中心HA及高可用方案
男儿当自强
06-01 3104
xxl-job 调度中心HA方案
2023-2024年云赛道模拟题库
weixin_52808317的博客
10-09 6696
2023-2024年云赛道模拟题库上线啦，全面覆盖云计算，云服务，大数据和人工智能考点，都是带有解析，实时更新，永久使用 参赛对象及要求： 参赛对象：现有华为ICT学院及未来有意愿成为华为ICT学院的本科及高职院校在校学生。 参赛要求： 1、为ICT学院可报名选手数量不限，非华为ICT学院最多可报30名选手； 2、参加全国总决赛队伍需要具备可用PC和上网条件； 3、总决赛参赛团队必须由3名学生和1名指导老师组成，学生及指导老师需来自同一所高校； 4、每名总决赛参赛选手只能参加一个赛道（实践赛与创
Hyper-V的使用技巧及管理方法
Jason_Deng_2017的博客
12-22 2万+
摘要 　　本文第一章简要介绍了Microsoft Hyper-V 产品背景、不同类型的Hyper-V及如何安装使用Hyper-V。 　　第二章介绍了Hyper-V的各项基本功能以及配置项，并从具体场景出发解释Hyper-V 的各个配置项的用途。 　　第三章详细介绍Hyper-V 四个较为高级的功能，并配以实例进行诠释，帮助读者理解如何使用这些功能。 　　第四章则从部署角度介绍如何构建Hyp...
行业分类-设备装置-一种高可伸缩性RAID阵列存储视频监控数据的方法和装置.zip
09-11
综上所述，"一种高可伸缩性RAID阵列存储视频监控数据的方法和装置"是针对视频监控领域定制的存储解决方案，它结合了高可扩展性、高性能、数据安全性和智能管理特性，以满足大数据量、高实时性以及严苛的可靠性要求。...
kmod-oracleasm-2.0.6.rh1-3.el6.x86_64.rpm和Oracleasmlib、Oracleasm-support
09-04
Oracle ASM (Automatic Storage Management) 是 Oracle 公司提供的一种高效、自动化的磁盘管理解决方案，尤其在Oracle数据库环境中被广泛使用。它简化了存储管理，提供了高性能、高可用性和高可扩展性。Oracleasmlib...
服装店创业计划书----高可.zip
12-07
以下是对"服装店创业计划书----高可.zip"内容的详细解读： 1. **市场研究**：首先，计划书中会包含对目标市场的深入分析，包括市场规模、消费者群体、竞争对手状况、行业趋势等。了解潜在顾客的需求、购买行为以及...
rhino grasshoper 框内物体排列（附视频）.gh
最新发布
10-18
【闭合线内物体按方向移动/排列】https://www.bilibili.com/video/BV1z1WfeSEWu?vd_source=b420114c993138474d2e93d83ead77a5
kwant-1.4.3-cp38-cp38-win_amd64.whl
10-18
kwant-1.4.3-cp38-cp38-win_amd64.whl
rhino grasshoper 景观椅（附视频）.gh
10-18
【rhino@grasshoper 曲线金属座椅景观案例（文件获取/见简介）】https://www.bilibili.com/video/BV1Dx4y147Lr?vd_source=b420114c993138474d2e93d83ead77a5
PCIe通义万问系列文档的第一部已整理完毕，含999个PCIe相关问答
10-18
《PCIe通义万问》系列文档旨在记录PCIe相关行业工程师们在PCIe协议学习、IP设计验证、产品测试及使用过程中遇到的问题、迸发的思考、进行的探讨及可能的解决方案，以期给遇到相同相似问题的同行们些许启发。文档涉及的技术方向主要为PCIe，也包含PCIe相关的CXL、UCIe及计算机体系结构相关内容。 本文档是《PCIe通义万问》系列文档之（一），含999个问题。问题内容有以下三个来源：MangoPapa（下称博主）的“PCIe每日一问一答”系列专栏；博主的博文留言及私信讨论；博主作为群主的“PCIe技术交流群”群聊内容。MangoPapa小助理、折叠、先杰、CR小队长、kangling共同完成了问答内容提取与归纳整理，噫嘘唏及慕荷负责文辞优化及编辑排版，上述人员及MangoPapa、JasonW、皮塞阿姨、席可儿参与了文档内容的审校。感谢以上人员的无私奉献。 本文档仅对讨论内容进行总结记录，不保证问题答案的正确性，部分问题只提供解决思路或讨论过程。术业有专攻，文内定有偏颇。如您发现谬误，一敬希原宥，二望乞点拨；如您持异见，欢迎来信讨论。如有需要，欢迎联系MangoPapa加入相关
毕业设计论文SpringBoot招投标管理系统.docx
10-18
毕业设计论文
使用IPVS-DR+heartbeat+ldirectord搭建高可用负载均衡集群
"IPVS-DR+heartbeat+ldirectord构建高可用负载均衡群集的实验手册，由火星狼制作，适用于内部培训。手册详细介绍了如何利用这些技术创建一个稳定且可靠的负载均衡环境，包括各个节点的角色分配和IP地址设置。" 在本...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值