Sitelet https://web.archive.org/web/20210816121006/https://github.com/TarsCloud/Tars/issues/820
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

同时发布一个服务的多个节点的实现问题 #820

Open
dangesong opened this issue Oct 15, 2020 · 2 comments
Open

同时发布一个服务的多个节点的实现问题 #820

dangesong opened this issue Oct 15, 2020 · 2 comments

Comments

@dangesong
Copy link

@dangesong dangesong commented Oct 15, 2020

What language are you using?

C++

What operating system (Linux, Ubuntu, …) and version?

Linux

What runtime / compiler are you using (e.g. jdk version or version of gcc)

4.8.5

Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
tars的发布流程:tarsweb上传安装包 -> tarsAdminRegistry开始发布 -> tarspatch 从/usr/local/app/patchs/tars.uplaod拷贝server.xxx.tgz到/usr/local/app/tars目录下,并重命名为server.tgz -> 通知tarsnode拉取server.tgz。最后发布服务etc
想问一下:
为啥需要执行这个拷贝的逻辑,直接告诉tarsnode来拉取server.xxx.tgz不也可以么?
考虑点:

  1. 单服务多节点发布时,这个拷贝逻辑也执行了多次,性能损耗
  2. 使用NFS时,会限制同一个源文件 -> 目标文件的拷贝,导致发布卡顿甚至失败
@dangesong
Copy link
Author

@dangesong dangesong commented Oct 15, 2020

改动之后的流程:
tarsweb上传安装包 -> tarsAdminRegistry开始发布 -> 通知tarsnode拉取server.xxx.tgz
最后发布服务etc

麻烦大佬们看下这个逻辑有啥问题?

@ruanshudong
Copy link
Contributor

@ruanshudong ruanshudong commented Oct 15, 2020

好像也没有什么问题, 你可以改了试一试, 看看发布啥的有啥问题, 没问题可以代码合并进来

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants