The configuration change of a node caused other normal nodes to panic.
【问题分类】
- bug
- P2P网络相关（包含libp2p,liquid）
- 链账户身份与权限相关（证书问题、public、多签投票问题）
- 核心交易引擎相关（交易池、DAG）
- 共识相关
- 智能合约相关
- 存储相关
- SDK相关
- 长安链CMC工具
- 长安链管理台
- 长安链浏览器
- 长安链合约IDE
- 长安链web签名插件
- 跨链相关
- 轻节点相关
- 隐私计算相关
- 密码学相关
- 环境依赖
- 其他补充：
【问题描述】
I started a blockchain cluster with 13 nodes and performed frequent configuration changes on one of the nodes for testing. After running the tests for a while, one of the other normal nodes in the cluster panicked. Below is a portion of the error log, and I suspect that the concurrent read and write operations on a map in the code were not handled properly.
In order to rule out the impact of frequent node restarts on the test, I conducted an experiment where I only restarted the node frequently without changing its configuration. The experiment lasted for 7 days, and none of the other normal nodes panicked. Therefore, the impact of node restarts on the test can likely be ruled out.
【相关日志文件】（如果有报错日志请贴图，或者上传附件）
【系统信息】（请填写系统信息，方便定位问题）
- chainmaker-go version * : [v2.3.4]
- OS & version * : ubuntu-22.04.3-live-server-amd64, Linux version 5.15.0-119-generic
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information