Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]node-controller模式下,配置完node节点定时同步jar包后,node节点jar包实际无同步 #30621

Open
lol666666 opened this issue Apr 26, 2024 · 4 comments

Comments

@lol666666
Copy link

联系方式

13716054767

MeterSphere 版本

v2.10.13-lts-163a8232

使用外置数据库

问题描述

配置node-controller模式,勾选定时同步jar包,但是节点node下同步的目录为空
/data/metersphere/metersphere/data/api-folder/jar/node/847f9a75-a4ae-47c8-8a41-f046ffef196d 麻烦问下,我资源池选择定时同步jar包了,但是发现node节点下的目录只有更新文件夹了,没有把jar包同步过去

重现步骤

  1. 主服务建立测试资源池
  2. 资源池配置好node和定时同步jar包
  3. 运行程序报错
  4. 发现node节点下的/data/metersphere/metersphere/data/api-folder/jar/node/847f9a75-a4ae-47c8-8a41-f046ffef196d 目录为空,jar包未同步

期待的正确结果

node节点正确同步获取主服务的jar包

相关日志输出

No response

附加信息

No response

@github-actions github-actions bot added the 状态:待处理 已分配给相关处理人等待处理人处理并更新状态 label Apr 26, 2024
@lol666666 lol666666 changed the title [BUG] [BUG]node-controller模式下,配置完node节点定时同步jar包后,node节点jar包实际无同步 Apr 26, 2024
@fit2-zhao
Copy link
Contributor

目前并未做热加载,插件包上传后需要重启 api-test 和 node-controller 服务。

@github-actions github-actions bot added 状态:待用户反馈 and removed 状态:待处理 已分配给相关处理人等待处理人处理并更新状态 labels Apr 26, 2024
@lol666666
Copy link
Author

重启后也未同步到node的目录下

@github-actions github-actions bot added 状态:待处理 已分配给相关处理人等待处理人处理并更新状态 and removed 状态:待用户反馈 labels Apr 26, 2024
@lol666666
Copy link
Author

重启后当时node节点目录下会存在同步的jar包,但是执行node的资源池时会被程序删除

@fit2-zhao
Copy link
Contributor

/data/metersphere/metersphere/data/api-folder/jar/node/ 这个目录下存放是文件管理中上传的函数包,当有jar变更时每次执行都会同步最新包,您把错误信息发出来看看。

@github-actions github-actions bot added 状态:待用户反馈 and removed 状态:待处理 已分配给相关处理人等待处理人处理并更新状态 labels Apr 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants