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

fix: 源上传失败,目标下载任务却是成功的,整体任务状态也正常,不符合预期 #2987

Open
wangyu096 opened this issue May 15, 2024 · 1 comment
Assignees
Labels
backlog 需求初始状态,等待产品进行评估 kind/bug 程序故障Bug,漏洞

Comments

@wangyu096
Copy link
Collaborator

Version / Branch / tag

3.x -> 3.9.x

出了什么问题?(What Happened?)

源上传失败,目标下载任务却是成功的,整体任务状态也正常,不符合预期
image

如何复现?(How to reproduce?)

非必现

预期结果(What you expect?)

下载与上传文件、整体任务状态一致

@wangyu096 wangyu096 added kind/bug 程序故障Bug,漏洞 backlog 需求初始状态,等待产品进行评估 labels May 15, 2024
@wangyu096 wangyu096 self-assigned this May 15, 2024
@wangyu096
Copy link
Collaborator Author

原因分析

  1. GSE 文件分发任务做拆分成 upload 和 download 原子文件任务。由于 GSE 的一些优化策略,当目标文件在目标服务器的目标路径上已存在(md5 相同)时,哪怕文件源 upload的任务结果为失败,都会把 download 原子任务状态设置为成功。
  2. job 判断整体任务成功的逻辑:download 任务全部成功。所以这个案例中,实际上 gse 返回的 download 原子任务状态都是成功的,所以判定整体成功
  3. 之所以会出现下载原子任务的状态为“FAIL“,是因为 upload 文件失败了,job 会认为对应的 download 原子任务必然是失败的,有这个处理逻辑,导致原本的下载任务状态被覆盖为”FAIL“
  4. 所以,任务总体结果是成功的,这里需要优化子任务的显示状态

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog 需求初始状态,等待产品进行评估 kind/bug 程序故障Bug,漏洞
Projects
None yet
Development

No branches or pull requests

1 participant