【YashanDB知识库】YCP高可用部署离线升级-rpc升级详细步骤

news2024/12/18 11:42:25

本文内容来自YashanDB官网，原文内容请见 https://www.yashandb.com/newsinfo/7686586.html?templateId=1718516

以23.2.4.100版本升级到23.2.11.100版本为例

升级前先对YCP主备节点执行备份

1、主节点执行

/opt/ycm/ycm/scripts/backup.sh -n ycm -i /opt/ycm/ycm -c yashandb -y /data1/dugg/yasdb_home/yashandb/23.2.2.100 --cata-log /data1/dugg/yasdb_home/yashandb/23.2.2.100/catalog --addr 192.168.3.102:3675 -k 0d09e5d01100dc76 -u sys -p Cod-2022

[dugg@localhost upgrade]$ /opt/ycm/ycm/scripts/backup.sh -n ycm -i /opt/ycm/ycm -c yashandb -y /data1/dugg/yasdb_home/yashandb/23.2.2.100 --cata-log /data1/dugg/yasdb_home/yashandb/23.2.2.100/catalog --addr 192.168.3.102:3675 -k 0d09e5d01100dc76 -u sys -p Cod-2022

backup ycm, tag: 20240926-153611...

[backup db] exec yasbak deploy

 hostid | node_type | nodeid | pid | instance_status | database_status | database_role | listen_address | data_path

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

 host0001 | db | 1-1:1 | 739908 | open | normal | primary | 192.168.3.102:3688 | /data1/dugg/yasdb_data/db-1-1

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

 host0002 | db | 1-2:2 | 658538 | open | normal | standby | 192.168.3.105:3688 | /data1/dugg/yasdb_data/db-1-2

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

 host0003 | db | 1-3:3 | 647339 | open | normal | standby | 192.168.3.106:3688 | /data1/dugg/yasdb_data/db-1-3

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

cluster:yashandb deploy yasbak succeed

[backup db] exec yasbak run backup database

connecting to yasdb node: 192.168.3.106:3688

backup 192.168.3.106:3688 succeed

[backup db] backup yashandb success

[backup dir] cp data/cert

[backup dir] cp data/yasdbpasswd.ini

[backup dir] cp etc

[backup dir] cp loki/loki-local-config.yaml

[backup dir] cp loki/loki-rules.yaml.bak

[backup dir] cp loki/rules

[backup dir] cp loki/tmp_rules

[backup dir] cp monit/conf

[backup dir] cp monit/data/conf

[backup dir] cp monit/data/monitrc

[backup dir] cp prometheus-2.28.1/prometheus.yml

[backup dir] cp prometheus-2.28.1/rules.yml

[backup dir] cp promtail/positions.yaml

[backup dir] cp promtail/promtail-local-config.yaml

[backup dir] cp static

[backup dir] cp yashandb_exporter/yashandb-metrics.yml

[backup dir] cp yashandb_exporter/yashandb-targets.yml

[backup dir] cp yas-hcs-api/conf

[backup dir] tar /opt/ycm/ycm/bak/ycm-20240926-153611.tar.gz

[backup dir] backup ycm success

[clear old backup] back up file is less than three, skip remove

back up success, backup set in /opt/ycm/ycm/bak/ycm-20240926-153611.tar.gz

2、第一个备节点执行

/opt/ycm/ycm/scripts/backup.sh -n ycm -i /opt/ycm/ycm -c yashandb -y /data1/dugg/yasdb_home/yashandb/23.2.2.100 --cata-log /data1/dugg/yasdb_home/yashandb/23.2.2.100/catalog --addr 192.168.3.102:3675 -k 0d09e5d01100dc76 -u sys -p Cod-2022

[dugg@controller upgrade]$ /opt/ycm/ycm/scripts/backup.sh -n ycm -i /opt/ycm/ycm -c yashandb -y /data1/dugg/yasdb_home/yashandb/23.2.2.100 --cata-log /data1/dugg/yasdb_home/yashandb/23.2.2.100/catalog --addr 192.168.3.102:3675 -k 0d09e5d01100dc76 -u sys -p Cod-2022

backup ycm, tag: 20240926-153650...

[backup db] exec yasbak deploy

 hostid | node_type | nodeid | pid | instance_status | database_status | database_role | listen_address | data_path

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

 host0001 | db | 1-1:1 | 739908 | open | normal | primary | 192.168.3.102:3688 | /data1/dugg/yasdb_data/db-1-1

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

 host0002 | db | 1-2:2 | 658538 | open | normal | standby | 192.168.3.105:3688 | /data1/dugg/yasdb_data/db-1-2

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

 host0003 | db | 1-3:3 | 647339 | open | normal | standby | 192.168.3.106:3688 | /data1/dugg/yasdb_data/db-1-3

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

cluster:yashandb deploy yasbak succeed

[backup db] exec yasbak run backup database

connecting to yasdb node: 192.168.3.106:3688

backup 192.168.3.106:3688 succeed

[backup db] backup yashandb success

[backup dir] cp data/cert

[backup dir] cp data/yasdbpasswd.ini

[backup dir] cp etc

[backup dir] cp loki/loki-local-config.yaml

[backup dir] cp loki/loki-rules.yaml.bak

[backup dir] cp loki/rules

[backup dir] cp loki/tmp_rules

[backup dir] cp monit/conf

[backup dir] cp monit/data/conf

[backup dir] cp monit/data/monitrc

[backup dir] cp prometheus-2.28.1/prometheus.yml

[backup dir] cp prometheus-2.28.1/rules.yml

[backup dir] cp promtail/positions.yaml

[backup dir] cp promtail/promtail-local-config.yaml

[backup dir] cp static

[backup dir] cp yashandb_exporter/yashandb-metrics.yml

[backup dir] cp yashandb_exporter/yashandb-targets.yml

[backup dir] cp yas-hcs-api/conf

[backup dir] tar /opt/ycm/ycm/bak/ycm-20240926-153650.tar.gz

[backup dir] backup ycm success

[clear old backup] back up file is less than three, skip remove

back up success, backup set in /opt/ycm/ycm/bak/ycm-20240926-153650.tar.gz

3、第二个备节点执行

/opt/ycm/ycm/scripts/backup.sh -n ycm -i /opt/ycm/ycm -c yashandb -y /data1/dugg/yasdb_home/yashandb/23.2.2.100 --cata-log /data1/dugg/yasdb_home/yashandb/23.2.2.100/catalog --addr 192.168.3.102:3675 -k 0d09e5d01100dc76 -u sys -p Cod-2022

[dugg@host106 upgrade]$ /opt/ycm/ycm/scripts/backup.sh -n ycm -i /opt/ycm/ycm -c yashandb -y /data1/dugg/yasdb_home/yashandb/23.2.2.100 --cata-log /data1/dugg/yasdb_home/yashandb/23.2.2.100/catalog --addr 192.168.3.102:3675 -k 0d09e5d01100dc76 -u sys -p Cod-2022

backup ycm, tag: 20240926-153703...

[backup db] exec yasbak deploy

 hostid | node_type | nodeid | pid | instance_status | database_status | database_role | listen_address | data_path

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

 host0001 | db | 1-1:1 | 739908 | open | normal | primary | 192.168.3.102:3688 | /data1/dugg/yasdb_data/db-1-1

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

 host0002 | db | 1-2:2 | 658538 | open | normal | standby | 192.168.3.105:3688 | /data1/dugg/yasdb_data/db-1-2

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

 host0003 | db | 1-3:3 | 647339 | open | normal | standby | 192.168.3.106:3688 | /data1/dugg/yasdb_data/db-1-3

----------+-----------+--------+--------+-----------------+-----------------+---------------+--------------------+-------------------------------

cluster:yashandb deploy yasbak succeed

[backup db] exec yasbak run backup database

connecting to yasdb node: 192.168.3.106:3688

backup 192.168.3.106:3688 succeed

[backup db] backup yashandb success

[backup dir] cp data/cert

[backup dir] cp data/yasdbpasswd.ini

[backup dir] cp etc

[backup dir] cp loki/loki-local-config.yaml

[backup dir] cp loki/loki-rules.yaml.bak

[backup dir] cp loki/rules

[backup dir] cp loki/tmp_rules

[backup dir] cp monit/conf

[backup dir] cp monit/data/conf

[backup dir] cp monit/data/monitrc

[backup dir] cp prometheus-2.28.1/prometheus.yml

[backup dir] cp prometheus-2.28.1/rules.yml

[backup dir] cp promtail/positions.yaml

[backup dir] cp promtail/promtail-local-config.yaml

[backup dir] cp static

[backup dir] cp yashandb_exporter/yashandb-metrics.yml

[backup dir] cp yashandb_exporter/yashandb-targets.yml

[backup dir] cp yas-hcs-api/conf

[backup dir] tar /opt/ycm/ycm/bak/ycm-20240926-153703.tar.gz

[backup dir] backup ycm success

[clear old backup] back up file is less than three, skip remove

back up success, backup set in /opt/ycm/ycm/bak/ycm-20240926-153703.tar.gz

升级主节点

1、解压安装包、三个节点都解压

[dugg@localhost upgrade]$ tar -zxvf yashandb-cloud-platform-23.2.11.100-linux-x86_64.tar.gz

2、生成被托管服务器的配置文件

sudo ./scripts/yasadm host gen -i /opt/ycm --rpc-port 9072

sudo ./scripts/yasadm host gen -i /opt/ycm --rpc-port 9072

 

-i, --install-dir 管理平台的安装路径

--rpc-port 管理平台服务器的升级RPC端口，用于RPC升级方式，默认为9072

 

[dugg@localhost upgrade]$ cd ycm

[dugg@localhost ycm]$ sudo ./scripts/yasadm host gen -i /opt/ycm --rpc-port 9072

command executed successfully

[dugg@localhost ycm]$ ll

total 24308

drwxrwxr-x. 3 dugg dugg 79 Sep 18 17:19 etc

drwxrwxr-x. 2 dugg dugg 10 Sep 18 17:19 log

drwxrwxr-x. 2 dugg dugg 4096 Sep 18 17:19 packages

drwxrwxr-x. 3 dugg dugg 67 Sep 18 17:19 scripts

drwxrwxr-x. 5 dugg dugg 4096 Sep 18 17:19 static

-rw-r--r--. 1 root root 1123 Sep 26 15:38 ycm_host.toml

-rwxrwxr-x. 1 dugg dugg 24875776 Sep 18 17:19 ycm-init

3、执行升级命令

sudo ./scripts/yasadm upgrade -i /opt/ycm -t ycm_host.toml --imp-exp-install-dir /data1/dugg/yasdb_home/yashandb/23.2.2.100 --rpc --role primary

sudo ./scripts/yasadm upgrade -i /opt/ycm -t ycm_host.toml --imp-exp-install-dir /data1/dugg/yasdb_home/yashandb/23.2.2.100 --rpc --role primary

 

-i, --install-dir 管理平台的安装路径

-t, --toml 被托管服务器信息的配置文件

--imp-exp-install-dir 安装有imp和exp的yashandb客户端路径，用于备份平台后端yashandb的数据

--role primary 升级主YCP

--plugin-package 可选，其它CPU架构的系统安装包，如果平台同时管理了x86_64和aarch64主机，该参数必填

 

[dugg@localhost ycm]$ ./scripts/yasadm upgrade -i /opt/ycm -t ycm_host.toml --imp-exp-install-dir /data1/dugg/yasdb_home/yashandb/23.2.2.100 --rpc --role primary --plugin-package /home/dugg/install/yashandb-cloud-platform-23.2.11.100-linux-aarch64.tar.gz

2024/09/26 16:21:56 upgrade check success

2024/09/26 16:21:56 [HOST INFO]:

HostId: host-750a9921, ManageIp: 192.168.3.105, HostName: controller

HostId: host-be7ed325, ManageIp: 192.168.3.106, HostName: host106

HostId: host-8db9f906, ManageIp: 192.168.3.102, HostName: localhost.localdomain

HostId: host-4f679140, ManageIp: 192.168.8.4, HostName: localhost.localdomain

HostId: host-5a28f120, ManageIp: 192.168.24.59, HostName: k8s-24.59

HostId: host-caaa2e41, ManageIp: 192.168.24.49, HostName: k8s-24.49

HostId: host-c42d7e89, ManageIp: 192.168.24.48, HostName: k8s-24.48

Are you sure to upgrade YCP? [yes/no]

yes

yes

2024/09/26 16:22:00 genertate upgrade backup config success

2024/09/26 16:22:04 deploy host host-750a9921 upgrade agent success

2024/09/26 16:22:05 deploy host host-be7ed325 upgrade agent success

2024/09/26 16:22:07 deploy host host-8db9f906 upgrade agent success

2024/09/26 16:22:08 deploy host host-4f679140 upgrade agent success

2024/09/26 16:22:10 deploy host host-5a28f120 upgrade agent success

2024/09/26 16:22:11 deploy host host-caaa2e41 upgrade agent success

2024/09/26 16:22:12 deploy host host-c42d7e89 upgrade agent success

2024/09/26 16:22:13 deploy upgrade agent success

2024/09/26 16:22:13 upgrade 23.2.4.100 to 23.2.11.100 begin

2024/09/26 16:22:13 create upgrade record in yashandb success

2024/09/26 16:22:14 [host-4f679140] stop ycm-agent process success

2024/09/26 16:22:14 [host-c42d7e89] stop ycm-agent process success

2024/09/26 16:22:14 [host-caaa2e41] stop ycm-agent process success

2024/09/26 16:22:14 [host-be7ed325] stop ycm-agent process success

2024/09/26 16:22:14 [host-8db9f906] stop ycm-agent process success

2024/09/26 16:22:14 [host-750a9921] stop ycm-agent process success

2024/09/26 16:22:14 [host-5a28f120] stop ycm-agent process success

[WARN]: /opt/ycm/ycm/scripts/yas-hc-api.sh does not exist, skip operate

2024/09/26 16:22:30 stop ycm process success

2024/09/26 16:22:30 stop all ycm/ycm-agent process success

2024/09/26 16:22:33 backup ycm success

2024/09/26 16:22:33 backup ycm-agent host-750a9921 success

2024/09/26 16:22:34 backup ycm-agent host-be7ed325 success

2024/09/26 16:22:35 backup ycm-agent host-8db9f906 success

2024/09/26 16:22:35 backup ycm-agent host-4f679140 success

2024/09/26 16:22:35 backup ycm-agent host-5a28f120 success

2024/09/26 16:22:36 backup ycm-agent host-caaa2e41 success

2024/09/26 16:22:36 backup ycm-agent host-c42d7e89 success

2024/09/26 16:22:36 backup all ycm/ycm-agent success

2024/09/26 16:22:44 install ycm upgrade package success

2024/09/26 16:22:47 install ycm-agent host-750a9921 upgrade package success

2024/09/26 16:22:51 install ycm-agent host-be7ed325 upgrade package success

2024/09/26 16:22:55 install ycm-agent host-8db9f906 upgrade package success

2024/09/26 16:23:00 install ycm-agent host-4f679140 upgrade package success

2024/09/26 16:23:02 install ycm-agent host-5a28f120 upgrade package success

2024/09/26 16:23:05 install ycm-agent host-caaa2e41 upgrade package success

2024/09/26 16:23:09 install ycm-agent host-c42d7e89 upgrade package success

2024/09/26 16:23:09 install all ycm/ycm-agent upgrade package success

2024/09/26 16:23:10 replace ycm/ycm-agent dir and file success

2024/09/26 16:23:10 exec upgrade sql success

2024/09/26 16:23:10 add default data success

2024/09/26 16:23:10 update config file ycm.yaml success

2024/09/26 16:23:10 update backup strategy in db success

2024/09/26 16:23:10 upgrade metadata success

2024/09/26 16:23:21 [host-c42d7e89] start ycm-agent process success

2024/09/26 16:23:21 [host-caaa2e41] start ycm-agent process success

2024/09/26 16:23:21 [host-4f679140] start ycm-agent process success

2024/09/26 16:23:21 [host-8db9f906] start ycm-agent process success

2024/09/26 16:23:21 [host-be7ed325] start ycm-agent process success

2024/09/26 16:23:21 [host-5a28f120] start ycm-agent process success

2024/09/26 16:23:21 [host-750a9921] start ycm-agent process success

2024/09/26 16:23:21 start ycm process success

2024/09/26 16:23:21 update host kernel arch success

2024/09/26 16:23:21 update upgrade status in yashandb success

2024/09/26 16:23:21 update upgrade stauts in config success

2024/09/26 16:23:21 upgrade success

2024/09/26 16:23:30 uncompleted upgrade instances:

instId: ycp0002; ListenIp: 0.0.0.0; electionIp: 192.168.3.105; port: 9010

instId: ycp0003; ListenIp: 0.0.0.0; electionIp: 192.168.3.106; port: 9010

command executed successfully

升级备节点

1、第一个备节点

sudo ./scripts/yasadm upgrade -i /opt/ycm --lib-dir /data1/dugg/yasdb_home/yashandb/23.2.2.100/lib --role standy

[dugg@controller ycm]$ sudo ./scripts/yasadm upgrade -i /opt/ycm --lib-dir /data1/dugg/yasdb_home/yashandb/23.2.2.100/lib --role standby

2024/09/26 16:51:37 [HOST INFO]:

Are you sure to upgrade YCP? [yes/no]

yes

yes

2024/09/26 16:51:40 genertate upgrade backup config success

2024/09/26 16:51:40 upgrade 23.2.4.100 to 23.2.11.100 begin

2024/09/26 16:51:40 create upgrade record in yashandb success

[WARN]: /opt/ycm/ycm/scripts/yas-hc-api.sh does not exist, skip operate

2024/09/26 16:51:41 stop ycm process success

2024/09/26 16:51:41 backup ycm success

2024/09/26 16:51:46 install ycm upgrade package success

2024/09/26 16:51:46 replace ycm dir and file success

2024/09/26 16:51:46 update config file ycm.yaml success

2024/09/26 16:51:54 start ycm process success

2024/09/26 16:51:54 update upgrade status in yashandb success

2024/09/26 16:51:54 update upgrade stauts in config success

2024/09/26 16:51:54 upgrade success

2024/09/26 16:51:54 uncompleted upgrade instances:

instId: ycp0003; ListenIp: 0.0.0.0; electionIp: 192.168.3.106; port: 9010

command executed successfully

2、第二个备节点

sudo ./scripts/yasadm upgrade -i /opt/ycm --lib-dir /data1/dugg/yasdb_home/yashandb/23.2.2.100 --role standy

[dugg@host106 ycm]$ sudo ./scripts/yasadm upgrade -i /opt/ycm --lib-dir /data1/dugg/yasdb_home/yashandb/23.2.2.100/lib --role standby

2024/09/26 16:52:19 [HOST INFO]:

Are you sure to upgrade YCP? [yes/no]

yes

yes

2024/09/26 16:52:21 genertate upgrade backup config success

2024/09/26 16:52:21 upgrade 23.2.4.100 to 23.2.11.100 begin

2024/09/26 16:52:21 create upgrade record in yashandb success

[WARN]: /opt/ycm/ycm/scripts/yas-hc-api.sh does not exist, skip operate

2024/09/26 16:52:22 stop ycm process success

2024/09/26 16:52:22 backup ycm success

2024/09/26 16:52:27 install ycm upgrade package success

2024/09/26 16:52:27 replace ycm dir and file success

2024/09/26 16:52:27 update config file ycm.yaml success

2024/09/26 16:52:35 start ycm process success

2024/09/26 16:52:35 update upgrade status in yashandb success

2024/09/26 16:52:35 update upgrade stauts in config success

2024/09/26 16:52:35 upgrade success

command executed successfully

3、查看升级后版本

cat /opt/ycm/ycm/etc/upgrade/version.toml

[dugg@host106 upgrade]$ cat /opt/ycm/ycm/etc/upgrade/version.toml

version = "23.2.11.100"

 

[[upgrade]]

source_version = ["23.1.2.100"]

path = "23.1.2.100"

 

[[upgrade]]

source_version = ["23.1.3.100", "23.1.4.1"]

path = "23.1.3.100"

 

[[upgrade]]

source_version = ["23.1.4.2", "23.1.4.3", "23.2.1.100", "23.2.1.103", "23.2.1.104", "23.2.1.105", "23.2.2.100", "23.2.3.100", "23.2.4.100", "23.2.5.100", "23.2.6.100", "23.2.7.100", "23.2.8.100", "23.2.8.101", "23.2.9.100", "23.2.10.100"]

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若转载，请注明出处：http://www.coloradmin.cn/o/2261570.html

如若内容造成侵权/违法违规/事实不符，请联系多彩编程网进行投诉反馈，一经查实，立即删除！

相关文章

[蓝桥杯 2019 国 B] 排列数

[蓝桥杯 2019 国 B] 排列数

目录 前言 题解 思路 疑问 解答 前言 对于本篇文章是站在别人的基础之上来写的，对于这道题作为2019年国赛B组的最难的一题，他的难度肯定是不小的，这道题我再一开始接触的时候连思路都没有，也是看了两三遍别人发的题解&#x…
阅读更多...
Spring Boot 3.x：自动配置类加载机制的变化

Spring Boot 3.x：自动配置类加载机制的变化

随着 Spring Boot 3.x 版本的发布，Spring Boot 引入了一些关键的变更。其中最重要的一项变更是 自动配置类的加载机制。在之前的版本中，Spring Boot 使用 spring.factories 文件来管理自动配置类的加载。然而，在 Spring Boot 3.x 中&#xff…
阅读更多...
arXiv-2024 | NavAgent：基于多尺度城市街道视图融合的无人机视觉语言导航

arXiv-2024 | NavAgent：基于多尺度城市街道视图融合的无人机视觉语言导航

作者：Youzhi Liu, Fanglong Yao*, Yuanchang Yue, Guangluan Xu, Xian Sun, Kun Fu 单位：中国科学院大学电子电气与通信工程学院，中国科学院空天信息创新研究院网络信息系统技术重点实验室 原文链接：NavAgent: Multi-scale Urba…
阅读更多...
（三）PyQT5+QGIS+python使用经验——解决各版本不兼容问题

（三）PyQT5+QGIS+python使用经验——解决各版本不兼容问题

一、问题描述 基础环境：Windows10（64） PyCharm2024 QGIS 3.22。 目的：解决之前python版本多，pyqt5以及QT Designer交互使用存在环境变量冲突矛盾，以及QGIS安装时自带python、pyqt5等问题。 尤其是在QT …
阅读更多...
【OpenCV计算机视觉】图像处理——平滑

【OpenCV计算机视觉】图像处理——平滑

本篇文章记录我学习【OpenCV】图像处理中关于“平滑”的知识点，希望我的分享对你有所帮助。 目录 一、什么是平滑处理 1、平滑的目的是什么？ 2、常见的图像噪声 （1）椒盐噪声 ​编辑（2） 高斯噪声 &a…
阅读更多...
秒优科技-供应链管理系统 login/doAction SQL注入漏洞复现

秒优科技-供应链管理系统 login/doAction SQL注入漏洞复现

0x01 产品简介 秒优科技提供的供应链管理系统，即秒优SCM服装供应链管理系统，是一款专为服装电商企业设计的全方位解决方案。是集款式研发、订单管理、物料管理、生产管理、工艺管理、收发货管理、账单管理、报表管理于一体的服装电商供应链管理解决方案。它涵盖了从企划到开…
阅读更多...
快速掌握源码部署Filebeat

快速掌握源码部署Filebeat

文章目录 1. 裸金属安装1.1 压缩包方式安装1.2 yum方式安装 2. docker安装3. K8s安装 项目使用了Filebeat，现在需要运行在ARM架构的服务器上，但是Filebeat官方没有提供，需要自己编译一份 filebeat等组件的源码地址 https://github.com/elasti…
阅读更多...
ST-Linker V2 烧录器详解说明文档

ST-Linker V2 烧录器详解说明文档

目录 ST-Linker v2烧录器介绍 STM8烧录口 STM32烧录接口 JTAG烧录接口 ​​​​​​​ ​​​​​​​ ​​​​​​​ 编写不易，仅供学习，请勿搬运，感谢理解 ST-Linker v2烧录器介绍 图片中是两种IC芯片的烧录器&#x…
阅读更多...
同三维TL201H2S4 4+2机手术互动录播主机产品

同三维TL201H2S4 4+2机手术互动录播主机产品

同三维TL201H2S4 42机手术互动录播主机产品 录制点播、直播导播、互动、音频处理器、中控等多功能为一体 6路视频输入:4路SDI1路HDMI1(4K30)1路(3选1:HDMI2/2路VGA) 2路视频输出：1路HDMI1(4K30)1路（2选1：VGA和HDMI2) 5路音频输入&#xf…
阅读更多...
RabbitMQ实现网络分区

RabbitMQ实现网络分区

RabbitMQ实现网络分区 网络分区的判断应答时间范围判定方式日志方式命令查看监控页面提示API查看 模拟网络分区封禁端口封禁IP封禁网卡挂起恢复操作系统 网络分区的影响未配置镜像队列情况下已配置镜像队列情况下 处理网络分区手动处理恢复步骤挑选信任分区重启方式&#xff08…
阅读更多...
一、LRU缓存

一、LRU缓存

LRU缓存 1.LRU缓存介绍2.LRU缓存实现3.LRU缓存总结3.1 LRU 缓存的应用3.2 LRU 缓存的优缺点 1.LRU缓存介绍 LRU是Least Recently Used 的缩写，意为“最近最少使用”。它是一种常见的缓存淘汰策略，用于在缓存容量有限时，决定哪些数据需要被删…
阅读更多...
【大前端vue：组件】鼠标上移 出现动画

【大前端vue：组件】鼠标上移 出现动画

【大前端vue&#xff1a;组件】鼠标上移 出现动画 <template><div class"view-introduction-culture"><div class"culture-wrapper"><h2 class"culture-title">鼠标上移&#xff1a;展示动画 显示出来</h2><di…
阅读更多...
解决电脑网速慢问题：硬件检查与软件设置指南

解决电脑网速慢问题：硬件检查与软件设置指南

电脑网速慢是许多用户在使用过程中常见的问题&#xff0c;它不仅会降低工作效率&#xff0c;还可能影响娱乐体验。导致电脑网速慢的原因多种多样&#xff0c;包括硬件问题、软件设置和网络环境等。本文将从不同角度分析这些原因&#xff0c;并提供提高电脑网速的方法。 一、检查…
阅读更多...
快速本地化部署 OnlyOffice服务 （ Linux+Docker）

快速本地化部署 OnlyOffice服务 （ Linux+Docker）

文章目录 一、OnlyOffice介绍&#x1f4d6;二、集成OnlyOffice&#x1f9e9;2.1 环境准备&#x1f5a5;️2.2 搜索镜像2.3 拉取镜像2.4 查看镜像2.5 创建容器2.6 进入容器配置2.7 重启服务2.8 添加字体字号2.9 测试OnlyOffice服务 三、在线预览office文档四、Cpolar内网穿透 一…
阅读更多...
Leecode刷题C++之形成目标字符串需要的最少字符串数①

Leecode刷题C++之形成目标字符串需要的最少字符串数①

执行结果:通过 执行用时和内存消耗如下&#xff1a; 代码如下&#xff1a; class Solution { public:int minValidStrings(vector<string>& words, string target) {auto prefix_function [](const string& word, const string& target) -> vector<…
阅读更多...
51c嵌入式~合集2

51c嵌入式~合集2

我自己的原文哦~ https://blog.51cto.com/whaosoft/11529950 一、不同的电平信号的MCU怎么通信 “电平转换”电路 ​ 先说一说这个电路的用途&#xff1a;当两个MCU在不同的工作电压下工作&#xff08;如MCU1 工作电压5V&#xff1b;MCU2 工作电压3.3V&#xff09;&#xf…
阅读更多...
2024年第十五届蓝桥杯青少组C++国赛—割点

2024年第十五届蓝桥杯青少组C++国赛—割点

割点 题目描述 一张棋盘由n行 m 列的网格矩阵组成&#xff0c;每个网格中最多放一颗棋子。当前棋盘上已有若干棋子。所有水平方向或竖直方向上相邻的棋子属于同一连通块。 现给定棋盘上所有棋子的位置&#xff0c;如果要使棋盘上出现两个及以上的棋子连通块&#xff0c;请问…
阅读更多...
Java线程池解读

Java线程池解读

Java 线程池是一个提供多线程管理和调度的工具&#xff0c;通常用来处理多个并发任务。线程池能够帮助有效管理线程的创建、调度、执行和销毁&#xff0c;避免频繁的线程创建和销毁&#xff0c;提高系统性能。 前言 Java 线程池是面试中的常客&#xff0c;面试官经常会问线程…
阅读更多...
如何为IntelliJ IDEA配置JVM参数

如何为IntelliJ IDEA配置JVM参数

在使用IntelliJ IDEA进行Java开发时&#xff0c;合理配置JVM参数对于优化项目性能和资源管理至关重要。IntelliJ IDEA提供了两种方便的方式来设置JVM参数&#xff0c;以确保你的应用程序能够在最佳状态下运行。本文将详细介绍这两种方法&#xff1a;通过工具栏编辑配置和通过服…
阅读更多...
【CC2530开发基础篇】继电器模块使用

【CC2530开发基础篇】继电器模块使用

一、前言 1.1 开发背景 本实验通过使用CC2530单片机控制继电器的吸合与断开&#xff0c;深入了解单片机GPIO的配置与应用。继电器作为一种常见的电气控制元件&#xff0c;广泛用于自动化系统中&#xff0c;用于控制大功率负载的开关操作。在本实验中&#xff0c;将通过GPIO口…
阅读更多...
推荐文章
最新文章

Copyright @ 2022~2023